Home > wsod intranet broken borked > "White Screen of Death"

"White Screen of Death"

Home › Forums › GovIntranetters › "White Screen of Death"

Tagged: 

Viewing 7 reply threads
  • Author
    Posts
    • 24 Nov 2016 at 15:43 #2693
      Luke Oatham
      Keymaster

      Hi Gavin

      V4.28 contains new support for child themes, which required some changes to how directories are referenced within the theme. This update may help. You’ll need to update theme and plugin files. Files have been removed from the theme folder, so you must overwrite the theme folder to ensure old templates are removed.

      You could try installing the default WordPress themes too – twentysixteen, twentyfifteen etc. as it looks like the installation is trying to default to these – just so that you can get back to the admin screen.

      I managed to bodge my installation when testing the child theme updates and got WSOD too. I had to edit the wp_options table in the database and reset entries where option_name is template, stylesheet and current_theme in order to get back to the admin screen.

      Let me know how you get on with the latest version.

      Luke

    • 25 Nov 2016 at 10:49 #2703
      Gavin McMenemy
      Participant

      Hi Luke,

      Thanks for the advice.

      Forced the installation back to TwentySixteen and I’ve got the admin pages back. One thing I’ve noticed is that all of the themes are missing their name. Instead I’m seeing “Theme Name”.

      I went ahead and activated govintranet – it was obvious from the picture which one it was.
      I’ve checked in the wp_options table and all template, stylesheet and current_theme are all set to govintranet.

      I suspect that there’s a DB issue somewhere but I am not sure what I should be looking for.

      The site looks mostly ok there’s some additional plugins we use which I need to chase down and reinstall so “mostly there”!

    • 7 Dec 2016 at 13:09 #2722
      Gavin McMenemy
      Participant

      Hi Luke,

      We’re still having issues here.

      Got the WSOD again today. As such I’m about to force the site back to twenty sixteen again. I’ve attached an image which I hope will illustrate matters.

      I’m not sure what the error is telling me. Clearly we have an issue where where a parent-child theme relationship has broken. Looking at the WP codex it suggests child themes should be in a separate folder but as I’ve not seen this behaviour with this theme can I assume that this is a red herring?

      Inside the themes folder I have 4 themes:

      Govintranet
      TwentySixteen
      TwentyFifteen
      TwentyFourteen

      and a dump of the govintranet-master folder from your zip.

      But looking at the Themes section for the site I can only see the active theme – not a list of all themes.

      What my gut tells me is that this is a DB issue but to be honest I am not sure where to start and accept I might be wrong.

      fyi: the version of Govintranet we have is the version from the last time we spoke (v4.29).

      Attachments:
      You must be logged in to view attached files.
    • 13 Jan 2017 at 15:35 #2841
      Gavin McMenemy
      Participant

      Hi Everyone,

      We’re really having issues here – can anyone provide a steer on my message above?

      If it’s easier doing a fresh install, does anyone know of a good way to port the content without porting whatever the bad settings might be?

    • 13 Jan 2017 at 17:36 #2842
      Luke Oatham
      Keymaster

      It feels like a muddle with the theme config in the database.

      You could try removing all themes except GovIntranet and installing the new TwentySeventeen theme and latest version of WordPress. WordPress should then try to default to a theme and will hopefully pick TwentySeventeen.

      The latest versions of GovIntranet (4.30+) handle child themes better, so I’d recommend updating theme and plugins.

      Please let me know how you get on. Do you have access to phpMyAdmin or similar?

    • 25 Jan 2017 at 16:49 #2865
      Gavin McMenemy
      Participant

      Hi Luke,

      Finally had a moment to check this and get back to you.

      So far so good.

      Notes: NO upgrade to WP. We just stayed on our current version 4.4.6.
      I downloaded the new version of your theme and Twenty Seventeen.
      I deleted Twenty Sixteen.
      (Admission: I didn’t realise that Twenty Seventeen required the new version of WP – oops!)
      I replaced the version of Govintranet we were using and used the latest version. At the time of writing this is 4.34.

      It works.

      ps.

      We could never get the searchform.php to work. So I’ve bodged a fix to force the search to return the correct permalink structure we’ve chosen.

    • 25 Jan 2017 at 20:30 #2866
      Luke Oatham
      Keymaster

      😁 that’s great news. Glad it worked eventually. Hopefully no data lost?

      I’ll take a look at the searchform.

    • 26 Jan 2017 at 09:07 #2867
      Gavin McMenemy
      Participant

      No, no data lost! I was dreading the idea of porting the data over to a new installation.

      As far as the search form is concerned:

      We’re using an installation on IIS (currently running Server 2008 r2).

        We have custom permalinks. (but they are nothing special)
        Our intranet url would be http://intranet.domain.com.
        The installation directory is \\server\inetpub\intranet
        What we’re finding is that the search doesn’t truncate the returned url properly.
        So I search for “ICT”, the default searchform returns intranet.domain.com/intranet/?s=ict
        Rather than intranet.domain.com/?s=ict

      Search is the only place we see this issue.

      To fix it I dug around a little in the wordpress codex and the [useless!] wordpress forums and found that I could “force” the correct string out of PHP.

      In searchform.php I found this: action=”<?php echo home_url( ‘/’ ); ?>”>
      Which I changed to action=”intranet.domain.com”>

      It works a treat. Although because it’s hardcoded I have to make the change if we change the theme or whatever.

      We’ve also inserted our own Login link to facilitate user’s signing in.

      Hope that’s of some use. Let me know if you want me to explain or expand anything.

  • Author
    Posts
Viewing 7 reply threads
  • You must be logged in to reply to this topic.