Closed (fixed)
Project:
Web Experience Toolkit
Version:
5.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Nov 2023 at 20:01 UTC
Updated:
19 Dec 2023 at 14:23 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
joseph.olstadComment #3
joseph.olstadComment #4
joseph.olstadComment #5
smulvih2@joseph thanks for opening a new ticket for this! Will see if I can reproduce the issue to test this fix.
Comment #6
jmdeleon commentedWas getting this same error. Patch in #2 fixes it.
Comment #7
skaughtI'm assuming #6 also manually deletes your own config too.
// Update hook 8501 wasn't run correctly for some reason, or the yml was deleted.in your patch you commented.
also: you do reset 8501 with the new namespace than it was it updated. (ln 678 after patch #2). this changes the condition to see if a user actually changed any config in their site. is this confirmed?
Documentation?
How did you delete the config to begin this test? It's as much a fail point should someone have the ability in an active project to manually delete an active config. We are patching against a dev line if not just from the 5.0.1 release, changing hashes and dropping a config...
Comment #8
joseph.olstad@SKAUGHT
An alternative test is this:
Remove the countries yml from your filesystem
import the configs so that it's deleted from your schema.
Now run the following drush commands.
doing this without the patch will crash and you'll not be able to upgrade
add the patch and the countries are brought in correctly without crashing.
Comment #9
skaughtYour overlaying a rollback situations.. I get that..
- physically removing the config form FS, then reset instance of triggered hook.
I do see this is a complex developer sequence to cause a fail. is this real-world then from the 5.0.1 release. or any sites that upgrade from v4 itself?
In the moment this seems more like {entity}->isNew() doesn't catch something as could be hoped..
Comment #10
skaught@joseph.olstad
how does this feel to you sir!
just clean from dev line (I didn't edit from yours)
Comment #11
joseph.olstadHi @SKAUGHT,
I deleted my countries yml, imported config to make sure the countries were gone then I ran your patch, set the schema version to 8501, ran updb, the end result is that I no longer had any countries.
The countries were not restored.
I prefer patch #2 because it brings back the countries with the expected namespace.
I also re-tested patch #2 , if I have the correct countries value, there's no crashing either when re-running the schema updates with or without expected countries that are brought in (or not) with the new 8501.
Comment #12
skaughtOkay, that sound good to me too!
let move with patch #2.
Comment #14
sylus commentedCommitted and attributed thanks for the fix everyone :D
Comment #16
joseph.olstadfixes we made to 5.0.x were not fully merged into 5.1.x
I just got tripped up on this with 5.1.0 , made a new ticket here:
#3409755: 5.1.x requires a merge from wxt 5.0.x - settings (wxt_core countries) fix is missing