|
Amy Swift
|
January 29, 2013 at 1:56 pm
We have an event that just went live on the site which has a member and non member pricing ($40 and $15). there is no free option for this event.
Somehow a user registered for the event, it shows a green Vi button indicating they paid but inside it shows payment of $0. and there is no indication of credit card payment or paypal payment. (this is a non-member)
Another user (who is a member) paid regularly and it worked ok.
Here is the event page
Both wordpress and EE are updated to latest version.
Please advise. let em know if you need admin access.
|
|
Josh
|
January 29, 2013 at 3:02 pm
Hi there, There’s a few possibilities here. The price selector has been modified to use a radio button. This isn’t a standard Event Espresso registration page template feature. If JavaScript is disabled on one’s browser, they can bypass that page without selecting a price. The other things to check: 1) Verify that all Event Espresso’s add-ons are current, you can check the version numbers on your account page against the version numbers on your plugin admin page. 2) Verify that if there are any templates in /wp-content/uploads/espresso/templates, that these are not using any of the old pricing functions from prior to version 3.1.28.P. If there is any old pricing function code from prior to 3.1.28.P in that location, Event Espresso will not work as expected.
|
|
Amy Swift
|
January 29, 2013 at 4:11 pm
I have disabled javascript in firefox and was still unable to bypass the price selector.
All addons are up to date.
I have files in the wp-content/uploads/espresso/templates folder but how do I know if there is old pricing code in there?
|
|
Josh
|
January 29, 2013 at 4:20 pm
If the files were copied over from a version of Event Espresso 3.1.28.P, and haven’t been updated since updating to 3.1.29, then there are old pricing functions that need to be updated.
|
|
Amy Swift
|
January 29, 2013 at 4:29 pm
In that case these are the new files.
What else can this be?
|
|
Josh
|
January 29, 2013 at 4:53 pm
The pricing selector has been modified, so it could be that. The stock Event Espresso registration form does not use a radio button.
Other things that should be checked: older gateway code in /wp-content/uploads/espresso/gateways and also the default payment status should be set to incomplete or pending in both Event Espresso>General Settings and within the event itself under event options.
|
|
Amy Swift
|
January 30, 2013 at 1:41 pm
ok uploads/espresso/gateways has no files in it.
as for the radio button, it was the only way make the system recognize a type of membership as you guys don’t offer a way to distinguish and only have member or non member. This was I show options in a radio buttons instead of dropdown and display:none the one that doesn’t match the logged in member’s membership type.
I don’t see how turning the dropdown into radio buttons can cause this problem.
In any case, another visitor registered to another event without paying and showing payment made of $0 but this time from the name and email address I was able to detect that this is automatic spam and not a person actually trying to register and wants to go to the event. they used the email burberry11111111@gmail.com
which as you can see here has been flagged as known spam from china.
This used to happen before i even implemented the radio buttons and before I last updated the plugins and wordpress and so I thought the updates resolved the issue but it looks like this is still happening. It looks like is it somehow only via robots. no one has managed to manually replicate signing up for free from any computer or any browser.
|
|
Josh
|
January 31, 2013 at 9:36 am
If you’re having troubles with spam registrations, we recommend using re-captcha and even better, having the host install the apache mod security module. There’s a post in our blog where you can read about this in more detail:
https://eventespresso.com/2012/08/protecting-your-events-against-spam/
|
|
Amy Swift
|
January 31, 2013 at 12:16 pm
Well the payment gateway itself should prevent spam registrations, at or least should stop them after initial registration and leave it incomplete.
But since one registration was spam but the other one was a registered member, the problem is not spam. it is that somehow under some conditions a full registration gets through without payment.
What next?
|
|
Josh
|
January 31, 2013 at 3:40 pm
It might help to know more about the browser that was used when this happened. One good way to get all the important browser details is have them go to supportdetails.com and send you the report it generates.
|
|
Amy Swift
|
January 31, 2013 at 3:42 pm
excellent service. I’ll check and report back.
|
|
Amy Swift
|
January 31, 2013 at 6:09 pm
Ok so here are the details of the person who got through. They said that when they got to the second page (detail confirmation page) it already showed $0 amount and when they clicked to complete registration it didn’t even go to the payment page and just confirmed it instead.
Details:
Operating System Macintosh Mac OS X 10.7.5 Intel
Screen Resolution 1280 x 800
Web Browser Safari 6.0.2
Browser Size 1116 x 603
IP Address 108.38.96.154
Color Depth 24
Javascript Enabled
Flash Version 11.5.502
Cookies Enabled
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17
|
|
Chris Reynolds
|
February 4, 2013 at 1:22 pm
@amy
I’ve confirmed that in Safari on OSX that you can go through a registration, not check your radio button, and get a free registration. The issue does not exist in Chrome. So it’s a problem with the radio button. We had a similar issue with Multi Event Registration which is why we replaced the radio buttons (when there is only a single option) to a dropdown menu, which you might want to try as well.
link
|
|
Amy Swift
|
February 4, 2013 at 2:55 pm
Hi Chris,
Thanks for identifying where the issue is.
For the particular needs of this site/organization we needed to have tiered membership pricing. meaning different pricing for different types or levels of members. And since this is not an existing option in EE I had to get creative and find some way to do it, otherwise the whole purpose of using this plugin becomes pointless for us.
So the only way I could find to do it is identify the member level, and display to them only they’re membership price, and the only way to do that was to get rid of the dropdown and replace it with a radio.
In most case it forces you to choose a price, and since there is only one displaying, that solved the problem. But now it turns out it doesn’t force the choice in safari.
So my question is, how is the forcing of the choice happening? is that javascript? why does it not work properly in safari? and how can I solve this?
|
|
Amy Swift
|
February 5, 2013 at 11:05 am
Sometimes i’m surprised I come up with solutions before you guys as you know so much more about this code then I do. and a simple solution at that.
I just added checked=”checked” to the radio button input tag. since i show only one price to who ever is on the page, whether they are a non member , level a member or level b member, the choice itself is arbitrary, it was already made for them based on whether they are logged in or not and if so they are logged in as what type of member. I just had to put it in there to pass it to the next reg’ page.
now i preselect the price by making it checked. done.
Thanks for the help. I would have probably taken forever to realize it was safari though.
|
|
Amy Swift
|
February 5, 2013 at 11:09 am
p.s.
that wasn’t meant as a put down. as frustrated as I often am with this plugin, i do appreciate your help
|
|
Chris Reynolds
|
February 5, 2013 at 2:12 pm
No problem. We’re glad you got it to work. As I said, we’ve had similar issues with Event Espresso core and Multi Event Registration, so we’ve had to remove the radio buttons ourselves, but the validation was (I believe) a js issue (not that it matters once you have the radio always selected).
However, what you might even want to do is remove the radio entirely and put a hidden input there instead — since there’s no actual choice happening, but you still need to submit the input.
|
|
Amy Swift
|
February 5, 2013 at 2:14 pm
Thanks! thats a good idea…
|
