GeoDirectory SupportWhite Screen/Site Crash on update – GeoDirectory Support https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/feed Thu, 05 Feb 2026 18:10:47 +0000 http://bbpress.org/?v=2.5.14-6684 en-US https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36772 <![CDATA[White Screen/Site Crash on update]]> https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36772 Fri, 10 Apr 2015 12:12:34 +0000 thebirdiemachine OK so I just updated the core and the plugins and now my site has a a totally white screen on the front end.

On the backend – if I try to navigate away from the page/screen I am on I get a white screen too.

Good thing this is my dev site because otherwise I would be freaking out.

My theme is X using Renew stack. How to fix this??? What is wrong here??? I first updated the core plugin then updated the extensions

You can check out my white screen here:

http://dev.muttmaps.com/blog/

Stacey

]]>
https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36774 <![CDATA[Reply To: White Screen/Site Crash on update]]> https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36774 Fri, 10 Apr 2015 12:52:57 +0000 Guust This is what I get on your homepage http://dev.muttmaps.com/ : “I’m sorry, your requested action is not allowed. If you have any questions, please contact the server administrator.”

FTP details and WP admin details please.

http://docs.wpgeodirectory.com/faqs/what-is-the-best-way-to-update-the-gd-plugins/

]]>
https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36776 <![CDATA[Reply To: White Screen/Site Crash on update]]> https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36776 Fri, 10 Apr 2015 13:07:24 +0000 thebirdiemachine https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36789 <![CDATA[Reply To: White Screen/Site Crash on update]]> https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36789 Fri, 10 Apr 2015 15:17:43 +0000 Simone Hello Stacey, the issue was not happening after the update, but you modified the db-language.php adding a wrong syntax in the string


__('Murrie\'s Mark', GEODIRECTORY_TEXTDOMAIN);

it needs only one

to escape the

'

, (I’ve edited that for you and your site is live) BUT you are highly recommended using the .po file instead of editing the core because all the modifications will be LOST when an update is being released.
Please follow the documentation here
http://docs.wpgeodirectory.com/translate-core/

]]>
https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36795 <![CDATA[Reply To: White Screen/Site Crash on update]]> https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36795 Fri, 10 Apr 2015 15:52:39 +0000 thebirdiemachine Simone,
Hi Simone,

Good to hear from you!

I did not modify the db-language.php – I don’t even know what that is (and you know that is true true true)

Having said that I the Murries mark thing has been a big problem since the beginning where the apostrophe was rendering as a / (I opened a few tickets on this a long time ago, the problem would go away then come back)

The site was fine until I did the update. I had the site up before the update and it rendered fine and was working.

Thank you for getting the dev site updated – but honestly there is no way I am can update my live site because I am pretty sure that the same thing is going to happen and I will not be able to fix it.

Stacey

]]>
https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36797 <![CDATA[Reply To: White Screen/Site Crash on update]]> https://wpgeodirectory.com/support/topic/white-screensite-crash-on-update/#post-36797 Fri, 10 Apr 2015 16:23:07 +0000 Simone Hi Stacey, I believe you did not edit it 🙂 But it looks so strange, also, if this is was something wrong, all of us should have encountered the same issue.
If you will have the issue on the live site, we well help you out to fix it, if you’re going to migrate the dev site into the live site, you are good to go since this is already been fixed

]]>