|
bchilders
|
February 5, 2013 at 5:55 pm
When I try to add new recurring events manually, I get the following message “Sorry, there was a security error and your event was not saved.”
|
|
Dean
|
February 6, 2013 at 5:27 am
Hi
Is this occurring with the latest version 3.1.30.4?
Do you have any outdated templates in uploads/espresso?
|
|
bchilders
|
February 6, 2013 at 8:50 am
Yes this is occurring with version 3.1.30.4. The uploads/espresso/templates folder is empty.
|
|
ndaniel
|
February 6, 2013 at 9:14 am
I am also getting this error when trying to modify an existing recurring event or series.
|
|
Jonathan Wilson
|
February 7, 2013 at 10:50 am
Hey guys,
Please make sure all of the add-ons are at their current versions.
If you have 3.1.30 (or greater), you should now have a System Status page in your Event Espresso menu, which displays a list of all your plugins.
|
|
bchilders
|
February 8, 2013 at 5:37 pm
All of the add-ons are up to date and I am still having the same issue. I just updated to 3.1.30.5 and still no change. Same problem..
|
|
Seth Shoultes
|
February 8, 2013 at 6:46 pm
Hey guys, this is not related to the templates at all. It is in the event editor within the admin. It has to do with nonce security check we added this version. Not sure why it would fail on this though. I’ll look into it.
|
|
Seth Shoultes
|
February 8, 2013 at 11:44 pm
Weird. I can’t seem to reproduce this. But I found that I can’t add another date to a manually created recurring event. Not sure if this was an existing bug or not.
|
|
bchilders
|
February 9, 2013 at 10:37 am
That is exactly the problem that I am having. It is weird because I did not have this problem before. I was able to extend the date range for the recurring event, but am not able to add any new dates without getting the security error. I was able to remove dates.
|
|
Jonathan Wilson
|
February 12, 2013 at 5:11 pm
Hello,
I am sorry for the delay. I am testing this and will turn in a ticket for our developers once I’ve recreated the issue. I will keep you posted.
|
|
Jonathan Wilson
|
February 13, 2013 at 10:17 am
Hello again,
I am able to reproduce this error. What version were you running before this started happening?
|
|
Leland Zaremba
|
February 13, 2013 at 2:27 pm
Seeing this problem as well. Any progress? We were running 3.1.29xxx previously. Please advise. Commenting out the security check in the update_event.php file did not correct the issue. Only seems to happen when manually adding events to a manual recurring event.
|
|
Jonathan Wilson
|
February 13, 2013 at 3:12 pm
Hey Leland,
I just submitted the ticket earlier today. There isn’t an update on it yet. Seth is aware that it definitely is an issue.
|
|
bchilders
|
February 13, 2013 at 3:21 pm
Unfortunately I am not positive on the previous version, but believe we were also running 3.1.29
|
|
Jonathan Wilson
|
February 13, 2013 at 3:28 pm
That’s fine. Thank you for that. I’ll add the info to the ticket.
|
|
Leland Zaremba
|
February 14, 2013 at 7:38 pm
This has been addressed. Thanks Seth.
|
|
Seth Shoultes
|
February 14, 2013 at 8:24 pm
Fixed in version 3.1.30.7
|
|
bchilders
|
February 15, 2013 at 12:35 pm
Updated and everything works great! Thanks for following up and getting the fix in.
|
