|
bigtomato
|
December 15, 2019 at 1:06 pm
Hello, it seems every time there is a major EE3 update, we have to go in and regenerate site permalinks, and we run a multisite, so it is tedious to say the least. Site admins cannot make any updates to pages or posts (or create new ones or do anything else) until we regen the permalinks. And they cannot regen the permalinks themselves because they no longer have the capability. Please see the image for the message they get. This doesn’t happen to super admins, only to admins. We’ve reached out to our host and they increased some variables but that didn’t fix it. thank you. 
|
|
bigtomato
|
December 15, 2019 at 1:10 pm
And this happened when we applied this update: event-espresso v3.1.37.17.P. The users get this message: “The link you followed has expired,” and a “Please try again” link which never works.
|
|
Tony
|
December 16, 2019 at 3:45 am
Hi there,
That error isn’t from Event Espresso, it’s actually from WordPress itself.
Have you tried updating any other plugins/themes on the network? Do you get the same error?
We’ve reached out to our host and they increased some variables but that didn’t fix it.
What exactly did they change?
Searching around the error seems to come from upload_max_size or/and post_max_size being set too low, my guess would be post_max_size.
EE3 is likely one of the largest plugins you have on your site and may well be the only one to trigger this.
If you go to Event Espresso -> System Status
Under ‘Server Environment’ what do you have for:
WP Max Upload Size
Server upload_max_filesize
Server post_max_size
The strange part is this only happening for super admins, I can’t see any reasons why wouldn’t also get that error currently.
|
|
bigtomato
|
December 16, 2019 at 11:43 am
Hi Tony, Here’s what we have under System Status:
WP Max Upload Size 10 MB
Server upload_max_filesize 200 MB
Server post_max_size 200 MB
WP Memory Limit 512 MB
Our host also changed the .htaccess to this:
php_value post_max_size 200M
php_value max_execution_time 300
Do you know what the max size in EE would be so we can adjust accordingly? Yes, strange on the super admin not getting the error…
thanks much.
|
|
Tony
|
December 17, 2019 at 3:14 am
Have you tried updating any other plugins/themes on the network?
Do you get the same error?
Those values are fine, you shouldn’t be hitting anywhere near those values.
The error message you included above, does that happen on every page in the admin? Can you and paste the link for ‘please try again’ here please, you ca remove the domain from the link if prefer and/or mark your post private so on EE staff can view it.
|
|
bigtomato
|
December 18, 2019 at 1:57 pm
Hi Tony, thanks. The error happen when site admins try to update just about anything: pages, posts, permalinks, download form attachments, etc. Here is part of the link with domain removed: /wp-admin/post.php?post=4389&action=edit
The frustrating thing is that when I set up a new test account on the site with duplicate admin privileges to the user, I don’t experience the error, but I have replicated it with other existing test accounts.
Look forward to your thoughts.
|
|
bigtomato
|
December 18, 2019 at 1:59 pm
And we also have multiple themes, and it happens on all so it doesn’t seem to be theme-related. We notice this happening whenever there is a major EE update, not with any other plugin.
|
|
Josh
|
December 19, 2019 at 3:36 pm
Hi,
For what it’s worth, Event Espresso 3 hasn’t had a major update in 4 or so years. There have been a few minor updates recently, as they were very minor fixes.
The errors are common to WordPress sites that do not have Event Espresso installed as well, however usually they’re only seen when trying to upload a file if hosting limits do not allow larger file sizes. Since you’re seeing this error while trying to update pages/posts and settings, it’s likely not an issue with maximum upload file size limits.
Have you checked your PHP error logs to see if there are any errors (not notices or warnings) when these errors are thrown?
One thing that could help, since you mentioned that a new user account isn’t affected, is you could change the Authentication Unique Keys and Salts in the wp-config.php file. What that will do is invalidate all existing cookies, and force everyone to log in again. If there are some corruption-related issues with the cookies, the new keys will help. You can get a new set of unique keys and salts from the wp.org secret-key service:
https://api.wordpress.org/secret-key/1.1/salt/
|
