The WordPress directory path is available in the constant ABSPATH. Be aware this is not related to the wp-content directory. The constant WP_CONTENT_DIR could be set to exactly the same value. Or another directory on the same level where WP_CONTENT_URL is another domain name. There doesn’t even have to be a wp-content equivalent: themes, plugins, … Read more
Try to set the constant COOKIE_DOMAIN to an empty value or the value of the real address. Example: define( ‘COOKIE_DOMAIN’, ” ); Be aware WordPress has a lot of issues with symlinks, so there might be other problems too.
I’m not sure that what you want is possible. Per the WordPress Codex page on Multisite: You are given the choice between sub-domains and sub-directories, except when existing settings restrict your choice. You must choose one or the other. So you can set your network up to use either sub-domains OR sub-directories for your child … Read more
This file and the copy in wp-content/plugins/ was added 2009 to prevent directory browsing even when the server allows that. This isn’t really a security feature, except in the sense of security by obscurity, but there might be files not everyone wants to see published or indexed by search engines. A better solution is: turn … Read more
Make sure you backup everything then: Move the content of /dir one level up, make sure you move hidden files as well (I care about the .htaccess file and maybe a .git folder) Download Search & Replace for WordPress, upload it to your server Access it with the url: http://www.xclo.co.uk/searchreplacedb2.php Follow the instructions, in brief, … Read more
I recommend reading up on the site_url() function. Take a look here: http://codex.wordpress.org/Function_Reference/site_url and specifically, read the difference between: site_url() & home_url() Then you could look at parse_url() or ABSPATH as suggested before by @NickJAB
Since you want to test out your existing(local) site on the server; you have done the right thing as far as I can see on pastebin except for 1 thing On step 10 – you replaced all occurances of “localhost” with your servername. Instead you should have replaced it with servername/directoryName. If you still have … Read more
Found the solution… the problem was due to placement of the conditional statement in the wp-config.php file. It needed to be inserted before the require_once(ABSPATH . ‘wp-settings.php’); line near the bottom of the default config file, otherwise the constants are already defined and cannot be redefined. So final section of the wp-config.php file now looks … Read more
Make sure you followed all these steps. It sounds like the .htaccess file was not updated correctly.
Your problem is that if you want to switch theme you have to do it very early, in fqact, the latest action you can hook for that task is setup_theme that is fired before the theme is actually loaded, so – first of all – if you want to change the theme you should use … Read more