3.0 breaks polylang support

  • Resolved stucyber

    (@stucyber)


    7 years, 10 months ago

    Dear Peter (and community),
    1st of all thanks for developing and actively mantaining this extremely useful small plugin. Just ufter updating to 3.0 today I ran in a polylang language variable validation error (?), resulting in only showing the main language-page, no matter which language currently being active. Deleting the second-language-error-page and after that recreating it did not help, more extensive testing has not been done by me so far. As a short term solution I just reverted back to the prior version. Any thoughts on that?

    Thanks in advance
    David

    • This topic was modified 7 years, 10 months ago by stucyber.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    7 years, 10 months ago

    Hi David,

    I’m sorry to hear that. It worked in my tests using the Twenty Seventeen theme. Can you please try to switch to Twenty Seventeen and check if its working on your site then?

    Peter

    Thread Starter stucyber

    (@stucyber)

    7 years, 10 months ago

    Hi Peter,
    thanks for your fast reply. You are right, 2017 works just fine, so I did some more testing. My setup (corner stones): recent wordpress, child theme of customizr v. 3.5.17. Plugins are not an issue, everything deactivated (except from yours and polylang) throws the same error.So the problem is maybe connected to customizr or your compatibility mode.
    More specific details on the error:
    Header and footer of 404-page load just fine in secondary language, only the body content (!) is still primary.

    Hope that helps and thanks for caring

    Edit: Maybe one more hint. I’m using the Simple Sitemap Plugin. After updating to 404page 3.0, the secondary language 404-page shows suddenly in the sitemap, the primary language one is still not visible (as it should be). So there’s maybe a database flag issue?
    David

    • This reply was modified 7 years, 10 months ago by stucyber.
    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    7 years, 9 months ago

    Hi David,

    thanks for the detailed description. I think I was able to identify the problem. Would you please test it with the current development version https://downloads.wordpress.org/plugin/404page.zip?

    Peter

    Thread Starter stucyber

    (@stucyber)

    7 years, 9 months ago

    Hi Peter,
    your dev build nails it – great job on this one! (Almost) everything is back to normal with Customizr activated, now. Only remaining symptom: The secondary language 404page still remains visible in the sitemap, though – but I can exclude this manually.

    I leave you to mark this as solved when you’re ready for it and really appreciate your support!

    Thanks and best wishes
    David

    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    7 years, 9 months ago

    Hi David,

    should be fixed now also. Please do me a favor and retest the latest dev build https://downloads.wordpress.org/plugin/404page.zip.

    Thanks
    Peter

    Thread Starter stucyber

    (@stucyber)

    7 years, 9 months ago

    Dear Peter,
    that’s it. Everything back to normal!

    Thanks for your efforts 🙂
    Greetings
    David

    Plugin Contributor Peter Raschendorfer

    (@petersplugins)

    7 years, 9 months ago

    Thanks for testing. Final 3.1 is out. Marked as resolved.

    Thread Starter stucyber

    (@stucyber)

    7 years, 9 months ago

    Marked as resolved.

    and works perfectly fine. Thank you!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘3.0 breaks polylang support’ is closed to new replies.