Somewhere in the core, URLs get absolutely pathed when put into the database. Why don’t you just load all your images from your staging server? Have the staging server hold the files while your local mirrors it. Add the following to your .htaccess to your local uploads folder and the contents are as follows: # … Read more
Install multi-site as subdomain setup. Do not use the sub-sites option. Go to Network Admin/Sites and select the site whose URL you want to change: Change the URL to the new domain. In your wp-config.php use define( ‘COOKIE_DOMAIN’, ” ); to be able to log in in both sites. You don’t need a plugin for … Read more
The two directories, where plugins can be located in line with normal mechanics are: wp-content/plugins wp-content/mu-plugins
I usually just avoid the issue entirely every time I create a new wordpress site: define(‘WP_HOME’, “https://wordpress.stackexchange.com/”); define(‘WP_SITEURL’, “https://wordpress.stackexchange.com/”); will cause wordpress to use root-relative urls for everything. Makes site migrations to other domains far easier. Ofc, if you access your site using a folder (eg. “http://<domain>/blog“) you could change them to: define(‘WP_HOME’, ‘/blog/’); define(‘WP_SITEURL’, … Read more
Add this to your wp-config.php: const JETPACK_DEV_DEBUG = TRUE; This makes it possible to use features on localhost that don’t require a connection to wordpress.com. See the announcement post on jetpack.me for the background. For your own plugins, learn that lesson: Do not rely on working outgoing connections. Respect your users privacy, and explain in … Read more
You can use wp-config.php to change the site url depending on where the site is accesed from, using $_SERVER[‘REMOTE_ADDR’]. Mine has something like this: if ($_SERVER[‘REMOTE_ADDR’] == ‘127.0.0.1’ || $_SERVER[‘REMOTE_ADDR’] == ‘::1’) { // accesing site from my local server define(‘WP_SITEURL’, ‘http://localhost/mysite/’); define(‘WP_HOME’, ‘http://localhost/mysite’); } else if (strpos($_SERVER[‘REMOTE_ADDR’],’192.168.0.’) !== false) { // accesing site from … Read more
In my case, it was simply the SITE URL left blank in Settings -> General. I filled it with my site URL, and everything started working again. I found out by enabling WP_DEBUG in wp-config.php, and I got this error: “Notice: Undefined index: host”
You could also try this. In IIS manager Go to Application pools and choose the one used by your WordPress Blog. Right Click and choose Advanced Settings… Change the Identity to LocalSystem Click OK to save changes. Then on Sites, Choose your WordPress Blog from the sites list Right Click on it and click on … Read more
As of JetPack 2.2.1 there is now a local development/debug mode. http://jetpack.me/2013/03/28/jetpack-dev-mode-release/ use: define (‘JETPACK_DEV_DEBUG’, true); in your wp-config and you should have access to any modules that don’t require a connection to function. Update, since around v3.3 another local development trigger was added via filter instead of define. Latest is now here: http://jetpack.me/support/development-mode/ Development … Read more
I usually do this when that happens (only locally, not for production) : chown -R nobody:nobody /path/to/wordpress