Support » Themes and Templates » WSOD on ANY theme change

  • Resolved pcvip

    (@pcvip)


    Anyone encounter this before?

    One of my sites has been in use for about six years. It’s time for a new look.

    I’ve chosen Themify.me’s new ULTRA theme, which is based on Themify’s builder (which honestly I don’t much care for, but that’s another story). In working through the transition, I’ve discovered that all of the builder’s settings get stored in the postmeta table (which means editing the settings or content created in it manually is all but impossible). OK, I get it, but that’s where it is.

    In the course of almost-ready-to-launch testing, we had occasion to flip the theme off and looking at the site’s behavior using 2015. And that murdered the site. Front end looked as making such a switch would make it look (expected), but back end when WSOD. Fixing it is simple; manual edit in the options table where it now says WP’s active theme is 2015 instead of Ultra.

    But of course, this is troubling, so test, test, test, and … same thing when I tried 2012. And 2014. And presumably anything else.

    I’ve even tried disabling caching because … you know … caching. Cycle/test/cycle/test … no change; SWITCHING THEMES BORKS MY SITE.

    Anyone have any clues what could be causing that and what to do?

    ONE CLUE (maybe):

    Not much caring for the manual SQL edit method of fixing things, I made my methodology “make sure you have an up-to-the-instant full backup of the database and drop all the tables and do a restore when it breaks.” And that’s fine, except, GET THIS: it breaks all widgets. IT DOESN’T CHANGE ANYTHING … it just makes me need to open the widgets back-end (just open it; I don’t make any changes) before any of them will display.

    Seriously … anyone?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    In working through the transition, I’ve discovered that all of the builder’s settings get stored in the postmeta table (which means editing the settings or content created in it manually is all but impossible). OK, I get it, but that’s where it is.

    So far so good.

    In the course of almost-ready-to-launch testing, we had occasion to flip the theme off and looking at the site’s behavior using 2015. And that murdered the site. Front end looked as making such a switch would make it look (expected), but back end when WSOD. Fixing it is simple; manual edit in the options table where it now says WP’s active theme is 2015 instead of Ultra.

    That part’s not good. When you get the 500 error does your server log say where the issue is? I mean, what PHP file is tossing the error.

    Hey Jan.

    There was no 500 error per se, although I supposes WSOD IS one, right?

    The fix turned out to be … get ready for this one … that a required plug-in which accompanies the theme (and which had been installed, internal to WP by following the instructions that popped up) wasn’t the correct version of the plugin.

    So the good news is that once the developer ‘fessed up and provided the correct version of the plug-in, this was automagically resolved. The bad news, of course, is that it leaves me speculating about how such an error could have snuck by in the first place. That said, Ultra is a new theme and it’s entirely possible I was the very first person to flip it OFF.

    Frustrating, though.

    My apologies for not remembering to come back in here and updating the case. PRESUMABLY whatever was wrong (other than the postmeta thing above, which I maintain is a very bad idea) is now OK.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WSOD on ANY theme change’ is closed to new replies.