• Resolved absinthe

    (@fabioassenzio)


    Hello,

    I have two questions to ask about this feature/plugin that will be included in the core.

    The first question is about security. If an update fails and creates a fatal error, this feature will automatically rollback the previous version of the plugin, ok. So it means that a plugin security update cannot be applied if it causes a fatal error, for example because it is incompatible with another plugin. Is it better to have a broken site or a vulnerable site? For me it would be better to have a broken site that needs to be fixed, but maybe for others it isn’t.

    The second question is about database.
    How can we introduce a rollback procedure, which does not include a possible rollback of the database as well? If a plugin introduces a change to the db, the automatic update fails and the automatic rollback comes into operation, would we have a misalignment situation on the site?

    I mean, the rollback can be associated with a restore operation,right? Are we sure that restoring only files is okay 100% of the time?

Viewing 1 replies (of 1 total)
  • Plugin Author Andy Fragen

    (@afragen)

    There shouldn’t be a security issue. If the update process fails at it’s initial attempt and the previously installed plugin is rolled back, it will still show an update. The presumption is that the update process failure is transitory and another attempt will be successful.

    Second part re:database. If the new plugin update fails there is no new database changes. See above re: reattempting the update process.

    This is not about re-installing older versions of a plugin or theme. It is about rolling back the previously installed plugin/theme back into the appropriate place so that an incomplete/failed update doesn’t leave your site with a potential PHP error.

Viewing 1 replies (of 1 total)
  • The topic ‘Two questions :)’ is closed to new replies.