Issue with makrdown file path stored in post meta
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start by tracing where the imported Markdown file path is written to post meta; the issue provides no file or test names. Reproduce the behavior across a plugin-directory move or rename, then verify that the stored reference remains usable without the documented wp search-replace commands.
Written by the indexing model from the issue text.
Description
As the complete path of markdown files to be imported gets stored in post meta. It causes an issue if:
- The absolute path to the plugin folder then changes.
- Name of the plugin changes.
Both of these issue happened in our case.
Had to run the following search-replace commands to fix this:
wp search-replace '/var/www/htdocs/wp-content/plugins/ee-markdown-importer/' '/var/www/htdocs/current/wp-content/plugins/wp-ee-docs-command/' --url=<site-url>
wp search-replace '/var/www/htdocs/wp-content/plugins/wp-ee-docs-command/' '/var/www/htdocs/current/wp-content/plugins/wp-ee-docs-command/' --url=<site-url>
- Dominant language
- PHP
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·