Leave wp-content/plugins and wp-content/themes directories when using --skip-content#230
Conversation
|
What about other directories like |
|
@swissspidy Neither of those directories are affected. Here's where we unwound accidental deletion of |
|
I'd consider this a bug fix. We were too aggressive with the removal and caused issues, and as you said, the original intent was not to remove the folders, but rather to not include the default extensions. So I'd say this is not a breaking change. |
|
Sorry for being late to the party. I would also argue this is a bug fix... that can break code. My main argument is : installing WP with CLI with the --skip-content flag makes a user unable to install a theme or plugin if it's not done, at first, with CLI. So if you just install WP with CLI then never use CLI again, you are left with an unusable installation regarding the addition of themes and plugins. |
I think this is a reasonable argument! Thanks for sharing, @maximejobin |
Creates the
wp-content/pluginsandwp-content/themesdirectories (and their correspondingindex.phpfiles) when usingwp core download --skip-content, instead of ignoring them.While these directories were intentionally excluded in the original pull request...
wp-contentdirectory anyway (pull request), so I don't think it's rational to createwp-contentbut notwp-content/plugins.I'm not sure if we should consider this a breaking change, or a bug with the original implementation.
Fixes #228