Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
3 Spelling and grammar fix.
source | link

I made some custom modifications to a plugin. When we get a notice that there is an official upgrade for this plugin in WP, a dev needs to manually do the upgrade because the changed files have to be integrated with the new version.

We don't want a staff member to accidentally click the upgrade button on this plugin while going thruthrough a series of upgrades.

However, we still want to see the upgrade notification, so that a dev can schedule tothe update, so. So increasing the version number in the header to some really high value is not a solution, because it blocks that visibility.

How can I can block WP from being able to upgrade and the plugin still be valid?

I made some custom modifications to a plugin. When we get a notice there is an official upgrade for this plugin in WP, a dev needs to manually do the upgrade because the changed files have to be integrated with the new version.

We don't want a staff member to accidentally click the upgrade button on this plugin while going thru a series of upgrades.

However, we still want to see the upgrade notification so a dev can schedule to update, so increasing the version number in the header to some really high value is not a solution because it blocks that visibility.

How can I can block WP from being able to upgrade and the plugin still be valid?

I made some custom modifications to a plugin. When we get a notice that there is an official upgrade for this plugin in WP, a dev needs to manually do the upgrade because the changed files have to be integrated with the new version.

We don't want a staff member to accidentally click the upgrade button on this plugin while going through a series of upgrades.

However, we still want to see the upgrade notification, so that a dev can schedule the update. So increasing the version number in the header to some really high value is not a solution, because it blocks that visibility.

How can I block WP from being able to upgrade and the plugin still be valid?

2 edited tags
| link
    Tweeted twitter.com/StackWordPress/status/1000006832243474432
1
source | link

Preventing a plugin from updating

I made some custom modifications to a plugin. When we get a notice there is an official upgrade for this plugin in WP, a dev needs to manually do the upgrade because the changed files have to be integrated with the new version.

We don't want a staff member to accidentally click the upgrade button on this plugin while going thru a series of upgrades.

However, we still want to see the upgrade notification so a dev can schedule to update, so increasing the version number in the header to some really high value is not a solution because it blocks that visibility.

How can I can block WP from being able to upgrade and the plugin still be valid?