• I had to ftp into my webhost, rename all my plugins, then go back through them. I found that tentblogger’s optimize db, memory limit, wanguard, and All-in-One Event Calendar by Time.ly are all broken, as is what appears to be almost all themes currently installed minus the old “wordpress classic”. Currently my site is up and running now with no plugins enabled. I will be re-enabling things, but no actual content is viewable in the slidingdoors theme and “wordpress classic” is UGLY plain! *sigh*. . . trying to find dark themes that will work with 3.9.2 now.

    All my sidebar content is visible in sliding doors, but the only theme showing actual content right now “wordpress classic”! I’m NOT happy!

Viewing 12 replies - 1 through 12 (of 12 total)
  • Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    What theme were you running before? Also, can you quote the error messages you saw?

    Thread Starter songdove

    (@songdove)

    No error messages, and I finally found a theme that works. The theme I was using was named in the post above already and I’ve contacted the theme developer asking if they intend to upgrade their theme to 3.9.2. As for the broken plugins, 3 gave me error 500 codes, the other gave me a 403 as it tried to find a probably now-outdated wp-admin/options. . . php file. My site is now largely up and running now, but it’s taken me 6hrs to get this far! Just trying to find one particular widget’s code and decide if I want the new theme’s home page or not. *shakes head*

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Ok, before proceeding, it would probably be best to rule-out any missed files or file corruption during the update.

    Try downloading WordPress again and delete then replace your copies of everything except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings. Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

    If you still have trouble with those plugins, time for a quick little discussion on error 500s, which basically amounts to, “We don’t know without the server error logs, so here are some common things to try.” 🙂

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins. If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Fourteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter songdove

    (@songdove)

    I’ve already been on the phone with my webhost. The error 500’s were coming from too many internal redirects in some cases, incomplete header information in index.php files in other cases, even after copying over fresh from downloaded 3.9.2 zip file. The ONLY way I was able to regain access to my site was to rename ALL plugin folders! Then it was a matter of re-enabling one by one until I found the four that continued to break the site.

    As far as themes go, even theme 2014 did not work in preview. None of the installed themes behaved for me except for the ancient “wordpress classic” and I wasn’t going to use that one! Finally I found a Tempera theme that works.

    We looked at the .htaccess file before I finally had to rename plugin folders to get into the site. Definitely a plugin issue this time round. My site is back up and running as I said already. Took me six hours but managed to get it up before this afternoon’s hootesuite plug for the e-course that I offer. *sweaty sigh*.

    Definitely not happy with this particular update!

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Does Twenty Fourteen work for you with the problem plugins disabled? If not, what error do you see when you visit your site after activating it?

    Thread Starter songdove

    (@songdove)

    I couldn’t even get 2014 to come up in the themes/live preview earlier today, but now it comes up for me in live preview. Makes me wonder more about the sliders theme I was using and it’s compability with the latest wp update. The only problem with switching themes so often is that this IS a live site. So I prefer to preview as opposed to activate.

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    Ok, but we do need to activate a different theme. It’s the only way to for sure disable the functions of the Slider’s theme to rule that out as a problem. You can do it during a low traffic period, you don’t have to do it now.

    Thread Starter songdove

    (@songdove)

    Ugh. . . either my typing is blurry, or you’re not reading everything I type. . . I already changed to another theme. I mentioned that six posts up in this thread. . . I thought you were asking me to change yet again. . . The hint before your last reply should have been “was using” because I’m not using the slider theme now. . . .

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    ok

    Thread Starter songdove

    (@songdove)

    Update that since changing themes, one of the four plugins came back. My calendar plugin, :-D! TinyMCE however is having similar problems to others reporting on that right now. Editing and creation are fine in the text tab.

    Hello songdove. Which calendar plugin was causing the conflict?

    Thread Starter songdove

    (@songdove)

    Hey _hoopla,

    The Calendar plugin nolonger worked with Sliding Doors theme after the upgrade to 3.9.2. The name of the plugin “All in one event calendar” by Timely.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘3.9.2 update broke several plugins and themes’ is closed to new replies.