- Issue created by @heavystonehead
- π©πͺGermany heavystonehead
small note, I only recently noticed the problem (I've been looking for the cause for a week now) but it seems to have existed since version 1.x to 2.x and dev. I have had anomalies in the DB since December
-
lazzyvn β
committed 9505189f on 2.x
Issue #3443443: Data salad after change weight with new Taxonomy
-
lazzyvn β
committed 9505189f on 2.x
- π«π·France lazzyvn paris
It was fixed because of the original delta. check dev version. I never thought about this situation. No one swaps line and changes the entity's name to autocreates a new one
- π©πͺGermany heavystonehead
The reordering issue appears to be resolved. Now only the 2nd anomaly remains.
If there is a taxonomy βTest 1β with ID 5 and a taxonomy βTest 1 (2)β with ID x, test 1 is selected and saved normally.
If there is a taxonomy "Test 1" with ID 5 and a taxonomy "Test 1 (5)" with ID x, then Test 1 will be saved as "Test 1 (5)" with ID x.Thesis:
The terms are compared here and the ID is added as soon as terms exist. The existing IDs are not used here. This probably even happens afterwards, because correctly saved content is replaced with the wrong term after saving. - π«π·France lazzyvn paris
It's normal because it get id from title (id)
$result = preg_match('/\((\d+)\)$/', $value, $matches); if ($result > 0) { $value = $matches[$result]; }
so it takes the last one. I don't know how to do better
- Status changed to Fixed
8 months ago 12:05am 2 May 2024 Automatically closed - issue fixed for 2 weeks with no activity.