Home › Forums › Calendar Products › Events Calendar PRO › Month View Navigation (prev/next) doesn’t stick to language (WPML)
- This topic has 24 replies, 7 voices, and was last updated 8 years, 5 months ago by
Mister.
-
AuthorPosts
-
March 15, 2017 at 7:09 am #1254442
Mister
ParticipantThis issue appears for Events Calendar Plugin Month View (AJAX Navigation) and Events Calendar Pro Month Mini Widget (AJAX Navigation).
Hi,
when having a setup with multiple languages WPML, any of the month previous and next navigation will always go back to the main language (e.g. English) when navigating to another month. To reproduce, please to the following:
- Set up a fresh WP install
- Install Events Calendar, and WPML
- Set up 2 languages in WPML and configure WPML as described in the docs
- Create events in multiple months and translate them as described in the docs
- Switch to language 2 and go to the month view
- Use the month view prev/next navigation and once you clicked, you will see that the month view did switch to language 1 after the AJAX load.
The weird thing is, that the whole page stays in the language 2, but only the month view content is loaded as language 1 (because of the AJAX load).
My assumption is that “wp-content/plugins/the-events-calendar/src/resources/js/tribe-events-ajax-calendar.min.js” has a bug.
How can this be fixed.
Please note that this is an absolute show stopper. I can’t run a productive site with that!
March 16, 2017 at 3:38 am #1254979Andras
KeymasterHello again Mister,
Thanks for reaching out and I’m sorry about this issue.
I tested this on my existing local setup which has WPML and so far I wasn’t able to recreate it.
I will try to do it again following your steps and will get back to you with my findings.
Thanks for your patience!
Cheers,
AndrasMarch 16, 2017 at 5:11 am #1254992Andras
KeymasterHallo nochmal,
So I tested it with a brand new install with the steps outlined above and I could reproduce the issue you outlined. So indeed, we might be facing a bug here. I will open an internal bugticket for this so our developers can take a look at it and develop a fix.
What I can tell you at this point is that the fix will most probably not be done in the next maintenance release as that one is well under way. More likely in the next one.
I am going to set the status of this ticket to “pending fix” and we will update it once the fix is released. If you have any new questions or issues please create a new ticket and reference this one.
Thanks and cheers,
AndrasMarch 16, 2017 at 5:23 am #1254997Mister
ParticipantHi Andras,
Thanks for the update and sorry to jump in again.
I understand that the fix takes time for being deployed, but for me this is a showstopper productive issue. Please provide me a fix here asap (e.g. code snippet), that I can overwrite the plugins core files until the fix is being officially deployed.
March 17, 2017 at 1:44 pm #1256072Andras
KeymasterHi Mister,
Our hands are full at the moment with the upcoming maintenance release, so I cannot guarantee anything, but I’ll see what can be done. I’ll get back to you on that soon.
Cheers,
AndrasMarch 20, 2017 at 2:09 pm #1256875Andras
KeymasterHi Mister,
I checked and while this fix will not make it into the upcoming maintenance release (still in March), it has high priority, so there is a high chance it will be in the one after that, sometime in April. Hang in there, the fix is coming soon.
Thanks for your patience!
Cheers,
AndrasMarch 20, 2017 at 2:15 pm #1256882Mister
ParticipantThis reply is private.
March 21, 2017 at 3:14 pm #1257620Andras
KeymasterThis reply is private.
June 5, 2017 at 1:18 pm #1293345Andras
KeymasterJust putting the reply here as well, maybe then you’ll be able to reply here too.
There is already a developer assigned to do this fix, however no release date has been set yet. I’m sorry that the wait is so long, please hang in there. This is on high priority at the moment and we are working on it.
Thanks for your continued patience!
Cheers,
AndrasJuly 14, 2017 at 9:07 am #1321243Victor
MemberHello Mister!
Just wanted to share with you that a new maintenance release (for the Week of 10th July 2017) is out, including a fix for this issue 🙂
Find out more about this release → https://theeventscalendar.com/maintenance-release-week-10th-july-2017/
Please update the plugins and let us know if the fix works for your site.
Best,
VictorAugust 1, 2017 at 9:33 pm #1329254Janne
ParticipantHi,
This bug still exists, so it would be good to get the fix as soon as possible.
August 2, 2017 at 8:28 am #1329460Mister
ParticipantHi – I also can confirm that this issue is not resolved. The bug still exists.
Please fix.August 7, 2017 at 2:25 pm #1331816Andras
KeymasterHello Janne and Mister,
Thanks for getting back to us on that and I’m sorry to hear you are still experiencing the issue.
We have discovered that this bug (#82286), though very similar to another one (#41908 – Ajax calls reset language in calendar widget), it is slightly different from that. The fix released was specifically addressing bug #41908. That seems to be fixed now.
The fix for bug #82286 is being worked on. At the moment a release date has not been set so I cannot commit to anything just yet.
Thanks for your understanding and your patience!
Andras
September 8, 2017 at 12:47 pm #1346833Sylvia Schütz
ParticipantThis problem is still existing – by the way, since March. Can you please tell us when there will be an update?
September 11, 2017 at 4:52 am #1347444Andras
KeymasterHello Sylvia,
Thanks for your inquiry!
I’m really sorry, until now we didn’t get to fixing this issue. I checked the status of the bugticket and currently is planned to be fixed with the next maintenance release and is waiting for a developer to be assigned to.
If all goes according to plan, then the fix should come in 2-3. However knowing how tricky it is with WPML it might need a bit more time. But I hope it will make it into the next one. It is definitely in focus now and I will also ping it to the team.
Thanks for your patience!
Cheers,
Andras -
AuthorPosts
- The topic ‘Month View Navigation (prev/next) doesn’t stick to language (WPML)’ is closed to new replies.
