|
David
|
August 2, 2016 at 5:43 am
I’m getting an error right now on my site when a guest tries to register for a ticket. They get the error:
An error has occurred:
We’re sorry, but you do not have the required permissions to perform the following action: Create New Registration
If I try to register while logged in, it works. But if I’m logged out (as all guest will be) the error is created.
Any ideas?
Thanks,
David
|
|
Lorenzo Orlando Caum
|
August 2, 2016 at 5:51 am
Hi David,
I was able to verify the issue on a testing site and we are working on a fix which will be available as a one-click update.
Could you deactivate and remove your current version and upload and activate this one?
redacted – Event Espresso support team – LOC // this issue was corrected this morning. Please update to the newest version of Event Espresso 4. You can force a re-check for updates through WP-admin –> Event Espresso –> General Settings and then click on the Save button.
We will update your support post once we have more information.
—
Lorenzo
|
|
David
|
August 2, 2016 at 6:09 am
Ok – thank you.
Fixed for now!
David
|
|
Josh
|
August 2, 2016 at 8:41 am
Hi there,
You can update to the current version of EE4 (4.9.6) and that will fix the error that you were seeing.
|
|
Melissa Jones
|
August 2, 2016 at 9:03 am
So how do you force an update? Getting this error… and the 4.9.6 update is not showing under wordpress updates?
|
|
Melissa Jones
|
August 2, 2016 at 9:16 am
URGENT!!!! Ok… downloaded and uploaded the latest version… and it’s somewhat fixed. I can make it to the register page – but now A BIG ERROR IS DISPLAYED across the top Warning: array_pop() expects parameter 1 to be array, object given in /home/gaaadmin/public_html/wp-content/plugins/event-espresso-core-reg/core/services/commands/CommandBus.php on line 119
|
|
Josh
|
August 2, 2016 at 9:21 am
You’ll need to turn off PHP display_errors or WP_DEBUG or both.
|
|
Melissa Jones
|
August 2, 2016 at 9:35 am
When or where were then turned on? I never did it? Where do I turn them off?
|
|
Tony
|
August 2, 2016 at 10:04 am
EE does not enable any error reporting on your server.
Either WP_DEBUG is enabled within wp-config.php or your server has error reporting enabled so it displays the errors/notices/warnings.
One way to disable the errors is to add:
@ini_set( 'display_errors', 0 ); to your wp-config.php file, I’d recommend adding this directly below the define( 'WP_DEBUG', FALSE ); (or TRUE) code.
Like this – http://take.ms/i4zEt
You don’t really want error reporting enabled on a production server so if your not comfortable with the above you may be better contacting your host and have them prevent the errors from being displayed for you.
|
|
paintingwithrita
|
August 2, 2016 at 3:34 pm
I am now getting that same error since updating to 4.9.6. Hiding the errors seems to me to be sweeping it under the rug. If displaying errors wasn’t enabled, I would not know there was a problem.
Warning: array_pop() expects parameter 1 to be array, object given in /home/paintiy4/public_html/wp-content/plugins/event-espresso-core-reg/core/services/commands/CommandBus.php on line 119
Warning: Invalid argument supplied for foreach() in /home/paintiy4/public_html/wp-content/plugins/event-espresso-core-reg/modules/single_page_checkout/EED_Single_Page_Checkout.module.php on line 873
Warning: array_pop() expects parameter 1 to be array, null given in /home/paintiy4/public_html/wp-content/plugins/event-espresso-core-reg/core/services/commands/CommandBus.php on line 119
|
|
Lorenzo Orlando Caum
|
August 2, 2016 at 4:04 pm
Hello,
That is a PHP warning rather than an error that would block a registration.
The good news is that I’ve just finished up testing on a fix that will resolve that warning and that should be released by tomorrow morning.
—
Lorenzo
|
|
Erick
|
August 2, 2016 at 5:22 pm
Why does my post keep disappearing? I am having the same error as OP even though I have updated to 4.9.6
|
|
Erick
|
August 2, 2016 at 5:45 pm
Now it is changed to a different message: “We’re sorry, but your ticket selections could not be processed due to a server timing error. Please hit the back button on your browser and try again.”
|
|
Josh
|
August 2, 2016 at 8:26 pm
Hi Erick,
Can you try disabling the bot trap option in Event Espresso > Registration form > Settings?
As an aside, maybe you can try posting your comments in one thread instead of many?
|
|
Erick
|
August 2, 2016 at 8:59 pm
Josh, I was split to another thread and wasn’t notified. Thought my posts were deleted.
|
|
Tony
|
August 3, 2016 at 5:57 am
@paintingwithrita
Hiding the errors seems to me to be sweeping it under the rug. If displaying errors wasn’t enabled, I would not know there was a problem.
Just to clarify, we are not trying to sweep the notices/warnings under the rug and will be pushing a fix for this shortly.
However generally its good practice not to display errors on your production server, log them so they can be fixed by all means, but don’t display them to your users. This is especially true for warnings/notices as they generally don’t have any effect on the code and just advise that something isn’t quite right but will still work.
For example if you update your PHP version on the server, code that was once perfectly valid may now start throwing notices. You don’t want them displayed to your end users although you’ll still want them fixing before they become a problem in the next version of PHP so you log the errors and check the log file from time to time to see if any errors are being thrown and from where.
To take it one step further you could have a development copy of the site on a subdomain, for example dev.example.com, this would be the same site set not to index on search engines and not visible to the public. You then enable full error reporting on that site and leave the production site to display none.
|
