You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a few pages in two languages. We have discovered that with the newest version of used plugins, after the edition of data for one of the languages and publishing the changes, the version of the page in the other language is destroyed. More specifically, if you edited in English and saved the changes, the English version replaces the data of the versions in other languages.
To Reproduce
Steps to reproduce the behavior:
Edit page in WPBakery
Change something
Click Save
Change language
Expected behavior
The changes for one language do not impact the version in other languages
* qTranslate-XT version 3.15.2
* WPBakery Page Builder version 7.3
* WordPress version 6.4.2
* PHP version 8.1
Tested in the newest Firefox on Linux and Windows
Everything worked fine until some of the recent updates. The web page was not updated for a few weeks, but in the meantime, the software was regularly updated, so we have not noticed the issue until now.
The text was updated successfully, but these errors were encountered:
copyme
changed the title
Edition of pages created with WPBakery destroyers the data
Edition of pages created with WPBakery destroys the data
Jan 10, 2024
We have a few pages in two languages. We have discovered that with the newest version of used plugins, after the edition of data for one of the languages and publishing the changes, the version of the page in the other language is destroyed. More specifically, if you edited in English and saved the changes, the English version replaces the data of the versions in other languages.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The changes for one language do not impact the version in other languages
Everything worked fine until some of the recent updates. The web page was not updated for a few weeks, but in the meantime, the software was regularly updated, so we have not noticed the issue until now.
The text was updated successfully, but these errors were encountered: