Did the Latest Polylang update knock out this plugin?

  • Resolved Oclair

    (@oclair)


    5 years, 6 months ago

    1. Just updated polylang and got notices in the admin that Hyyan WooCommerce Polylang Integration requires Polylang to function. (so something went bump in the dark due to a polylang update and set off a detection) As well I got a notice from Lingotek Translation for the same complaint regarding the requirement for polylang being installed.

    2. Tested the polylang support for our site and discovered it was not working.

    3. Deactivated the following plugins in this order Hyyan WooCommerce Polylang Integration, Lingotek Translation, and then polylang.

    4. Activated the following plugins in this order Polylang, Lingotek Translation, and then Hyyan WooCommerce Polylang Integration

    Result is that the site appears to be working again (TBD)

    Polylang Change Log
    2.3.11 (2018-10-03)
    Pro: Add action ‘pll_created_sync_post’
    Pro: Fix language and translations not included for tags in the REST API
    Fix Assigning a parent category breaking the hierarchy of translated category
    2.3.10 (2018-08-16)
    Fix Lingotek notice not dismissable
    Fix fatal error with the widget calendar
    2.3.9 (2018-08-14)
    Add a notice to inform about Polylang for WooCommerce
    Deprecate PLL_Pointer
    Fix bulk editing pages with no language breaking hierarchy #281

Viewing 1 replies (of 1 total)
  • Plugin Contributor jomo

    (@jonathanmoorebcsorg)

    5 years, 6 months ago

    No, the latest Polylang update did not normally knock out this plugin.
    Maybe you had a caching issue, eg opcache running stale code?
    Yes polylang added their upsell notice in 2.3.9 which I suppose they are entitled to do, but there was no actual change to break this plugin as far as anyone is aware.

Viewing 1 replies (of 1 total)
  • The topic ‘Did the Latest Polylang update knock out this plugin?’ is closed to new replies.