I was debugging and 3 weeks ago a commit went in that changed the way the upgrade path was handled. I don't have issue with the upgrade path itself, but the way it was handled. Eventually another "hook_update()" will be issued and to avoid problems, it is best practice to simply leave the function for the hook there while removing it's code so that someone doesn't accidentally code 8301 in the future as for those who upgraded to RC1 and then to a future version would be missing a crucial upgrade.

CommentFileSizeAuthor
#2 field_group-3092313-fix_hook_update_removal-2.patch375 bytesgeneralredneck

Comments

generalredneck created an issue. See original summary.

generalredneck’s picture

generalredneck
him/his
Primary language English
Location Texas, USA 🇺🇸
commented
Status: Active » Needs review
StatusFileSize
new field_group-3092313-fix_hook_update_removal-2.patch375 bytes

Please see the following patch

swentel’s picture

swentel commented
Status: Needs review » Reviewed & tested by the community

Right, that makes sense, thanks!

nils.destoop’s picture

nils.destoop commented
Status: Reviewed & tested by the community » Fixed

Good catch. Committed it to dev

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.