Whenever a page is translated inside any RESOURCE (not any page, in any resource) using in built Google Translate, the site refreshes with the translated contents too. Translating again results the same issue.
Attempted page example (in reviews): https://nulledvault.com/downloads/exploitfixer-anti-crash-dupe-plugin.11955/
Steps to reproduce:
1. Right click on the resource page
2. Click on "Translate to <language>"
3. See the page go back in its original state because of a site refresh.
This is not on the client side as you need to go in any resource to reproduce this, not some random page.
Now for the suggestion, there are some users that don't speak English as their main language, thus having them to use google translate to translate their origin language to English. But this takes effort and for some 1 line review, people may not want to use google translate.
To contrast this, you can add a "Auto Translate" feature where users are able to translate the content if the content is written in a different language.
Or you can automatically translate all messages before they are sent for visibility.
Attempted page example (in reviews): https://nulledvault.com/downloads/exploitfixer-anti-crash-dupe-plugin.11955/
Steps to reproduce:
1. Right click on the resource page
2. Click on "Translate to <language>"
3. See the page go back in its original state because of a site refresh.
This is not on the client side as you need to go in any resource to reproduce this, not some random page.
Now for the suggestion, there are some users that don't speak English as their main language, thus having them to use google translate to translate their origin language to English. But this takes effort and for some 1 line review, people may not want to use google translate.
To contrast this, you can add a "Auto Translate" feature where users are able to translate the content if the content is written in a different language.
Or you can automatically translate all messages before they are sent for visibility.