• Resolved platschi

    (@platschi)


    I am having a long list of strings to translate (some 700+ items). On each page under “String translations” (total 38 “pages”), I need to hit the “Save changes” button to save translations. As soon as I edit a string on the last page (page 38 of 38) and hit “Save changes”, polylang loses all translations and sets all (!) strings back to parent language (English in this case).

    Like, I lost hours of translations by translating a string on the last page! This seems to be some strange bug connected with the last page of strings.

    Using Polylang 2.0.5 on latest WordPress.

    • This topic was modified 8 years ago by platschi.
Viewing 4 replies - 1 through 4 (of 4 total)
  • @platschi – Did you find a solution for that problem? Fighting with the same.

    Thread Starter platschi

    (@platschi)

    @caramaple Yes. Under Settings -> Writing, WordPress should correct invalidly nested XHTML automatically was turned on. After I switched it off, it worked.

    Plugin Author Chouby

    (@chouby)

    Hi!

    This issue is fixed in the beta version of Polylang 2.1.
    https://github.com/polylang/polylang/archive/2.1beta2.zip

    In this case, if you make a mistake in html tags (forgetting to close a tag for example), WordPress fixes it automatically before the strings are saved in DB. But this breaks the serialization of data made by Polylang, making all strings unreadable.

    In Polylang 2.1, I changed the place where the data are stored and thus the WordPress option should not interfere anymore.

    Thanks, @platschi and @chouby, strangely I noticed that it seems to work in our test environment, but not in production.

    Another thing I wanted to ask, in a multisite setup, it seems to work only for Super Admin and not for normal Admin. Is that possible?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Polylang deleting string translations upon submit’ is closed to new replies.