Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author ulfben

    (@ulfben)

    I only update a plugin when I’ve made a substantive change to it. Changing a version number in the readme everytime WordPress updates is useless busywork.

    The plugin works. Enjoy it.

    Thread Starter Fizzgigg

    (@fizzgigg)

    I respect that, and I have no clue how much work it is to make a tiny update just to make the version notice on ww.wp.xz.cn up to date with the current update, I’ll take your word for it.

    From my point of view though, with the kind of sites I deal with, as long as a plugin isn’t compatible with the new version, I put the update of WordPress on hold. And if it takes time, I switch to another plugin that is compatible in the notes on the plugin page. A plugin that isn’t said by the author to be compatible with the new version is by me concidered to be incompatible and not the other way around.

    I know that I am whining, but it’s just that I think your plugin is to good not to care. 🙂

    Plugin Author ulfben

    (@ulfben)

    WordPress core updates are way too important to ignore while waiting for bullshit compatibility ratings on plugins.

    You know the rules; be up to date or out of order.

    And no matter the authors claim, updates on production servers will never be without risk. I’d recommend you try and sort out a testbed or some method to dry run updates.

    Thread Starter Fizzgigg

    (@fizzgigg)

    I know, I know. And just to make it clear, if I was fuzzy before – if nothing has to be done to the plugin itself (as in this case) all I asked for was an update to the “Compatible up to:” field here on ww.wp.xz.cn. Nothing more, nothing less, and no unnecessary work with the plugin itself and pushing out a new version, just an update on the information.

    Plugin Author ulfben

    (@ulfben)

    Yeah, that’s how I read it. 🙂

    But here’s my perspective; I maintain half a dozen active plugins. WordPress core updates (on average) every other month (2 planned releases per year and 1-2 minor updates between each). I just can’t be arsed to edit and commit all those readmes for no reason.

    For what it’s worth, it was 8 years since last time a WordPress update broke this plugin (2007, with the introduction of the taxonomy system which restructured the database entirely). Besides, I run all of these plugins on my various sites. I’d notice breakage pretty quickly. 🙂

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

The topic ‘WordPress 4.2 compatibility?’ is closed to new replies.