|
Bo Attwood
|
March 18, 2013 at 1:01 pm
My multi-event registration is working great for events that are set to <100 attendees, but as soon as I have one set to unlimited, or even as high as 4999, the shopping cart shows the event as present, but the registration page kicks those high-limit attendees out of the cart, and the customer is not billed for them. Is there some attendee max that is set in the code somewhere that I can unset? Any help would be greatly appreciated.
|
|
Josh
|
March 18, 2013 at 1:50 pm
Hi Bo,
That’s very interesting. I’m not aware of a limit in the code that would make this happen. I haven’t seen this happen elsewhere either. To be sure, I set up a few test events with no attendee limits on a sandbox site and tried to reproduce this issue. It turned out that the events with unlimited available spaces stayed in the cart when I did a few test registrations.
Have any of the cart functions or templates been customized or modified on this installation?
|
|
Bo Attwood
|
March 18, 2013 at 2:09 pm
The only cart functions that have been modified are the Authorize.net payment gateway functions and the Event Espresso include file main.php. The main.php has only been altered to affect the display text. No modification to the function of the php has been made. The remainder of the modifications made to the site have been aesthetic, using css with custom ids and classes to customize the look and feel of the site.
To clarify this issue, the items stay in the cart on my site as well, but once you reach the registration page, only the events which have a set number of attendees show up, and upon checkout, it is only these set-figure events that are ultimately charged for.
|
|
Josh
|
March 19, 2013 at 7:30 am
Hi Bo,
You could try turning on the WordPress debug feature (by editing wp-config.php) and go through a registration for one of these unlimited events. There may be an error message that displays when you get to the registration form screen where a form should appear for the missing event. This may help narrow down the issue.
|
