|
Lucinda Dalrymple
|
February 1, 2015 at 3:01 am
I have two standard prices:
Camper Registration $720.00
Camper Registration with Aftercare $813.00
I originally entered the Camper Registration as the first standard price. It came up as Name 2, and I added Camper Registration with Aftercare as the second standard price, which came up as Name 5. With that configuration, the main registration page showed Camper Registration with Aftercare as the event price.
So I deleted both prices and put Camper Registration with Aftercare in first, which became Name 2, and Camper Registration in second, which became Name 5. It now displays correctly on the main registration page [EVENT_LIST], but NOW on the second registration page [ESPRESSO_EVENTS], the default price in the dropdown is the Camper Registration with Aftercare price.
How can I get the Camper Registration price (or both prices) to display on the main registration page, as well as having it be the default price in the second registration page?
Note that I also just added a topic regarding the main registration page also not displaying the discounted early bird price, in case that matters.
Registration Page: http://summerfunseattle.org/registration
Password: nufremmus
Recently upgraded EE from 3.1.36.1.P to 3.1.36.6.P
Event Espresso version 3.1.36.6.P
WordPress version WP 4.1
Installed plugins:
Admin Color Schemes by WordPress Core Team version 2.0,
Advanced Code Editor by BaInternet version 2.2.6,
All In One SEO Pack by Michael Torbert version 2.2.5.1,
Anything Popup by Gopi Ramasamy version 5.6,
Conditional Widgets by Jason Lemahieu and Kevin Graeme (Cooperative Extension Technology Services) version 2.0.5,
Contact Form 7 – Dynamic Text Extension by Chris Mavricos, SevenSpark version 1.2,
Contact Form 7 Honeypot by Dao By Design version 1.6.2,
Contact Form DB by Michael Simpson version 2.8.28,
Contact Form 7 by Takayuki Miyoshi version 4.1,
Duplicator by LifeInTheGrid version 0.5.12,
Easy FancyBox by RavanH version 1.5.7,
Easy Privacy Policy by Kevin Sparrow version 1.02,
Event Espresso – Attendee Mover Tool by Event Espresso version 1.1.b,
Event Espresso by Event Espresso version 3.1.36.6.P,
Really Simple CAPTCHA by Takayuki Miyoshi version 1.8.0.1,
Remove Widget Titles by Stephen Cronin version 1.0,
Shockingly Simple Favicon by matias s version 1.8.2,
Spectacu.la Page Widget by James R Whitehead of Spectacu.la version 1.0.7,
Site Plugin for summerfunseattle.org by Sparrow Web Design version 1.0,
TC Comment Out by Tracy Rotton version 1.2,
UpdraftPlus – Backup/Restore by UpdraftPlus.Com, DavidAnderson version 1.9.50,
WP Mail From II by Ben Huson version 1.0.2
Thanks!
|
|
Lorenzo Orlando Caum
|
February 2, 2015 at 8:23 am
Hi Lucinda,
You can change it to show the additional pricing by adjusting some of the templates.
Try this tutorial:
https://gist.github.com/lorenzocaum/59a9037fac1dbf1478e6
—
Lorenzo
|
|
Lucinda Dalrymple
|
February 16, 2015 at 4:30 pm
Thanks for your reply. I guess I’ll need to edit the files.
How will this affect the order of display of the prices on a)the main registration page, and b)the dropdown list of prices on the second registration page?
FYI, The other question I asked regarding the main registration page not displaying the discounted early bird price also requires editing child versions of core files.
This seems a little ridiculous. I think that, instead of us having to edit core files, Event Espresso should handle these things. In this case, I think that EE should either display the first price as the default price on the main registration page, as well as having it be the default price in the second registration page, OR there should be a checkbox where we can select which is the default price. OR it should display all the prices. OR give us an option whether to display only the default price or all of the prices. OR…
See what I mean? Instead of your customers having to edit files, these features should be thought out and coded beforehand to be handled by EE. It seems obvious to me that when there are multiple prices, we should be able to either select the default price and/or specify a sort order (Checkbox? Entry field for sort order? Drag and drop interface?).
I also don’t like to have to edit files and risk either a)having them overwritten when EE is updated or, b)having to edit “child” files and risk losing out on functionality when the parent file gets updated.
|
|
Sidney Harrell
|
February 16, 2015 at 7:18 pm
When you upload the files after editing them, you’ll want to upload them to uploads/espresso/templates, so that they will not be overwritten by an update.
Even having editable templates was pretty state of the art for a WordPress plugin when EE3 was first written. Since then, every aspect of the system has been rewritten, which resulted in EE4. I would invite you to check it out, if only to play around with it for now on a dev site or one of our demo sites, and decide later if you want to convert an existing EE3 site, or build a future site in EE4.
|
|
Lucinda Dalrymple
|
February 16, 2015 at 9:16 pm
I thought EE4 was a different plan than EE3, and we would have to pay for a completely new license. Is it possible to download EE4 and test it on a local install of my client’s site without purchasing a new license? And if I do that, is there anything special that needs to be done to convert the existing EE3 site to EE4?
Thanks.
|
|
Tony
|
February 17, 2015 at 1:00 am
Hi Lucinda,
All EE3 licenses include EE4 as part of the license, the reasons for this is eventually we would like all users to switch to EE4 as it supports their feature requirements.
Your license key still applies to one site, but you are more than welcome to install EE4 on a dev site and see if it suits your needs. Just leave the license key field blank on the dev site.
And if I do that, is there anything special that needs to be done to convert the existing EE3 site to EE4?
That’s a tough question to answer because EE4 integrates more heavily with WordPress than EE3, EE4 uses custom posts types (with custom tables) which allows EE4 events to be used much more like WP Posts, this allows compatibility with more plugins and integration with your theme to display the events.
The downside to this is that there are far too many plugin/theme combinations for us to test all variations and occasionally conflicts happen. Also if the theme is doing something really strange this can also effect EE4 events sometimes.
However please don’t be put off from EE4, most installs work without any conflicts and if there are any they are usually resolved very quickly (or a temp work around used until then) and EE4 has some great features! The above just means it is important to install EE4 on a dev site locally (or on a live dev server) before updating live to check all is well. If the theme is properly coded, and you are not using any (very) strange plugins it is likely you’ll find no issues at all.
When you install EE4 on a site that has previously used EE3 you will be asked if you would like to migrate your data, this will transfer all data from your EE3 install to EE4, simply follow the on screen instructions to do so.
If you do have any problems just let us know and we can investigate.
|
|
Sidney Harrell
|
February 17, 2015 at 3:33 pm
Hi Lucinda. I just got informed that this has been fixed in 3.1.37, which is available from the Pre Release section of your account page. Once you’ve got it installed, go to the template options screen to select all prices or range.
Sorry about that, it must have been one of the last features that was added to the 3.1 branch.
|
|
Lucinda Dalrymple
|
February 19, 2015 at 3:52 pm
Great! Thanks for letting me know. We’re right in the middle of our annual registration period, and I don’t feel comfortable updating EE in the middle of it. I know it would probably be fine, but better to err on the side of caution I think.
though I guess I could backup the site, install it locally. and upgrade there to test it. That shouldn’t take too long. I’ll give that a shot.
Thanks again.
|
|
Dean
|
February 20, 2015 at 4:39 am
We always recommend testing updates (to any plugin/theme) on a development server first just in case, plus backing up before updating the live site.
|
