Hi, trancefixed, & welcome. Have you tried renaming your parabola theme folder to something different, i.e., parabola1? Now–don’t panic, because your blog will stop working at that point, but if you’re able to log in, you can then change it via your dashboard. I don’t know if your site is set up for automatic updating, but, if so, perhaps something broke when that happened?
Please let us know if that did or did not help, ok?
Hi Jackie
Thanks for the suggestion.
I renamed the parabola theme folder to parabola1 but I still can’t log in and now – as you predicted – my website won’t load either (White screen only).
I believe WordPress is / was set up for automatic updating.
I’ve checked the Parabola theme page and can’t see anyone else who has had this problem recently.
Any ideas what to try next?
TranceFixxed, can you use ftp (& hopefully secure ftp) or your hosting control panel to re-upload your WordPress files? I guess I’m just wondering if an automatic update didn’t go so well & some files may have become corrupted?
Hey TranceFixxed,
Usually when you get just a white screen, there is an error, but it is not being displayed.
The reason for this is because the display_errors directive in your php.ini file is set to off. Turn on display_errors by editing your php.ini file and replacing this:
display_errors = off
With this:
display_errors = on
Once the you can see the errors on your page start by seeing if the error is caused on the server end or is something within wordpress.
If it appears to be something that can be fixed, contact your web hosting company. They will help you.
If it’s on WordPress, then your best bet might be to restore from a backup. Again, your web hosting company can help you there.
Hi all
For the benefit of anyone else having this problem – I eventually fixed this by speaking to my Web Host who first increased the server memory allocated to my site and then made “corrective changes in the server’s Mod_security setting”.
They declined to provided any more information about what they changed but it sounds like the corrective action is to speak to your web host.
Thanks all for your help
Cheers Tim