Hooks Needed for WP 2.7 Upgrade Features
|Reported by:||markedwards||Owned by:||DD32|
Seems as though there are no action hooks in place that get called before Wordpress tries to upgrade plugins, themes, and the core itself. In my perspective this is a big oversight that will cause problems down the road and wind up breaking a lot of sites. Some plugins will need to know in advance that an upgrade is about to take place for the plugin itself or the core in order to take appropriate actions that maintain site stability. I can image that the same holds true for many complicated themes. This lack also presents a problem on multi-admin sites - what if one admin inadvertently begins an upgrade without realizing that another admin isn't ready for that to happen? The results could potentially be catastrophic and lead to extended downtime, loss of work, loss of data, etc.
PLEASE include action hooks in all the core upgrade functions BEFORE any file copying/deleting takes place. This will allow a diverse set of safety checks to be put in place by whoever needs them, which will prevent disasters.
I marked this high priority - based on my experiences managing and developing high traffic multi-editor and multi-admin sites I truly think it's warranted and should be handled before 2.7 officially launches. After all, it's just a series of do_action calls - nothing major to get this straightened out.
Change History (7)
- Priority changed from high to normal
- Summary changed from Hooks Need for WP 2.7 Upgrade Features To Avoid Disaster! to Hooks Needed for WP 2.7 Upgrade Features