|
Atma
|
September 6, 2019 at 5:51 am
The weird thing is, some people don’t have an issue, others (maybe different browser?) do.
Then again one person didn’t have an issue yesterday, then had one today. While a third person had an issue starting two days ago.
The same problem already happened a month ago, then it was suddenly gone.
For the first time today someone even got an error message from their browser.
Please see screenshots:
https://www.dropbox.com/sh/4m3069msplpgfdx/AACBDxaDiJqn4b8mPKjchZdRa?dl=0
|
|
Josh
|
September 6, 2019 at 6:43 am
Hi,
First, the event’s description has some invalid html. There’s a closing </p> tag which has no opening tag. Here’s a screenshot from the source:
https://slack-files.com/T02SY781D-FN37V1Q4V-3e41c1b813
There may be other issues with the markup, and if you’re not sure how to fix, you can switch to the html editor on that event, and copy its contents, and run it though a validator like this one:
https://validator.w3.org/#validate_by_input
Secondly, your site’s version of Event Espresso 4 is out of date and needs to be updated. Can you update to the current version of Event Espresso 4?
|
|
Atma
|
September 6, 2019 at 8:52 am
Okay thank you, but this error effects all events. It must be something else if it affects all of them or no?
|
|
Atma
|
September 6, 2019 at 9:22 am
Yes, I think we will have to update. We have a lot of custom code in there, so I am a bit worried but it seems the best solution.
Can we upgrade to EE 4.9 with WP Version: 4.9.11 ?
|
|
Josh
|
September 6, 2019 at 9:34 am
You’ll lose your custom code if you update. So the first step is extract the custom code and put it into its own custom plugin.
As an aside, if you’re having issues like this on every event, then you could also check your custom code. Normally Event Espresso 4 doesn’t inject mismatched markup like that, but your custom code may be altering things.
Finally, yes, you can update to EE4.10 (that’s a 10 and 10 is more than 9) is compatible with WP version 4.9.11.
|
|
Atma
|
September 6, 2019 at 12:21 pm
We solved the issue thank you!
|
