Jump to content

4.7 schema migrations were added to the 4.5 upgrade block

Go to solution Solved by Matt,

Recommended Posts

The database changes related to the image scanner (adding core_files_temp.requires_moderation, core_attachments.attach_moderation_status, and core_image_scanner_logs) were added to the upgrade routine for 105013 (4.5.0 beta 1) rather than one of the 4.7 releases.

This doesn't cause problems for most people because step 2 of the upgrade routine is to check the database schema, although this could cause problems in future if future upgrade steps act on this new table and someone is upgrading all the way though (and similar bugs in future could be more of a problem if they aren't just straight forward add queries).

I ran into this because I replaced the upgrade wizard with a significantly (order of magnitude) faster CLI implementation, but that script had omitted the databaseCheck step.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...