WordPress problems I’ve had to fix

From time to time WordPress develops a hiccup or minor problem that I have to fix. It is usually during an upgrade of a plugin, theme or WordPress itself or during the installation of a brand new plugin or theme. Here are a few how to’s on fixing WordPress problems…

PCLZIP_ERR_BAD_FORMAT

The error can be solved by downloading this new http.php file from official WordPress site and over writing it on your current file.

http://core.trac.wordpress.org/export/11450/trunk/wp-includes/http.php

If you cannot upload this file to the /wp-includes/ directory theny our problem is that you have exceeded your disk quota. Delete some error logs and backup files or get your host to increase your quota.

WordPress Problem Upgrading Plugins, Theme’s or Core Updates

You may get this error if you try to install or update a theme or plugin, or whilst installing a core update directly from wordpress admin area


Warning: ftp_mkdir() [function.ftp-mkdir]: /public_html/wp-content/plugins/plugin-name/: Permission denied in /home/public_html/wp-admin/includes/class-wp-filesystem-ftpext.php on line 240

Could not create directory. /public_html/wp-content/plugins/plugin-name/

Plugin Install Failed.

or

Downloading update from http://wordpress.org/wordpress-2.8.4.zip.

Unpacking the update.

Could not copy file: /public_html/wp-content/upgrade/wordpress-2.8.4/wordpress/wp-comments-post.php

Installation Failed

Possible Solution 1:

Change the permissions for plugins, themes and upgrade directories to 777. Remember to change  permissions back to 755 when you are done installing.

Possible Solution 2:

Make a note of the plugins you have Activated, Deactivate all of them and then see if you can upgrade. If you can then reactivate all your favourite plugins.

Possible Solution 3:

Clear your upgrade directory. This sometimes seems to help.

Login issues after an upgrade to WordPress 2.8.1 & 2.8.4

After automatic upgrade I tried to login and got a plain white screen. To fix I logged onto my site via FTP then renamed the plugins folder and created a new empty plugins directory.

  1. Make a note of all the plugins on your site that are active
  2. Login to your site via FTP
  3. Find the “plugins” directory under wp-content and rename e.g. “plugins.day”
  4. Create a new directory called “plugins” which is empty and will trigger WordPress to deactivate all plugins
  5. Login and view plugins, all should be deactivated
  6. Do the reverse of steps 3 & 4, delete “plugins” then rename “plugins.day” to “plugins”
  7. Back to Plugins and activate plugins, preferably one-by-one

WordPress Fatal error: Allowed memory size of 33554432 bytes exhausted

  1. Download, backup and then open: wp-settings.php in wordpad/notepad or another editor
  2. Find define(’WP_MEMORY_LIMIT’, ‘32M’);
  3. Change 32M to 64M :   define(’WP_MEMORY_LIMIT’, ‘64M’);
  4. Save and then upload and voila! the problem should be fixed

Occasionaly this will not solve your problem and you’ll need to up your php.ini memory limit.

http://perishablepress.com/press/2008/02/17/wordpress-error-fix-increase-php-memory-for-cachephp/

“Headers already sent” warning problem?

Description: You get a warning message on your browser that says:

Warning: Cannot modify header information – headers already sent by
(output started at…

Reason and Solution

It is usually because there are spaces, newlines, or other garbage
before an opening '< ?php' tag or after a closing '?>' tag, typically in
wp-config.php. This could be true about some other file too, so please check the file that gave you the error too (mentioned in the error message).

Useful and Helpful WordPress Pages

Installing WordPress
Upgrading WordPress

This entry was posted in hosting, troubleshooting, wordpress and tagged , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>