Hello there,
Thank you so much for reaching out and for bringing continued attention to this matter.
We sincerely acknowledge the issue you’ve referenced regarding the compatibility between Ally and the WPML language switcher, where switching languages disrupts the connection due to domain changes—ultimately preventing the feature from displaying correctly in the live view.
Please rest assured that our team is fully aware of this and is actively working to find a solution. While we don’t yet have a confirmed ETA, resolving this is a top priority for us, especially considering the impact it has on multilingual websites like yours. We deeply appreciate your patience and understanding as we work toward a reliable fix.
Should you have any additional details, feedback, or specific use cases you’d like to share, we’d be grateful to hear them—they truly help us improve.
Thank You!
Hi, I have several sites that use WPML, I also tried to install Ally, but it only appears on the home page of the main language.
It’s very unfortunate because I find the plugin very well done!
Will you be able to fix the problem before the end of June, when the new regulation will come into force?
thanks
-
This reply was modified 1 year ago by
durf62. Reason: clarification
Hello there,
we are currently holders of MAX licences with over 25 webs deployed with this plugin, we have 75+ more webs that we would use your licences on but since WPML is hold back atm we might even need to move to other accessibility solution. More than 50% of our webs use WPML, there is absolute need for fix regarding this matter since clients won’t accept having accessibility on only just one language.
Hope you can come with resolution soon.
Hello @branislavmeandzija,
Thanks so much for being our valuable user—we truly appreciate your trust in our plugin.
We completely understand how important WPML compatibility is for your workflow, especially with so many multilingual sites. Please rest assured that the team is aware of this and actively working toward a solution.
We’ll keep you updated and truly hope to have this resolved for you soon.
Thank You!
Solution for Ally/Elementor + WPML using subdomain per language
Hey folks! I went through this exact problem: the Ally accessibility widget (Elementor) worked fine on my main site in Portuguese, but didn’t show up on the English version under /en/ using WPML.
After a lot of trial and error, here’s how I fixed it:
- Set WPML to use “different domain per language”
In WPML, under Languages, I switched to using a different domain for each language:
- Portuguese:
in9ti.com
- English:
en.in9ti.com
- Created the subdomain in my DNS and pointed it to the same server
I created en.in9ti.com in my DNS and pointed it to the same IP as the main site.
- Updated my hosting panel (I use CloudPanel, but this works elsewhere too)
I edited the Nginx Vhost config to add the subdomain as a server_name alongside the main domain: nginxCopiarEditar
server_name in9ti.com www.in9ti.com en.in9ti.com;
Now, both the main and the subdomain open the same WordPress install.
- Added both domains in the Ally/Elementor dashboard
On the Ally dashboard, I registered both domains so the widget is active on both.
- That’s it!
Now the accessibility widget shows up and works great on both the Portuguese and English sites!
Hope this helps someone else stuck with this issue.
Is there any idea when is going to be fixed? WPML is used in many websites around the world so is a huge issue, us one of the most common plugins. Also using subdomains is not a fix for live websites and it affects SEO negatively.
This should be a priority.
Hi.
Same question as Novvaweb: When will this bug be fixed? We can’t simply switch the sites to subdomains.
We have a MAX subscription… which makes it all even more painful.
Thanks
WJ
-
This reply was modified 10 months, 2 weeks ago by
eWebjojo.
Hello there,
With the latest version of Ally – 3.6.0, we’re happy to share that WPML support is now available. You can update to the latest version to start using it right away.
Thank You!
