|
Becky Melton
|
January 15, 2015 at 1:21 pm
We really, really need to apply 2 prices to our event registrations (member and non-member prices). If we make 2 types of tickets, we will be unable to enforce the attendee number limit. Is there no way to create promo codes in EE4?
|
|
Josh
|
January 15, 2015 at 3:17 pm
Hi Becky,
Have you tried setting a limit for the event’s datetime? This way, you’ll be able to enforce an attendee number limit and make two types of tickets.
Promotional codes for Event Espresso 4 is under active development and will be released for early beta testing when it’s ready for testing.
|
|
Becky Melton
|
January 16, 2015 at 6:52 am
Hi Josh. Thanks for your reply.
Yes, I see limiting the event’s timeline would work if the event occurred on one date. However, the events I am setting up have 10 sessions. (summer camp with 10 one week sessions) If each date has 2 types of tickets, how could we enforce the attendee limit for each session?
The only way I see is (1) offer a discount or (2) create separate events, which would be cumbersome for the registrants signing up for multiple weeks.
Any suggestions?
|
|
Becky Melton
|
January 16, 2015 at 7:22 am
Hi Josh – I think I figured it out by reading this article. https://eventespresso.com/wiki/datetime-ticket-names-consolidate-event-pages/
Thanks for your help!
|
|
Becky Melton
|
January 16, 2015 at 9:21 am
I couldn’t do it this way, because an alert advised me there were more variables than allowed by the server. (10 event dates, and twenty ticket types.) Is there a fix for this?
|
|
Tony
|
January 16, 2015 at 9:39 am
Hi Becky,
Can you go to Event Espresso -> Help & Support -> Support (tab)
Within that screen you will see PHP version, can you post up your current version number please.
|
|
Becky Melton
|
January 16, 2015 at 9:42 am
PHP Version: 5.4.34
|
|
Becky Melton
|
January 16, 2015 at 10:02 am
This is the error:
The number of inputs on this page has been exceeded. You cannot add anymore items (i.e. tickets, datetimes, custom fields) on this page because of your servers PHP “max_input_vars” setting.
|
|
Tony
|
January 16, 2015 at 10:29 am
This is a setting within PHP 5.3.9+ which will need to be changed in order for you to add more tickets.
There are multiple ways to increase max_input_vars, for example adding:
php_value max_input_vars 3000
to your .htaccess file within the root directory of WordPress should increase this value.
However if you are unsure of how to do this, I would recommend issuing a support ticket with your host asking them to increase your max_input_value to 3000 (it will currently be 1000 so 3000 shouldn’t allow you to create 3 times the amount of tickets)
|
|
Becky Melton
|
January 16, 2015 at 11:01 am
Thanks for this tip. – I added php_value max_input_vars 3000 to the .htaccess file, but it deactivated your plugin and seemed to blow the PHP version back to 5.2. I undid my changes and opened a ticket with the host.
I’ll send update …
|
|
Tony
|
January 16, 2015 at 11:19 am
Some hosts do not allow you to change those values within .htaccess so it needs to be done (usually) through a custom php.ini
The best way is to issue a ticket with your host (as you have done) as they will know their servers best.
Please do let us know how this goes.
|
|
Becky Melton
|
January 18, 2015 at 8:03 am
I have changed the max_input_vars to 3000 in our php.ini file. I have added a few more tickets, but continue to get the error alerts about exceeded input vars. Also, the free ticket is being automatically added each time I save changes. (strangely, the free ticket does not appear on the front end.)
Can you help me understand what to do?
|
|
Lorenzo Orlando Caum
|
January 18, 2015 at 5:39 pm
Hi Becky,
Has your host updated your site from PHP 5.2 to a current release of PHP?
—
Lorenzo
|
|
Becky Melton
|
January 18, 2015 at 5:47 pm
The host (BlueHost) advised me to select PHP 5.4 (Single php.ini) in the control panel and change the max_input_value to 3000 in the php.ini file in the root directory. I have made the change and can now add the additional tickets. However, I continue to get the inputs exceeded warnings each time I edit the event.
|
|
Tony
|
January 19, 2015 at 4:12 am
Which version of Event Espresso 4 are you using? (You’ll find this in the Plugins menus or at the bottom of the Dashboard)
If you go to Event Espresso -> Maintenance -> System Information.
Then search for max_input_vars on that page, check that value is 3000 and not 1000 (It likely is as your tickets would not save if not but good to double check)
Go to Event Espresso -> General Settings. Make no changes and just save.
(This forces EE to re-evaluate your settings)
EE checks your max_input_vars values and saves it, then compares input_vars on the fly and throws a notice if you reach the saved value. Saving the config should force this to re-evaluate and save the new value.
|
|
Becky Melton
|
January 19, 2015 at 6:10 am
Using version EE4 Version 4.4.8.p
The System Information page shows:
environment php max_input_vars 1000 version 5.4.34
I saved the General Settings page, but the value did not change on System Information page. I also tried de-ativatiing a re-activating the plugin without success.
Checked the php.ini file in root directory, and it says max_input_vars 3000
It seems the plugin is not seeing the new value.
Suggestions?
|
|
Tony
|
January 19, 2015 at 8:55 am
It sounds like your php.ini file is not recursive, meaning that the settings are applied in the directory that file resides within and not sub-directories.
So now the server has the higher value for max_input_vars (which is why they save), but the settings within /your root directory/wp-content/plugins/* are still 1000, as this is where EE runs from it also shows as 1000.
As modifying .htaccess did not work last time, I would once again contact bluehost and ask them to check if those settings are set to be recursive and if not advise the best way to set it so that it is, Apache may also need to be restarted for the settings to update.
I can provide code for you to try again within that directory if you prefer? Although it would be much better to do the above in my opinion.
|
|
Garth
|
May 5, 2015 at 10:15 am
Starting today, current support license holders can opt in to the pre-release channel and download the Event Espresso 4.7 and Promotion add-on pre-releases.
We’d love to get your feedback on some of the new promotion features and changes that we’ve been working on. These include:
- New interface for managing promocodes
- Promo code discounts now apply to entire order instead of per ticket
- Promo code generator
- Automatic (non-promo-code) discounts
- Discounts limited by quantity
- Discounts limited by start date and end date
- A widget for displaying non-promo-code discounts
- A shortcode for displaying non-promo-code discounts
Important: The Event Espresso 4 promotions add-on will activate only if Event Espresso 4.7 is active. This means you’ll need to install the Event Espresso 4.7 pre-release before installing the promotions add-on.
If you haven’t already opted into Event Espresso’s pre-release channel, you can go to your account page and check the box to opt in to the pre-release channel. Once you opt in, the download files will be available under the EE4 tab under the Pre Release Downloads heading.
You can find out more information about in the pre-release channel guide.
If you have feedback about Promotions or the 4.7 release, please reply to that Promotions announcement or start another new topic.
|
|
Josh
|
August 18, 2015 at 10:54 am
Update: The Promotions add-on for Event Espresso 4 is now available.
|
