Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Shopp | Event Espresso - Staging Server
I’m looking for an estimate on development.
1) I’m currently using Shopp for events and moving to Event Espresso. How much development cost to merge the EE and shop at payment step? We are are considering Stripe, as they are used by both pluins but not locked into that choice.
2) Add coupon codes that reduce the cost of an event by type, not lowering cost of all events.
3) Set the number of participants by ticket type. For example setting 50 VIP and 500 general tickets. I know I can make duplicate events, but that looks broken to the end user.
4) For events with multiple times how do you limit the capacity by time.
That look a bit like a scam. Buy services tokens and they keep the money even if they say no… If they cannot give a quote I assume they are not interested.
It works a little differently than this. We only charge for the Customization Review if we actually do the review. We’ve spent a lot of time doing reviews in the past without getting the actual work, so we’ve started charging for the reviews.
Right now our availability is extremely limited to take on customization projects so I can advise contacting one of our pros for requesting customization proposals:
The support post ‘Shopp’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.