So, I installed the Wishlist addon on a site with 2 languages. When I add an event to my wishlist from the English version, it is added to the wishlist. But only the English Wishlist. If I then change the language to Danish the corresponding events are NOT on the wishlist. (we have English and Danish versions for all of our events) .
So that's really poor usability and very confusing. Say that a user adds events to his wishlish while being on the English version of the site, and later changes to the Danish version, he will not be able to see the events he put on his wishlist / he will have to re/add them for every single language. That doesn't work..
Also, another issue is, that the events displayed using the wishlist manager shortcode don't get the correct colors. They should get the corresponding colors. (all events have a color decided by their category)
Here's a video where everything is explained / https://www.dropbox.com/s/atvt8ca331nype7/wishlist-language-issues.mp4?dl=0
Please let me know how this can be fixed.
Thank you
- May 30,2022 AT 8:45PM - 2 years agoHello,
1. Everything seems to be working correctly:
https://www.animationsfestival.dk/2953-2/ (two calendars L1 and L2, wishlist L1)
https://www.animationsfestival.dk/2958-2/ (wishlist L2)
As you can see one shows events only for L1 and the other is for L2 languages.
2. Please add etc_override=”yes” to the shortcode:
Yes, that is exactly the problem. They should of course show the same events for both languages. There should not be two lists with different events. If I am on the English version of the website, and I add an event to the wishlist, that event should be added to the English version as well as the Danish version. The only difference, that the English version of the event should go on the English version, and the the corresponding event in Danish, should goon the Danish version.
It doesn’t make sense if the same user has two different versions of the wishlist – one for L1 and one for L2.
In general multilingual site separates each language into it’s own subdomain (/en, /de, /es,…). Users go to the only one they can understand, so there is no point of having multiple languages of the same event in one calendar (or list).
Of course there is a point. If you can understand more than one language you might use the site in language A today and language B tomorrow. I understand a few different languages, so i cannot just simply “go to the only one they can understand”. I think you understand more than one language too Artem ๐
Think about this : I go to the website today and it’s automatically set to language A. I log in and I save some events to my favourite list. Then two days later I visit the site again, but this time I find out “Hey, I can see it in language B too”, so I switch my language to B and go to the wishlist, which is totally empty.
OR another scenario would be that I add events to Wishlist in language A, and then I would like to show my wife what I added to the wishlist, but she doesn’t understand language A, so we must switch to language B – and there is nothing to show.
This behaviour is normal in multi-language websites. You don’t have favourites per language. Something like this is always per user – not per language. And when a plugin supports multi language this should be the behaviour. It’s the same if I go to an event while in language A, and I click on the language switcher, I will get the same corresponding event in language B – not a blank page, but the same data, just in a different language. That is pretty common.
I would say it’s a big flaw in this addon, and I would appreciate if you could fix it. It’s more of a bug than a feature request. (basically it’s useless on multi language sites).
Please take this up with Ashan. I’m sure he will see the flaw and that he can add support for it ๐
I have assigned this ticket to Ashan
Thank you my friend for taking the time to tell us more about this issue you have identified.
You are using each event as its own language. Event A might have same information in language 1 and 2 but the way you are using, it is 2 separate events. So adding Event 1 in language 1 is not same as adding event 1 in language 2. Does it make sense? They are 2 separate posts with separate post IDs. Wish list is functioned using this premise of unique event IDs.
I mean I get what you are saying and the scenarios you present. You are the first person to bring this to us, so thank you for opening our eyes to this mismatch situation.
If you add event 1 in lang 1 event post id 11 to wish list… and then to be able to see event 1 in lang 2 with event id 12, it would need to run additional database queries referencing back and forth which could slow down loading time.
Are you using language corresponding events?
I will get the event type override not working for wish list manager issue resolved in the next update. which I am working on now.
As for colors of evet type please use shortcode etc_override=’yes’ in the shortcode ๐
Hi Ashan, thank you for getting back to us. I am glad you see the issue. I guess not many people have used the wishlist plugin on multi language sites.
And yes, I do understand that it is based on unique post ID’s. I do think however that it should be possible to have a database where you can look up the corresponding events – as pairs. I think that is what the translation plugins like Polylang and WPML do. You have a “base” language, and then you have other language versions connected to that event / post / page. So if I create an event in English first, then create the same event in Danish, i can connect them using the language plugin.
You ask: Are you using language corresponding events? Yes – I am using that. An event is basically just a custom post type and Polylang (which we are using) just adds this functionality to all post types, pages, taxonomy etc. You have a base language and then you add another language to that. So I guess whenever you are on a post / page in language A and you switch to language B, there is a lookup in the database asking “Hey, does this post have a corresponding version in language B? Yes – it does, and here is the corresponding post ID”, and it is then served to you
I get that it’s not easy to implement – and that it the queries will slow down loading times a little bit, but I think it’s worth the trade off so EventON can fully support multi languages. The user experience is much better this way I think.
Thank you very much for your kind reply! You are correct it would make the wishlist a much smoother experience! It does require a lot of work and we are in the middle of big EventON 4.1 update so will have to put this in the back burner, unfortunately.
Will keep you posted when we move in to this.
Thank you.. I understand.. It makes me happy however that you take it seriously and you are going to add it in the future.
I have been using EventON for about 3 years now. I think I have used it on 7-8 of my clients sites. I have talked to you before, both here and from other clients accounts.. And whenever you step in Ashan (and Dave for that matter), there is always a positive vibe ๐
Thanks you for that. And continue doing great work!
/Morten
Thank you very much Morten for your kind words!! brighten up my day!!!
So just fyi the next update to wishlist will not have this it is going to be eventON 4.1 compatibility. But will get this implemented ๐
Hi Ashan,
It’s been about 7 months now. Have you implemented this yet?
/Morten
long explanation shortened- No we have not sorted that out as yet.
theres a few issues with the current eventon that are being worked on at this time I am sorry. plus theres a huge RSVP , tickets and action user update coming out once we sort out the current issues.
it is on the todo list, but its not the next thing on the todo list (I’m being honest ) I know its not what you wish to hear. you are the only one to request it so theres alot of updates for action user, rsvp and tickets that effect alot more people. while theres a few staff here- only 1 person is doing the updates- thats Ashan.
So I guess this has still not been addressed. What a shame.
It really worries me to hear that the only developer on the team is Ashan. What happens to the thousands of sites running EventON if Ashan gets sick or something else happens? What about the people whose livelihood depends on selling tickets using this plugin? Their businesses will be destroyed if you don’t have a plan B.
Sorry, but I cannot recommend anyone to use EventON anymore. It’s simply too risky. I will not recommend it to my clients in the future. And I recommend all ofย them (around 8 clients)ย to stop using EventON and start using something like Modern Events Calendar instead.
It’s a shame.. It really is.. I liked it a lot. But well.. Nothing lasts forever.
Hello Morten, Thank you for the message and I completely understand your worry and need for safety net and your concern for worries in the future. We are mortal beings, we are not here to live forever isn’t it so? everything is impermanent ๐ Yes someday EventON will cease to exist, just as once a great Roman empire has vanished ๐
We had several big updates we were working on over the past year, gigantic updates to the entire ticket system which is used by a huge array of users. Anyways we were quite caught up with that. As dave mentioned we are a small team, and we have to be careful on where we invest our time. The feature you request make sense, but would it be used vastly by others to prove worth of our time invested in developing that is the biggest question, specially when we work on gigantic ticket updates and main eventON updates.
Have you raise a feature request for this feature you are asking for wishlist, where others can vote for them and we can get the high voted items developed, where we know there is a demand for.
Anyways, if you are looking for a more safer calendar solutions, I am certain there are many out there.