Go with the easiest alternative of all: do nothing. No, really: WordPress itself handles redirects for renamed Post Titles. Edit Apparently, the retention of _wp_old_slug only happens for non-hierarchical objects. So, since Pages are hierarchical, they don’t get to enjoy the auto-magic slug redirection. Therefore, for static Pages or other hierarchical post objects, I would … Read more
The solution: I pasted the block of Mutisite code below the “That’s all, stop editing! Happy blogging.” line. I’d installed multisite so often that I didn’t pay attention to that part. So if you ever think you’ve installed multisite correctly but the My Sites button never appears, you’ve pasted the definitions too far down in … Read more
You need to set these too: define(‘AUTH_KEY’, ‘put your unique phrase here’); define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’); define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’); define(‘NONCE_KEY’, ‘put your unique phrase here’); define(‘AUTH_SALT’, ‘put your unique phrase here’); define(‘SECURE_AUTH_SALT’, ‘put your unique phrase here’); define(‘LOGGED_IN_SALT’, ‘put your unique phrase here’); define(‘NONCE_SALT’, ‘put your unique phrase here’); Please … Read more
WordPress site front page fails to load in IE
From a stackoverflow response: CURLOPT_SSL_VERIFYPEER checks that the remote certificate is valid, i.e. that you trust that it was issued by a CA you trust and that it’s genuine. CURLOPT_SSL_VERIFYHOST checks that the cert was issued to the entity you wanted to talk to. To compare it to a real-life scenario, VERIFYPEER is like checking … Read more
Does WP suppresses .htaccess if permalinks are disabled?
It seems unorthodox but I added my user to the _www group: $ sudo dseditgroup -o edit -a ‘whoami’ -t user _www Finally, I gave write privileges to the group: $ sudo chmod -R g+w /path/to/dir That seems to work, but like I said seems like a weird solution to add my user to the … Read more
This is going to sound crazy, but the following worked… I put the content in the following directory: /var/www/myexamplesite.com/public_html (and created log/ as well) Along with the following entry in httpd.conf <VirtualHost *:80> ServerAlias www.myexamplesite.com myexamplesite.com DocumentRoot /var/www/myexamplesite.com/public_html ServerName www.myexamplesite.com # Log file locations LogLevel warn ErrorLog /var/www/myexamplesite.com/log/error.log CustomLog /var/www/myexamplesite.com/log/access.log combined <Directory /var/www/myexamplesite.com/public_html> <IfModule mod_rewrite.c> … Read more
Impossible to guess, that’s certainly not a native WP behavior. If the requests are indeed being made by WP’s API you could hook into it and log what is happening to have more insight into the issue. pre_http_request should be a fitting hook everything of the kind passes through, as far as I remember.
Server stressed by /feed