Update Broke Events Calendar (White Screen)

[Ken Eastwood]

Hi,

Just updated The Events Calendar from 3.10 to 3.10.1 on a staging site, before updating the live site. Everything worked fine before. Update has resulted in white screens on all events pages.

Have tried updating the permalinks, enabled debug (no error message) and deactivated all other plugins. Oddly, I’ve even deleted the plugin and installed a copy of 3.10 and the problem remains.

Any ideas or suggestions?

Ken

[George]

Hey Ken,

Sorry for your problems here – staging sites are great though, right? Glad you found this problem on that and not your live site…

First, I’m curious if you can clarify this bit of information:

Update has resulted in white screens on all events pages. Have tried updating the permalinks […]

So, just to be clear, only web pages at /events/-type URLs on your site show the white screen? And your admin works fine, other front-end pages like your blog posts work fine?

Next, I’m curious: how is your staging site hosted? Do you use WP Engine, for example, and use their default staging site feature? Do you use the “out-of-the-box” staging site provided by another host, perhaps?

Or are you running your own server(s), and your own staging one?

I’m just curious because it seems there is a problem, at core, with the server itself. Some weird caching or permissions issue, for example. The reason I suspect this is because of what you wrote here:

Oddly, I’ve even deleted the plugin and installed a copy of 3.10 and the problem remains.

It’s hard to say that with much confidence though – definitely an odd issue, let us know about some of the information requested here and we’ll take things from there, hopefully we can sort this out quickly for you.

And again, thanks for trying on a staging server first! 🙂

Cheers,
George

[Ken Eastwood]

Hi George,

Thanks for the reply.

Admin is working fine. It’s just the events calendar page and all other events related pages that are blank.

I set the staging site up myself in a folder beneath public_html i.e. a standalone instance of WordPress. We do this for most of our client sites and yes, it’s very useful (lesson learned the hard way)! We use Heart Internet for hosting.

I can’t see anything else wrong. We do use the WP Rocket cache plugin but tried deactivating.

Very strange!

Cheers,

Ken

[George]

Hey Ken,

Okay, thanks for the information here. I think a permissions reset might be in order – if you don’t know how to do this, you can contact your webhost support to do it, it’s usually a super-quick change for them to make.

You’ll want your WordPress installation directory to have its permissions set to 755, recursively, and be owned by the web server.

Send that above sentence over to your web host, or reset the permissions to that yourself if you’re able to – that could be the problem.

Thanks,
George

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts