Preserve index.php in wp-content during import #1052
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issues
Proposed Changes
I propose to add
index.phpto the protected files list during site import. Previously, themoveExistingWpContentToTrashmethod was removingindex.phpfrom thewp-contentdirectory, which is a required WordPress file. The fix ensures this file is preserved alongside other critical files likedb.phpand themu-pluginsdirectory.Testing Instructions
wp-content/index.phpexists in the new sitewp-content/index.phpstill exists after the importPre-merge Checklist