WordPress Plugins and Themes

Urgent: Catchable Fatal Error, site down

23 Replies ·

  1. Hi all,

    Our website uses Stargazer with a child theme. All has been very happy for several months, but today the site went down and all I have is this:

    Catchable fatal error: Object of class WP_Error could not be converted to string in /home/usjabiru1/public_html/wp-includes/default-constants.php on line 101

    A few days ago WP did an automatic update. I wonder if the plugins are updating and one of them went wonky on me. Our phpbb forum, usjabiru.com/forum, is working fine, but I can’t access the rest of the site, including wp-admin.

    Any idea what this means?

    Thanks!
    Katie

  2. rv3flyer

    Thanks Justin!

    The site is back up now. I went into cPanel to start deleting plugins. I deleted the ones I knew I wasn’t using or weren’t important, which didn’t mean much because they weren’t activated anyway. I was nervous about deleting any more plugins and having to redo my sidebars and slide shows, so I did a Google search on how to deactivate plugins from cPanel, and I got this: http://support.hostgator.com/articles/specialized-help/technical/wordpress/disableenable-all-wordpress-plugins-via-the-database

    So I started doing that. When I accessed wp-options database through phpMyAdmin, I noticed that Line 1, siteurl, had this text string: O:8:”WP_Error”:2:{s:6:”errors”;a:1:{s:30:”wpdb_get_table_charset_failure”;a:1:{i:0;s:0:””;}}s:10:”error_data”;a:0:{}}

    I replaced that with the real URL for the site, and now it’s back up. So, the question is, why did that happen in the first place?

  3. Justin Tadlock

    It’s hard to say why that happened. That’s why I had suggested deleting plugins. If some plugin was filtering a hook and accidentally returned a `WP_Error` object, that may have been saved. Or, there may be some other reason like a bug in WP.

  4. David

    Yes, your site is down. If you have access to it with FTP, you can pull down a copy before deactivating plugins or whatever.

  5. rv3flyer

    Thanks for the heads up– Tonight I went into WP-Admin and deleted the rest of my unused plugins and updated the ones I do use. One of them, Meta Slider Pro, gave me a failed update due to an unspecified error. So I deactivated it. Hoping that’s the bad egg.

  6. rv3flyer

    Still giving the error. I went to GoDaddy support and the best they came up with was to subscribe to their Sitelock security program for $84/year and that “might” point to the problem. Do you guys have any experience with that?

  7. David Chandra

    first thing you need to do is to backup everything.

    second. you need to get your priority.
    site down vs. deactivate plugin.

    so, delete all your plugin (you have the backup anyway).
    fix the site url db.
    if the problem is gone, then it’s one (or more) of your plugin.

    if the problem still exist
    switch to default theme.
    if the problem is gone after you switch theme. then it’s your theme.

    if you still have the problem.
    delete your wordpress files get a fresh files from wp.org and install.

  8. rv3flyer

    OK, well now I don’t feel so bad for bugging you guys on this Theme forum– After deactivating all the plugins yesterday afternoon, the problem is still here, so I’m moving on to investigating the theme. Switched to Twenty Fourteen for today.

  9. rv3flyer

    The Twenty Fourteen theme stayed up for 24 hours… so it’s theme related. My child theme based on Stargazer is very simple, with some code for the company logo in the header and a few lines for the Meta Slider slide show–the same plugin that wouldn’t update due to an error a few days ago. So I deleted the slider code and relaunched with my child theme. Plugins still deactivated and fingers crossed.

  10. rv3flyer

    Child theme went down within a few hours. Going to Stargazer stock theme.

  11. rv3flyer

    The stock Stargazer theme is working. Can you tell me what’s wrong with my child theme that could cause the error? Here it is in its entirety… not much here.

    /**
     * Theme Name: My Child
     * Theme URI: localhost
     * Description: My attempt at a properly designed child theme for Stargazer
     * Version: 0.1
     * Author: Katie B
     * Author URI: 
     * Tags: 
     * Template: stargazer
     */
     
     @import url('../stargazer/style.css');
     
    #site-title a {
    	display: block;
    	width: 400px; /* Width of image. */
    	height:  100px; /* Height of image. */
    	background: url('images/headerlogo.jpg') no-repeat 0 0;
    	text-indent: -9999em;
    }
  12. Norm

    I don’t know if this is causing your problem but you don’t need

    @import url('../stargazer/style.css');

    in your child theme.

  13. David

    Nice site (last time I took a look it was down).

    I don’t see anything in your style sheet that would cause the problem you were having. It is still a mystery.

    If it were me, I would probably re-enable the child theme … but you could try one, by one, turning on the plugins also.