fix: prevent db/backup from exporting triggeres twice#15854
Closed
gopeter wants to merge 1 commit intocraftcms:5.xfrom
Closed
fix: prevent db/backup from exporting triggeres twice#15854gopeter wants to merge 1 commit intocraftcms:5.xfrom
gopeter wants to merge 1 commit intocraftcms:5.xfrom
Conversation
angrybrad
approved these changes
Oct 8, 2024
Member
|
Thanks for the PR! Cherry-picked your commit into the |
Member
|
Craft 4.12.6 and 5.4.7 are out with that fix. Thanks again! |
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.
Description
If plugins include triggers in their tables, using
craft db/backupexports them twice, leading into importing problems since triggers have to be imported after the data to prevent their execution.