Plugin Deactivating after update

Hi Jayson

We’re not aware of this error. Could you share more details of the error you are seeing so we can investigate please.

Here is it recreated on a testing site.. But I have had a lot of customers with problems this morning because of the plugin being deactivated or deactivating if they run updates.

The error is below, but the plugin is actually there on the list, just not activated – it looks like you have renamed something without thinking of the consequences. I can send pictures of the process but essentially just wen to updates, ran the update – it said all completed successfully and then when visit the plugins page the plugins is not activate any more with this error:

The plugin yoco-payment-gateway/yoco_wc_payment_gateway.php has been deactivated due to an error: Plugin file does not exist.

Thanks for reporting this and the extra information. We’re investigating and evaluating how many would be affecting by this.

it is 100% hit rate and will effect everyone. The problem is you renamed your primary plugin file from underscores to hyphens.
yoco_wc-payment_gateway.php
changed to
yoco-wc-payment-gateway.php

Thanks Jayson. The renaming was done to conform with WP filename requirements but has had unintended consequences. In our testing we were able to upgrade successfully, but clearly this is an issue for our merchants.

We’re preparing a hotfix release, v2.0.1, to revert the change and avoid the issue for those upgrading in future. However, this will impact those merchants who have already installed v2.0.0. They will need to manually activate v2.0.1 after installation, for the very same reason.

We appreciate your input on this and our apologies for the impact.

This time make sure you communicate the breaking change before you publish the fix so that people are aware that there is an issue comming… If i had not caught this early alot of people I work with would have been having problems for weeks to come.

Yes, indeed, there will be notes in the change log about the issue, and we will be sending out additional communication to our merchants.

Hi Jayson. I’m marking this issue as resolved given the release of the new version and the communication to merchants.