There are many reasons this error can occur. Those two were the most frequent for me: Session-Cookie Open the Javascript Console by pressing F12 and click on the tab “Console”. If you see some error message that goes something like cookie_nonce it’s a session cookie problem. The problem solves by just completely logging out and … Read more
This would seem to be a “fault” of the way WordPress (the “server”) is reading the HTTP request headers. (If they are being read into an associative array without any normalisation then the comparison will naturally be case-sensitive.) This should arguably be “fixed” in WP. However, it’s possible to create a “workaround” in .htaccess and … Read more
It depends how you want to uniquely identify users. Some options to uniquely identify people might be the: The WordPress User ID. If people are logged in then using their WP User ID is a good option. The WordPress session ID. This is unique to the session; People will get a new session after some … Read more
“RSS” stands for “resident set size,” one way to measure the amount of memory used by a process in Linux. It does not refer to RSS feeds. This probably has very little to do with WordPress, and everything to do with the amount of RAM in your box and how much memory Apache is using. … Read more
The latest and greatest php version is always the recommended version. Seriously. All core devs use it when developing trunk. Only a few bother to test older php versions, as can be seen by the occasional ticket opened related to php4 or php5.x incompatibility. The same cannot be said by plugin authors, however… As you … Read more
For starters try Core Control plugin to see if scheduled tasks are accurately assigned. Scheduled posts will show up as publish_future_post > check_and_publish_future_post() with post’s ID as argument.
Of course you can optimize your servers like the hosting companies do, it just depends on how much skill you have and how much effort you want to take on. Here’s a community wiki that might give you an idea of what to consider doing: Best-of-Breed Features of a High-End WordPress Web Host? One thing … Read more
You should be able to just add your port 8888 under general settings wordpress/site url, or directly in your config.php. In your case that would be http://localhost:8888 . I don’t know how or what browseling is but a quick glance also shows they support ssh reverse tunnel proxy for localhost, which is another option.
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
http://codex.wordpress.org/Hardening_WordPress#File_Permissions / – The root WordPress directory: all files should be writable only by your user account, except .htaccess if you want WordPress to automatically generate rewrite rules for you. /wp-admin/ – The WordPress administration area: all files should be writable only by your user account. /wp-includes/ – The bulk of WordPress application logic: all … Read more