Support

December 4, 2017 at 3:19 pm

Hi there,

Can you provide more details please, what exactly isn’t working?

If you de-activate all other plugins and just have Event Espresso running, do you see the same problem? I’m using 4.9.1 on multiple test sites within any issues with the WP Editor so its likely EE is another symptom rather than the cause.

If you open up Chrome dev tools and look in the ‘Console’ tab when the editor isn’t working, do you see any errors there?

December 5, 2017 at 1:11 pm

Bad gateway is a server error and usually happens when your server doesn’t have enough resources to respond to the request.

We need much more details to be able to help you here, posting the error from ‘somewhere’ on your site, doesn’t really help.

So again, can you provide more details on what isn’t working with the editor?

Where are you getting 502 bad gateway?

Did you do this:

If you open up Chrome dev tools and look in the ‘Console’ tab when the editor isn’t working, do you see any errors there?

Any errors?

Have you check the servers error logs for any error from Event Espresso?

December 5, 2017 at 1:40 pm

I know what a 502 error means, but there is no way there is no correlation between everything working fine and everything breaking when ONLY EE4 Core is installed.

That isn’t what I said.

I said I can’t reproduce this on any of my test sites so it’s likely EE is another symptom rather than the cause (and I still stand by that), that doesn’t mean that’s definitely the case nor does it mean EE is definitely causing it.

So far, your the only person reporting any issues with 4.9.1 and we don’t know of any bugs in the latest version of EE that would cause any problems.

The problem with the above replies is each post only gives half the info, for example:

I just did try that and it still does not work. And yea, bad gateway
“Failed to load resource: the server responded with a status of 502 (Bad Gateway)”

There’s no mention of that being within the console, as I’m sure you are aware you can get 502 on any request so it could have been anywhere. As it’s in the console, it’s happening on a specific resource (or more) the server can’t load but that also isn’t included, so it’s pretty much a needle in a haystack right now.

I understand that in order to do a deep troubleshoot, you need more info. I posted this in hopes that you guys were aware of the bug and had a simple fix. As this is not the case, I will dig a little deeper.

I’m not trying to be awkward here and I’m more than happy to try and help find the problem (as is any other member of support), but we can only go on the info you provide which right now isn’t very much so I asked for more details. Even as a suspected bug report, the above wouldn’t be enough for us to narrow down the problem enough, especially without being able to reproduce.

Have you checked the server’s error logs? Any errors from Event Espresso there?

December 5, 2017 at 2:23 pm

Let’s start from the beginning, which specific editor are you using?

After logging in, what steps do I need to take to reproduce what you are seeing?

I assumed earlier your were referring to the WP post editor, but you may be referring to something else. So where exactly within WP do I need to go to view the problem?

December 5, 2017 at 3:03 pm

Ahh, ok. Now I can reproduce.

That’s the Theme Editor, same happens with the Plugin Editor.

The ‘WP Editor’ would normally be the post editor which is what I assumed you meant, but obviously not. We don’t need any additional details currently and have created a ticket to investigate further, we’ll update this thread with any news.

January 10, 2018 at 9:02 am

This is fixed in Event Espresso 4.9.54.