Add category_shop.active migration to 9.2.0 upgrade - #1890
Open
PrestaEdit wants to merge 1 commit into
Open
Conversation
Companion for PrestaShop/PrestaShop#41643, which stores the category 'active' flag per shop instead of globally. Fresh installs get the column via db_structure.sql; upgraded shops need the same column, seeded from the existing category.active value. Uses add_column() so the directive is idempotent and receives the same AFTER clause as the fresh-install order, matching the pattern of PrestaShop#1887. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Core PR PrestaShop/PrestaShop#41643 moves the category
activeflag fromcategorytocategory_shopso visibility can be configured per shop in a multistore setup. Fresh installs get the column viadb_structure.sql; existing shops need the same column added and back-filled during upgrade, otherwise every read oncategory_shop.active(Category, Search, Manufacturer, Supplier, the two grid query builders and CategoryRepository) fails after upgrade.Follows the same idiom as #1887:
add_column()for idempotence and an explicitAFTER positionso upgraded shops match fresh-install column order.🤖 Generated with Claude Code