It doesn’t matter. It just has to do with standard naming in WordPress because you typically call your “parts” with get_template_part();. get_template_part(); checks if the file is in the child theme first, then uses the one from the parent theme if it doesn’t. It provides a way for you to override template files from the … Read more
I would try changing your line in wp-config.php to define( ‘UPLOADS’, ‘media/blog/files’ ); // where docker is mounted Ie, get rid of the first /. Let me know if this works. EDIT If you can’t change the definition of UPLOADS you could strip out the forward slash out with code. Try changing your code to … Read more
I found that by removing the WordPress section from the .htaccess in the main website root, both main website custom 404 and WordPress custom 404 functionality appear to work correctly. Is there any reason why I shouldn’t do this? Yes, this is what I was going to suggest. If WordPress is installed in the subdirectory … Read more
I believe I’ve found the solution. I add the following RewriteRule ^example_directory/files/(.*) new_directory/$1 to my WordPress .htaccess rules like so: RewriteEngine On RewriteBase / RewriteRule ^example_directory/files/(.*) new_directory/$1 RewriteRule ^index\.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] I couldn’t get it working before and I think the key was moving the … Read more
Using a stock WordPress installation, no. WordPress, by default, stores uploads in the /wp-content/uploads/yyyy/mm/ directory for single sites. For network installations, it stores them elsewhere and maps a similar permalink structure to the new location. I can see what you’re trying to accomplish by keeping things in separate directories, but you’d have to revise a … Read more
Use one main wp-config.php and name the others according to the name of the host: example.com.config.php example.net.config.php and so on. In your main wp-config.php write: $current_config = __DIR__ . “https://wordpress.stackexchange.com/” . $_SERVER[‘HTTP_HOST’] . ‘.config.php’; if ( file_exists( $current_config ) ) require_once $current_config;
Your easiest solution here is to keep everything in your cms folder. and follow this step found at http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory This will keep all wordpress related files in the cms folder, but it will look like its running from the root, copy of index and some .htaccess wizardly as you call it :). enjoy Using a … Read more
I guess you’re talking about a site specific wp-config.php file that resides in your themes folder. At the point where you’re loading the wp-config.php file, WP isn’t fully loaded, so you ain’t got any constants or filesystem API or other basic API functions available. Here’s how I approach this: Structure # Dir structure ~/ROOT ├── … Read more
Comment out the following by adding hash tags before it #RewriteCond %{REQUEST_URI} !^/images/ #RewriteCond %{REQUEST_URI} !^/images #RewriteCond %{REQUEST_URI} !.*images(.*) and see if that helps.
If you want the two to be completely separate (as you hint at in your question), you have two (or three?) options: You install multiple blogs with a sub-directory structure of your choice. This way you will have complete control of your URLs. For example you could have one install running out of your /blog … Read more