Admin backend seems following order language?

  • Resolved vasek608

    (@vasek608)


    1 year, 9 months ago

    Hi, my site language is “English”, admin user is using “Site default” language, web is translated into Czech & German, via Polylang.

    After upgrading from 3.2.13 to 3.3.3, I am experiencing a following weird behavior: admin backend seems following order language?

    Example – when admin i just in woocommerce order overview, all backend is in english (which is expected and correct):

    But when opening details of individual german order, then the admin backend becomes partially translated into german:

    Such behavior is imho not correct (at least in 3.2.13 this was not happening – there admin was always in user language). I tried to activate/deactivate all modules in ttfp settings, but seems not affecting it.

    Expected behavior: the admin backend shall be always in admin user language, shall not follow the language of individual orders..

Viewing 4 replies - 1 through 4 (of 4 total)

  • I have a similar problem. For example, the WOO plugin is not working in the primary language. If I deactivate your plugin – everything works fine

    Plugin Author Marcin Kazmierski

    (@marcinkazmierski)

    thanks for your suggestion, I fixed it in 3.3.4 version.

    I added in “TTfP Settings” page one more option: “Force translate admin dashboard:”

    Hi @marcinkazmierski

    I’m actually getting some unexpected behaviour now as a result of this latest change.

    I think the change makes sense in general – the admin area should be translated to the language you have selected in the admin bar as opposed to the language of the post you’re editing. But we’ve noticed that this also affects things like links added through the WYSIWYG and post object/relationship fields in ACF.

    The WYSIWYG only seems to let me select posts created in the site’s Primary language, and ACF post object/relationship fields only return posts from the language selected in the admin bar – making it difficult to edit translated content.

    If I disable the new setting, ACF returns posts from all languages which equally difficult to work with.

    Historically these fields only returned posts from the same language as the one being edited (which I would think is the preferred behavior).

    I’ve reverted to V3.3.3 for the time being but would you please be able to let me know if this is intended behaviour going forwards as we may need to implement our own solution in our theme if so.

    Plugin Author Marcin Kazmierski

    (@marcinkazmierski)

    @switchdan I have updated plugin to version 3.3.5. Please confirm that everything is OK.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Admin backend seems following order language?’ is closed to new replies.