Issue with version 4.0.0 and composer

I have the same problem! Could this be fixed? It keeps saying 4.0.0 is the latest version. Please release a new version with the fix, with better version number

• This reply was modified 2 years ago by rned.

Same problem here as well. Not sure why they would choose to release a fix with the same version as a previous bad release.

Hi, I use WordPress and all my plugins as composer-dependencies and experience the same problem: the “old” plugin-code is still installed under 4.0.0. Could you please release a 4.0.1 version with the updated code so that wpackagist.org can scan and index this new release?

Thanks!

Hi everyone,

Thanks for the feedback.
However, this 3rd party service that scans the wp.org repository to make plugins available as packages is not something we support for the time being.
So I’m afraid we won’t be able to create a new release version just for this, but we will keep it in mind in for the future.

Kind regards,
Niklas

@niklasinpsyde that is a disgraceful stance to take and a very bad developer practice. You released a broken version and then a fix with the same version number. That is not something to take lightly no matter if it is within the WordPress repository or a third-party service.

I agree with @coreyw. We have quite some sites which we have to manually constrain to the old version (when we need to deploy), whilst we always try to keep up with the latest plugin-versions. I urgently request to release a new (minor) version-number that allows us to update the plugin properly.

So I’m afraid we won’t be able to create a new release version just for this

It’s not “just for this”, it’s also for those users like myself who’ve disabled the bad BackWPup 4.0 version and are waiting for an update to a newer version that will fix the issues without having to uninstall, reinstall and reconfigure.

Meanwhile, backups aren’t running and I’m considering switching to a different plugin because the way you’ve been handling this is quite bad.