WordPress 3.0 Problems And Their Solutions

WordPress 3.0Earlier we saw the fix for WordPress Error – Headers Already Sent Warning Problem and also WP Super Cache Content Encoding Error. Now we are going to discuss about the common problems and solutions in the much awaited WordPress release, WordPress 3.0, which released last week and reached maximum of downloads. WP 3.0 had several fixes and new features, but unfortunately some of the themes were not compatible with WordPress 3.0 and famous Thesis was one amongst them I believe.

#1 – Problem : Custom File Editor Issue in Thesis 1.7

Error :

Fatal error: Call to undefined function use_codepress() in /home/content/46/5420546/html/wp-content/themes/thesis_17/lib/admin/admin.php on line 42

Solution :

Just follow these steps and please don’t forget to keep a backup. Please!

  1. Connect to your webhost using FTP Client or CPanel File Manager. I recommend FTP Client, and preferably FileZilla.
  2. Go to the location mentioned in the error message

Example : wp-content/themes/thesis_17/lib/admin/

  1. Download admin.php to your system and open it using a file editor. I recommend NotePad++.
  • Now go to the line 42 (where the error is) and add two forward slashes before it and make that as a comment.

  • Example : //if (use_codepress()) add_action('admin_print_footer_scripts', 'codepress_footer_js');

    1. Now upload the updated admin.php to the wp-content/themes/thesis_17/lib/admin/ and that’s it!

    Now you can use the Custom File Editor without any issues, but you’ll unfortunately miss syntax highlighting feature. Hope the next version of Thesis will solve this problem!

    Source : http://www.letsgeek.net/2010/06/thesis-1-7-custom-file-editor-error-wordpress-3-0/


    #2 Problem – Stuck in Maintenance Mode after failed plugin upgrade

    Error : "Failed to create directory /public_html"

    Now the whole site even the /wp-admin just shows this message:

    “Briefly unavailable for scheduled maintenance. Check back in a minute.”

    Solution :

    Check this WordPress Forum Thread : http://wordpress.org/support/topic/411803


    #3 Problem – Fatal Error on Upgrade, Allowed memory size exhausted

    Error : Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2356995 bytes) in /home1/tampamas/public_html/wp-includes/http.php on line 1331

    Solution :

    Check this WordPress Forum Thread : http://wordpress.org/support/topic/298403


    #4 Problem – Some Plugin Problems

    Plugin Names : Podcasting Plugin by TSG, HeadSpace2 and Event Calendar.

    Solution :

    Check this WordPress Forum Thread : http://wordpress.org/support/topic/411649


    #5 Problem – My Theme is not compatible with WordPress 3.0!

    Some Themes : Themes like Atahualpa, Comfy Magazine and so on are getting errors.

    Solution :

    Make your theme compatible with WP 3.0 : http://millionclues.com/problogging/wordpress-tips/make-your-theme-wordpress-3-0-compatible/


    #6 Problem – WordPress 3.0 multi-site multi-domain problems.

    Problem 1 : I can’t load page URLs except when using ?p=xyz permalinks

    Problem 2 : The new themes I installed and activated on the main WP 3.0 site do not show up on separate domains

    Problem 3 : I cannot access Plugins on separate domains

    Problem 4 : New users are not visible on separate domains

    Solution :

    WordPress 3.0 multi-site multi-domain problems and solutions : http://blog.mixu.net/2010/05/31/wordpress-3-0-multi-site-multi-domain-problems-with-solutions/


    #7 Problem – Adding images to the post

    Solution :

    Check this WP Support thread : http://wordpress.org/support/topic/411940


    #8 Problem – WP3.0 Media Uploader “Unable to create directory”

    Error :

    “test.jpg” has failed to upload due to an error
    Unable to create directory /usr/local/www/domainname/www/blog/wp-content/uploads/2010/06. Is its parent directory writable by the server?

    Reference :

    Check this WP Support thread : http://wordpress.org/support/topic/414052


    #9 Problem – After upgrade- Unwanted code at the top of my page

    Error :

    ", $count2 {$name2}s"; } } echo $output; } } $elixir = new Elixir(); ?>lixir(); ?> ", $count2 {$name2}s"; } } echo $output; } } $elixir = new Elixir(); ?>e(__FILE__).'/'); // Get everything else require_once(ABSPATH.'wp-settings.php'); ?>

    Solution :

    Check this WP Support thread : http://wordpress.org/support/topic/414141


    #10 Problem – 3.0 UPGRADE Fatal error: Call to a member function add_rewrite_tag() on a non-ob

    Error :

    Fatal error: Call to a member function add_rewrite_tag() on a non-object in /home/content/u/r/b/urbaneco/html/wp-includes/taxonomy.php on line 289

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/411455


    #11 Problem – Admin permission error after 3.0 upgrade

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/413565


    #12 Problem – Upgrade to WordPress 3.0 Shows Broken Backend And No CSS Front Page For New Site

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/412083


    #13 Problem – Cannot save posts in 3.0 – get error – Warning: Cannot modify header information

    Error :

    Warning: Cannot modify header information - headers already sent by (output started at /home/gototenn/public_html/wp-config.php:83) in /home/gototenn/public_html/wp-includes/pluggable.php on line 890

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/411601


    #14 Problem – WordPress 3.0 Multiblog Enabling Problem and Solution

    Solution :

    WordPress 3.0 Multiblog Enabling Solution : http://xpressabhi.com/wordpress-3-0-multiblog-enabling-problem-and-solution/


    #15 Problem – WordPress upgrade overwrites my custom theme

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/413368


    #16 Problem – No wysiwig editor after upgrade to 3.0

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/413658


    #17 Problem – After update to WP3 my RSS link is not working

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/411879


    #18 Problem – Blank Page After 2.9.1 to 3.0 Upgrade

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/412752


    #19 Problem – Problem with single_cat_title after 3.0 upgrade

    Solution :

    Check this WP Support Thread : http://wordpress.org/support/topic/412233

    Did you encounter any one of these errors? Do you any other fix? Please share it in the comments!

    WordPress Error – Headers Already Sent Warning Problem

    Yesterday I almost became tensed. Some tutorials on the net are really lame! 😛 I trusted a site and applied that tutorial directly on my blog, and the result became sh*t. I highly recommend you to try tutorials on a demo blog rather than on your primary site or blog.

    Yesterday I came across this unique WordPress error titled “Cannot modify header information – headers already sent by …” [Without Quotes]

    Though, this tutorial is 99.9% perfect, I recommend you to backup all your theme files before implementing this tutorial. Happy Blogging!

    I’ll tell you what mistake I did and how to resolve that.. 8)

    Description :

    You get a warning message on your browser that says:

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

    Example :

    Warning: Cannot modify header information – headers already sent by (output started at //home/htdocs/wordpress/wp-config.php:1) in /home/htdocs/wordpress/wp-login.php on line 12

    WP-Error-close

    Reason :

    The reason is simply simple. It is usually because there are spaces, new lines, or other garbage before an opening < ?php tag or after a closing ?> tag, most probably in wp-config.php. It may also occur in other files too, so please check the error message. Many editors are adding additional blanks (spaces) and empty lines at the end of a file when you edit it.

    Solution :

    The best solution I would say is to replace the corrupted file with the file you have in your backup. You can also try the following alternative steps!

    #1 – Download the file mentioned in the error message.

    #2 – Now open that file using a really good Text Editor. It should be a plain text editor. I highly recommend Notepad++ or TextWrangler.

    P.S. Don’t risk. Avoid Notepad, WordPad and even MS Word.

    #3 – Now check that the very first characters are < ?php and the very last characters are ?>

    Most Important!

    You should save your file either as ANSI/ISO-8859 or as Unicode without BOM. Don’t ever save in normal format.

    Have you ever faced this problem? Do you any other solution for solving this?