|
rpicker
|
August 5, 2024 at 3:45 pm
Hi, we’ve installed Event Espresso on a new website that just launched.
In the WordPress dashboard after the plugin is installed and activated there’s no Event Espresso section in the menu.
When I copy and paste the URL to access some of these dashboard pages it says:
Sorry, you are not allowed to access this page.
Weirdly enough when I went to edit a user account I saw this message:
As part of the process for updating Event Espresso, your database also needs to be updated. Event Espresso is in COMPLETE MAINTENANCE MODE (both WordPress admin pages and front-end event registration pages are disabled) until you run the database update script. Visit the Maintenance Page to get started, it only takes a moment.
That message doesn’t show up anywhere else in the dashboard.
When I click on “Visit the Maintenance Page to get started” it just takes me to a blank page that says:
Sorry, you are not allowed to access this page.
How can we get this fixed?
I’ve already tried changing themes and disabling all plugins and I can confirm it’s not a theme or plugin conflict.
I’ve also tried changing our PHP version on our hosting (SiteGround) to all the available different versions and that doesn’t make a difference either.
Thanks in advance for any help with this.
|
|
Tony
|
August 5, 2024 at 6:11 pm
Hi there
If EE is in maintenance mode (which the messaging you are getting suggests it is) then it means it has detected older EE data.
But your saying this is a new site?
Was the database copied from a previous version of the site?
Has EE been previously installed and if so, do you know which version number of Event Espresso it was?
|
|
rpicker
|
August 6, 2024 at 10:02 am
It’s a brand new site however when installing EE I accidentally installed version 3 first, then realized right away that it was an older version so I removed the plugin and installed the latest version.
Currently Version 5.0.21.p is installed.
The new site uses a brand new database and WordPress installation.
|
|
rpicker
|
August 6, 2024 at 10:26 am
Installing an older version of the plugin and then updating from that fixed the issue so we’re all good now.
|
|
Sam
|
August 6, 2024 at 10:56 am
We are glad you got that working now. Please feel free to ask if you have any other questions.
|
