|
MINTvision
|
May 14, 2018 at 8:31 am
We sell different tickets to our events (for adults, children etc.). If I now select more than one ticket, the tickets do not get mentioned on the checkout page – neither does the price change. The description only shows the first ticket and nothing else. Please take a look at the following screen shot: http://clients.mintvision.de/?t=18d753f5fc73a9335905059e33d6ccfd
The price does indeed change when I select two sets of the same ticket – however this does not work for different tickets.
Could you please take a look at what is going wrong here…I did send you all login details to the site in relation to this earlier thread: https://eventespresso.com/topic/error-81002-during-checkout-paypalexpress/
|
|
Josh
|
May 14, 2018 at 8:51 am
Hi there,
The issue you reported here is fixed in the release candidate for Event Espresso 4.9.62.p.
Please note we do not keep the log in details after we’re finished using them.
|
|
MINTvision
|
May 14, 2018 at 9:00 am
Hi Josh –
Please don’t tell me that this means we have to wait for an upcoming update for this issue to be fixed? The events offer different ticket types and this is a very basic reason why we chose this plugin – we are in the end phase of going online. Is there an update out there already, which I am missing?
We were able to work around the plugin’s limitations earlier by changing our whole setup, but this is a basic thing we understood to be covered by the plugin. Why else would you offer different tickets within each event? Please tell me I misunderstood your response. What do you mean with a “release candidate”. We need to fix this ASAP…if this does not work we got a real problem with the client.
Best regards
Gaby
|
|
Josh
|
May 14, 2018 at 9:13 am
Hi Gaby,
You can download the release candidate here:
https://github.com/eventespresso/event-espresso-core/archive/master.zip
Then, after 4.9.62.p is released you can switch back to the official release to continue to get 1-click updates when new versions become available.
|
|
MINTvision
|
May 15, 2018 at 4:28 am
Hi Josh,
Thanks, but we do not want to use a trial version of a plugin that is mentioned as unstable.
Also, I am now finding that the translation of the red registration button (Weiter zur Registrierung) on the checkout page is not working out for us, as it should be called “booking = Buchung” in German rather than “registration”: https://www.dropbox.com/s/7z61v3ymx8l94l1/Screen%20Shot%202018-05-15%20at%2012.01.12.png?dl=0
The german translation for this button cannot be found via the po file. I was able to change other text areas, but not this one. I found several older posts about how to change the register button via a custom function plugin – I tried to catch both English and German words via the custom plugin in various variations, but it does not seem to catch anything: https://www.dropbox.com/s/n4qy9kibap42yc6/Screen%20Shot%202018-05-15%20at%2012.24.50.png?dl=0
Is this approach still working for EE4?
https://gist.github.com/joshfeck/4962940
It seems really complicated having to translate buttons like this…
|
|
Tony
|
May 15, 2018 at 5:22 am
Hi there,
Thanks, but we do not want to use a trial version of a plugin that is mentioned as unstable.
May I ask where it states that master (which is the branch you would be downloading) is unstable? With our development workflow, we try keep master release ready, so all testing is done against master branch.
The german translation for this button cannot be found via the po file.
Sure it is, the button is broken out to cover various different combinations with how users setup EE, with the flexibility, comes more complications in how we can translate those buttons.
So as mentioned we break down the strings to allow for flexibility and that particular button is using 2 strings right now.
The first part is Proceed to %s see HERE
The %s is a place holder that is replaced depending on the context of the button, for your specific context it’s using Finalize Registration, see HERE
So to change Registrierung abschließen you can change the translation for Finalize Registration in your PO file.
I was able to change other text areas, but not this one. I found several older posts about how to change the register button via a custom function plugin – I tried to catch both English and German words via the custom plugin in various variations, but it does not seem to catch anything:
‘Fuzzy’ translations like that will not work with WordPress (and therefor EE).
The function you have now translated the string ‘Register’ to ‘Weiter zur Buchung’, but that will not change the string ‘Register Now!’ to ‘Weiter zur Buchung Now!’ as the original string must match exactly.
It seems really complicated having to translate buttons like this…
If you have any feedback on how you would like to translate the strings differently and still allow for the flexibility needed on those buttons I’ll happily pass that along to the developers.
|
|
MINTvision
|
May 15, 2018 at 7:55 am
Hi Tony,
May I ask where it states that master (which is the branch you would be downloading) is unstable? With our development workflow, we try keep master release ready, so all testing is done against master branch.
I was referring to the explanation of what the prerelease channel is not: https://eventespresso.com/wiki/pre-release-channel-guide/
We cannot risk a further delay with additional problems, so I am just hoping we can terminate this project now somehow within the given limitations.
The translation of the button worked…thank you!
|
|
Josh
|
May 15, 2018 at 8:35 am
The release candidate isn’t actually from the pre-release channel. Those are two different things and the explanation from the pre release channel does not apply to the master branch of Event Espresso 4 core available from Github.
|
|
Josh
|
May 17, 2018 at 1:06 pm
Update: 4.9.62.p is released. To get back onto the official release you can follow these steps:
1) Download the plugin from your account page
2) Deactivate and delete the release candidate version of Event Espresso from your WordPress -> Plugins page
3) Upload the new plugin to your site via Dashboard -> Plugins -> Add New
4) Activate the plugin
|
