Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hello there,
Thanks for your contact!
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi there,
Thank you for providing the credentials.
We have migrated the website into a copy version hosted in our servers, in order to make tests without compromising the live production, but so far we weren't able to reproduce the issue there.
Then, we tried to enable WPML back in the original website, and as far as we can see, everything looks good now. Could you please review it and let us know if it is fine, indeed?
Yes, it looks great. But only if you are logged in.
Every page on the site (if not logged in) looks like the one attached to this message. (Only footer and header show)
Please, if you test this on the live site, ensure it also works when not logged in. Otherwise (as I have done now), deactivate the plugin.
We have applied the proposed solution in our copy version, and it seems to work. I was going to test it in your website, but the login for the cpanel is not valid anymore.
Therefore, may I kindly ask you to give it a try in the live website? Just make sure to have a complete backup before doing so.
Hi, I Changed the code. It seems to work 🙂
In what version of the code will this be "standard"?
(Now we have 4.6.6, and I think I saw an upcoming update, and I guess it is not in that version!?)
Languages: English (English )Portuguese (Brazil) (Português )
Timezone: America/Sao_Paulo (GMT-03:00)
Hi there,
Glad that it is fine now.
The linked solution is a temporary workaround. This should be fixed in a future version of WooCommerce Multilingual. As far as I can see, on the board it's planned to be released with WooCommerce Multilingual 5.5.0.
We can not guarantee that it will be included in this version, but I will let you know once the version is available.
You can also see the state of the erratum. If something changes, it will be updated too.