|
Andrew
|
March 6, 2014 at 7:11 pm
Hi All,
We recently upgraded from EE3 to EE4. For the most part, it seems to be working brilliantly, except for one critical issue… the “Register Now” button only works when there is a user logged in to the back end. It works perfectly for myself and the other users while we are logged in, but if we log out and try the same registration, it fails. The registration button sends us back the same single event page with the additional text “…/?ee=process_ticket_selections” on the end of the URL.
We are running a single event and you can see it happen at: http://gracebiblechurch.org.au/events/voddie-baucham/
Version details are below.
Thanks,
Andrew
—————————————————–
WordPress Version: 3.8.1
PHP Version: 5.4.23
MySQL Version: 5.5.36
Event Espresso Version: 4.1.8.reg
WordPress Address (URL): http://gracebiblechurch.org.au
|
|
Tony
|
March 7, 2014 at 2:00 am
Hi Andrew,
I’ve just ran a couple of test registrations (one Paid in which I stopped once directed to Paypal, the other using the free tickets you have available) I’m not seeing any issues with the registration.
Can I ask what OS & browser are you using?
|
|
Jason
|
March 7, 2014 at 1:11 pm
Looks like I have the same issue here.
Test event at http://www.theminimakers.com/events/
I will close my other post as its related to this issue. All of my plugins and WP install are updated. Happens regardless of browser used.
|
|
Josh
|
March 7, 2014 at 2:42 pm
Hi Jason,
Please follow up with Lorenzo in the thread that you stared. This may be a different issue.
|
|
Andrew
|
March 7, 2014 at 4:49 pm
Hi Guys,
We tracked down the issue (which is why Tony managed to get through).
We are running a security suite called “Better WP Security” and there was a setting “Filter Suspicious Query Strings” that prevented the registrations from going through (registration worked once we disabled this).
Serge (my developer) may post on here as me if he needs to follow this up. He has far more of the tech understanding… I usually just write content!
Andrew
|
|
Lorenzo Orlando Caum
|
March 9, 2014 at 8:36 pm
Hi Andrew, thanks for sharing this solution. Your post helped another member who had a similar issue.
—
Lorenzo
|
|
Andrew
|
March 9, 2014 at 9:56 pm
Good to know.
The tech question (and well over my head) will be whether the security suite was blocking something that was a legitimate security issue (i.e. the EE code does something in a less than ideal manner) or whether it was just being overzealous…
Might be worth figuring that one out.
Andrew
|
|
Dean
|
March 10, 2014 at 4:21 am
Hi Andrew,
Thanks for the feedback. I think that the security plugin may have just been a little over zealous here, the query string is certainly not a security risk.
|
