Bug in 2.0.2

  • Resolved Jeromes04

    (@jeromes04)


    2 years ago

    Hi,
    @jrmora made a video to showcase one part of the new problem :

    But there are others problem related to this:

    * Not able to change / modify the content after a translation. If you try to save it as a draft or publish it -> no change are made.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author malaiac

    (@malaiac)

    Will fix in 24 hours (away from my keyboard atm)

    Thread Starter Jeromes04

    (@jeromes04)

    unfortunatly no change with 2.0.3

    And the bad thing : no way to rollback to the last stable version

    Plugin Author malaiac

    (@malaiac)

    v2.0.4 should fix the problem, can you confirm ?

    Thread Starter Jeromes04

    (@jeromes04)

    Nope, sorry…

    Now the translation doesn’t xorks. And the other problem seem to continue.

    Thread Starter Jeromes04

    (@jeromes04)

    2.0.5 => same issues

    Thread Starter Jeromes04

    (@jeromes04)

    2.0.6

    When I click on translate, I am kicked from the post but translation is OK on Microsoft EDGE and SAfari…Not on Chrome ( no translation )

    When I go back to the post, I can modify and save my job.

    • This reply was modified 1 year, 12 months ago by Jeromes04.

    2.0.6
    Here it works with Opera (saving the draft with Polylang before).
    It does not exit the editor anymore.
    https://ibb.co/hDHhDKD

    Plugin Author malaiac

    (@malaiac)

    variations between browser feel like late cache invalidation
    still following this thread @jeromes04 feel free to add/resolve

    It doesn’t matter which browser I use. I still get kicked out to posts when clicking translate. I have tried with Edge, Opera and Chrome.

    Thread Starter Jeromes04

    (@jeromes04)

    it’s the same for me ( with cache resfresh / clean ) : I am always kicked but translation works except with Chrome.

    I still get kicked out, and I’m unable to use the plugin since I get kick out before anything is translated

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Bug in 2.0.2’ is closed to new replies.