Custom `wordpress` and `wp-content` locations

Feature requests
1

I prefer installingWordPress into ../app/public/wordpress, but leaving content at ../app/public/wp-content.

I think that’s a best practice, because it separates third-party files from custom code. It makes it easier to treat WordPress as a dependency, and keep the root folder much more organized.

It’s possible to do that manually*, but I think the site.conf.hbs changes will get overwritten the next time Local changes it. It’d be nice to WP in a subdirectory instead by default, or at least have an option to do it. Alternatively, you could load site.conf.hbs.local if it exists, and otherwise use the default config.

  • For anyone looking to manually configure things this way, you’ll need to make these changes:
  1. Move wp-admin, wp-includes, and the root files into a app/public/wordpress. Leave wp-content and wp-config.php at app/public.
  2. Create a new index.php that just has: require_once __DIR__ . '/wordpress/index.php';
  3. In wp-config.php, add these lines:

define( ‘WP_CONTENT_DIR’, __DIR__ . ‘/wp-content’ );
define( ‘WP_CONTENT_URL’, ‘https://core.test/wp-content’ );

  1. In conf/nginx/site.conf.hbs, remove the root directive, and add these lines in the server block:

root {absolute path to your site}/app/public/wordpress;

location ~* (/wp-content) {
root /Users/iandunn/local-sites/core/app/public;
}

Optionally, you can also create a {local directory]/{your site}/wp-cli.yml that has:

path: app/public/wordpress

2

Thank you for sharing this @iandunn!