[Escalated to 2nd Tier] Problem translating Event Calendar
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Elementor users - please update WPML to the latest version to maintain compatibility. More details here - https://wpml.org/changelog/2024/12/wpml-4-6-15-critical-update-for-elementor-sites/
After a lot of back and forth with one of your supporters, I contacted Event Calendar to see if they could find a solution. Since then they released, last week, a maintenance update supposed to fix the bug that was causing WPML/Event Calendar to cause 404s in my French calendar.
The release document is here: hidden link
It didn’t fix the issue. I still get 404s when I try to access my events in French on the live and staging website BUT we installed WPML and Event Calendar on a new and separate WordPress installation and it worked.
I want to give access to the staging website so you can find how to fix the problem. Resetting WPML on the staging site broke ALL the translations (posts, pages, etc.) and redoing all of that is not an option.
This seems like the slugs are not updated properly in the already created events, \
However, creating new event works without any issue.
For debugging purpose, I would require your permission to install duplicator plugin on your stating site, it will enable me to create a copy of your site and test the issue on my local environment with some debugging tools.
If you feel you can help with creating the duplication package , You can use the Duplicator plugin to create a snapshot of the site and share the package link with me http://wordpress.org/plugins/duplicator/, I have enabled private fields for you the share the details.
This seems more like a compatibility issue, I would like to isolate the issue in a fresh installation. I have created a sandbox site for this purpose, Please upload the latest version Event calendar pro plugin to the site
One Click Login:hidden link
Please configure WPML and setup the Events calendar the same way as in your site, make sure to create a dummy event and translate it, The Attempt is to recreate the issue can escalate to our compatibility team.
Please, note we need only the bare minimum setup to reproduce the issue.
Yes it is a compatibility issue but you cannot recreate the issue since it was happening before the latest Event Calendar maintenance update. However the update did not fix the issue on my client's calendar. If you try to recreate it on any other website, it will simply work. So what I want to know is how can we fix it on my client's calendar without having to redo the whole thing.
I did install the Event Calendar, WPML and created an event but like I said it will not replicate what I'm describing/what you can witness on the staging website.
I have checked your live site, everything seems to work fine with the events calendar hidden link. Can you please confirm whether the issue is resolved or could you please share me the URL where the issue can be seen.
The live site currently has a plugin running that is "fixing" some issues. This is a temporary solution we found while waiting for you to give us the permanent solution.
You can see the issue described here: hidden link
On the live site you will notice that if you click to see the next month, the whole French calendar switches to English. So no, it is not resolved.
Thanks for your patience, I have tested this in detail,
Our team found the bug. It is necessary to fix a code snippet in the WPML and also in The Events Calendar plugin. We have sent a correction request to the authors of the plugin.
Your live site works fine since the events slug is not translated however in the staging site the event slug translated to french as eventments which is causing the issue.
To fix the issue with the calendar please enable the Language Ajax cookies in WPML > Languages section clear SG cache, Test the site in a new browser. I hope this helps you better.
I am escalating the issue to the compatibility team.
