I used to use Xampp but I decided to try Wamp for my new WordPress project. After installing WordPress on local machine and chaning Permalinks to Post Name in admin I suddenly started getting these errors:
The requested URL was not found on this server.
Don’t you just love it when such errors appear? I forgot how I solved this in the past projects but remembered it has something to do with
.htaccess. After Googling and trying out few solutions nothing worked until I realized that with Wamp you can enable mod_rewrite via WAMPSERVER Control Panel (you will find it in your tray).
So just click on
WAMPSERVER icon, then
Apache Modules and then scroll down to
rewrite_module and enable it. Restart Apache (or restart all services) and your permalinks will work.
Seems like qTranslate is not really updated anymore or at least it is updated very slowly. So when I updated WordPress to new version I got this message and qTranslate editor in admin was disabled.
The qTranslate Editor has disabled itself because it hasn’t been tested with your WordPress version yet. This is done to prevent WordPress from malfunctioning. You can reenable it by clicking here (may cause data loss! Use at own risk!). To remove this message permanently, please update qTranslate to the corresponding version.
I guess the easiest way is to just click on the link and it will probably enable itself. I googled it and it seems some people might have problems with that. So the solution that worked for most people is this:
wp-content/plugins/qtranslate/qtranslate.php file and change line 90 from
just save it and that’s it.
Of course if WordPress is updated to new version qTranslate will disable itself again. What you can do is enable it for all version by dynamically inserting current WordPress version, like this
qTranslate will now work for all (future) versions of WordPress.
Hint: You can find out your WordPress version on the bottom right in the admin or by opening a file
/wp-includes/version.php and checking the
$wp_version variable on the top.
Note: Do this on your own risk. It seems to work for most people but beware you might loose your data if something goes wrong. The safest way is to wait for author of qTranslate to update it but it seems this is not happening.
WordPress update stuck in maintenance mode
In some cases the message “Briefly unavailable for scheduled maintenance. Check back in a minute” doesn’t disappear after you update your WordPress, despite the update being successful. Even worse – you are locked out of admin because both admin and your site display this message.
How to fix the WordPress maintenance mode problem? The solution is simple. Use your FTP program to connect to your server and delete the
.maintenance file from your server (it is in the WordPress root directory, same as .htaccess). In most cases this will fix it. If the update did not finish then loginto admin and try to reinstall WordPress updates.
When you want to install or upgrade a plugin, WordPress will most probably display this message:
To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.
If you are on shared hosting you might not have this problem but if you are on a VPS or Dedicated server you will most probably get asked to supply FTP credentials every time you want to install or upgrade plugin or even WordPress. This can become an annoyance if you install plugins a lot so this is one of the first things I always fix when I install new WordPress site.
Here is how to solve it: open your
wp-config.php file (by default it can be found in your root WordPress directory) with text editor and simply add your ftp login information near the bottom of the wp-config.php file (just above the /** Sets up WordPress vars and included files. */ comment for example):
//*add your FTP credentials*
//*If you like and can use a SSL connection set this to true*
After you do this your won’t be asked for FTP credentials anymore. There are other solutions like settings permission with chown via shell or installing suPHP on your server but this one seems to be the easiest.
If the above fails for whatever reason you can comment the above code and try adding the following code in the
wp-config.php file,somewhere at the top:
define( 'FS_METHOD', 'direct' );
define( 'FS_CHMOD_DIR', 0777 );
define( 'FS_CHMOD_FILE', 0777 );
This forces files to be writable by the server. You should only use this if adding FTP credentials method fails.