|
zcsiteadmin
|
March 17, 2023 at 10:52 am
Hi,
I was part of the forced update yesterday, and today received numerous complaints from users saying they couldn’t access the system to manage events or even view registrations.
After a couple hours of trial and error, I discovered that now the “edit_posts” option must be enabled for everyone’s role, even if they have no authority to create anything otherwise.
|
|
Tony
|
March 17, 2023 at 12:20 pm
Hi there,
I was part of the forced update yesterday,
Forced update? We have not pushed out a forced update, infact we have chosed NOT to support auto updates within EE4 for a long time (and still don’t) for multiple reasons but in short, we can’t force any updates on EE.
We show you an update is available and your free to update when ready.
I discovered that now the “edit_posts” option must be enabled for everyone’s role
This I’ve not seen but I’m more than happy to investigate.
What capabilities do/did you have on the role?
|
|
zcsiteadmin
|
March 22, 2023 at 10:33 am
I have seen other posts regarding this (one example is titled Website Down after updating DB). It was a forced WordPress db update, not an Event Espresso update. Since the page came back up, things have been less than stellar on the experience end. But, I suppose this is a WordPress case rather than an EE case… I’ll close.
|
|
zcsiteadmin
|
March 22, 2023 at 10:34 am
This reply has been marked as private.
|
|
Tony
|
March 22, 2023 at 11:13 am
I have seen other posts regarding this (one example is titled Website Down after updating DB).
This one?
https://eventespresso.com/topic/website-down-after-updating-db/
Thats an EE4 migration, so an EE4 specific database update. I guess you could call those ‘forced’, but EE4 needed to be updated for that migration to need to happen.
Since the page came back up, things have been less than stellar on the experience end.
What has been happening? I’m more than happy to investigate if you can add some details.
But, I suppose this is a WordPress case rather than an EE case… I’ll close.
Possibly, although maybe not. We really need more details on what is happening to say more.
—-
WRT your private post, is that happening within the Event Editor?
Are you on visual or text/html mode?
It could be an issue with WordPress, a conflict with another plugin or an issue within EE itself (although I’ve not had any other reports of it).
|
|
zcsiteadmin
|
March 22, 2023 at 4:02 pm
This reply has been marked as private.
|
|
zcsiteadmin
|
March 22, 2023 at 4:19 pm
This reply has been marked as private.
|
|
zcsiteadmin
|
March 22, 2023 at 4:23 pm
This reply has been marked as private.
|
|
Tony
|
March 22, 2023 at 5:41 pm
For the original issue – I’m on EE 5 and WordPress 6.1.1. Last week when I was logged in and about to add an event, a message popped up which said it was putting my site in maintenance mode until I updated the database.
But that can only happen if you updated Event Espresso, so you ran updates on plugins first?
If you updated Event Espresso then yes, it needed to update the database to match the latest schema. That’s not a forced update as we didn’t ‘push’ the update to you, you updated the plugin and it ran its migration script.
Hmm, with regards to the HTML on a single line, I’m not getting that on the event editor:
https://monosnap.com/file/tWfIBzzYiZztbnBClh94C5VxUj0tIW
Or the message editor:
https://monosnap.com/file/RznCfyEXlP8SX35kuF0Mfhu0XLN9T4
When editing either of those, if you open up your Browsers dev tools and look in the console section does it show any errors from Event Espresso?
|
