WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #31819, comment 13


Ignore:
Timestamp:
04/04/2015 09:51:19 PM (6 years ago)
Author:
ericlewis
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31819, comment 13

    initial v1  
    33Plugins should (try) not to depend on markup looking specific for critical path functionality, as it is subject to change. Obviously, we should balance this statement with our project's commitment to backwards compatibility.
    44
    5 Also, if your goal is to perform a backup before upgrading a plugin, that would be better handled in the PHP application layer rather than triggering it via front-end user actions. This would remove the plugins' dependency on the markup to take a particular form.
     5If your goal is to perform a backup before upgrading a plugin, that would be better handled in the PHP application layer rather than triggering it via front-end user actions. This would remove the plugins' dependency on the markup to take a particular form.
    66
    77You could tap into the upgrade process via the [https://github.com/WordPress/WordPress/blob/4.1.1/wp-admin/includes/class-wp-upgrader.php#L356 upgrader_pre_install hook] and perform your backup. This hook runs before every individual plugin upgrade.