Hi and thanks for your question.
Point 1 is actually a bit strange. Which theme and which page builder are you using? And how did you insert the switcher into the project? Via shortcode or as a block?
I’ve added point 2 to the to-do list for the next updates. That’s actually still missing here.
Hi,
we use GeneratePress and Gutenberg, so nothing special.
Same behaviour with shortcode and language switch block.
I duplicated the project and tested with the standard GP Theme and Twentyfive, same problem.
Deactivated all plugins that possibly could interfere, same problem.
I can give you the url and access to the backend of the test environment, only need to know where to send the credentials…
@claudiaiw I’m am 100% sure you mean well but please never ask for or offer credentials on these forums.
https://wordpress.org/support/guidelines/#we-reserve-the-right-to-manage-the-forums-to-the-best-of-our-ability
Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER.
If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty.
Please be aware that repeatedly asking for credentials will result in us escalating this to the plugins team.
It’s never necessary to do that. Here’s why.
There are many ways to get information you need and accessing the user’s site is not one of them. That’s going too far.
*Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
*Ask the user to create and post a link to their phpinfo(); output.
*Ask the user to install the Health Check plugin and get the data that way.
*Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
*Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again.
*Ask the user for the step-by-step on how they can reproduce the problem.
You get the idea.
Volunteer support is not easy. But these forums need to a safe place for all users, experienced or new. Accessing their system that way is a short cut that will get you into real trouble in these forums.
Hello,
thank you for your feedback. I have now been able to reproduce the problem on my end. A solution has already been added to the repository and will be available in the next release of the plugin. This is currently planned for the beginning of next week.
Addition: the active language will also be marked with the next release. This is done using a separate CSS class, but we do not provide any formatting for this atm.
-
This reply was modified 6 months, 1 week ago by
threadi.
The update is now available.
