• Resolved smadenli

    (@smadenli)


    [Moderator note – topic decapped – please do not yell on these forums]

    It will F*** up your site major.

    To the author,

    Please do not include experimental stuff to your major releases and test it thoroughly.

    This is a fantastic plugin, but this time, you broke it!

    https://www.ads-software.com/plugins/polylang/

Viewing 4 replies - 16 through 19 (of 19 total)
  • Have to jump in to this thread. I understand that it could be very frustating when something breaks. And thrust me on this one. Been working with clients using plugins and themes from theme marketplace (that i will not name here) that could make grown man (or woman) cry when it comes to breaking everything.

    But please understand that the men and women creating plug-ins and also doing it for free (OpenSource is not the same as free beer) + supports users (many of them on their spare time). With that in mind, take a nice walk or jump in to the WordPress Codex if you (or any other) feel frustrated next time (that’s a natural reaction on problems!). Later you come back and write an detailed error report (of course with a smiley at the end for the kids!).

    The plugindev will love you that way. For real. As Chouby stated in the thread. It’s almost an impossible task to test every theme/plugin combination. In this case it did seem to be the Nextgen Gallery that breaks things. And hey! Both you (the user) and the developer will get learn something new (that’s how development works in general), and that must count for something?

    I don’t know exactly how Polylang works, but i have seen a couple of plugins conflicting with Nextgen Gallery (or vice versa i should say). Most of them is conflicting with the Nextgen Gallery call for pluggable functions (at the top i the NextGen main plugin file).

    Cheers
    -> For the kids ??

    Thread Starter smadenli

    (@smadenli)

    Hello all,

    I run further tests:

    Restore the site to its original state (DB & files)
    this state is 3.71 wp, 1.1.6 polylang, nextgen 2.0.33
    uninstalled nextgen
    upgraded polylang 1.2.2 Works fine
    installed nextgen 2.0.33 install works no errors.

    but now the nextgen slide show will not work.
    Uninstalled nextgen
    installed NEXTCellent (back level legacy nextgen 1.9.13)
    works.

    I guess we now have to choose between polylang and nextgen V2:)

    I will also start a post in nextgen to see if this I something they can fix or even aware of. BTW new NEXTGEN V2 breaks other things as well but it is all nextgen related (so it appears), such as slide shows etc.

    As for the polylang, I think the author should still see if there is a way at least to signal the conflict or possibly a work around so that things does not break when upgrade is run. This is even more important now with the automatic updates.

    I will keep this open until we hear a final word from Fredrick

    Cheers :):):)

    Plugin Author Chouby

    (@chouby)

    Yes it seems that Nextgen gallery v2 has still some issues compared to v1.9.x.

    Yesterday I released v1.2.3 of Polylang which solves the conflict with Nexgen gallery during upgrade from v1.1.6 and older. Hopefully no other plugin will interrupt the upgrade process with this new version.

    Just one note: by default, the automatic updates concern only minor versions of WordPress and should not concern plugins and themes (except if you install a plugin which manages these automatic upgrades).

    Thread Starter smadenli

    (@smadenli)

    I am pleased to report that Polylang 1.2.3 installed smoothly and functioning as expected.

    Thank you Fredrick for staying on the problem and resolving promptly.

    This thread is now closed.

    :):):)

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘Do not install it.’ is closed to new replies.