- Issue created by @DamienMcKenna
- Assigned to DamienMcKenna
- Status changed to Needs review
almost 2 years ago 9:26pm 2 June 2023 - last update
almost 2 years ago 112 pass, 2 fail - last update
almost 2 years ago 112 pass, 2 fail The last submitted patch, 3: metatag-n3364475-2.patch, failed testing. View results →
The last submitted patch, 4: metatag-n3364475-4.patch, failed testing. View results →
- last update
almost 2 years ago 113 pass -
DamienMcKenna →
committed 54147e31 on 2.0.x
Issue #3364475 by DamienMcKenna: Update scripts to convert JSON data on...
-
DamienMcKenna →
committed 54147e31 on 2.0.x
- Status changed to Fixed
almost 2 years ago 10:02pm 2 June 2023 - Issue was unassigned.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States jklmnop
FYI, this change broke our site and I just spent quite a while trying to debug it. I have custom code that expected the data to be a serialized array. I did not anticipate this kind of change from RC to stable as I wouldn't classify it as a bug fix. Just wanted to document it, in case others also have this issue.
That said, I'm very pleased that these values are JSON now! So much easier to work with! Appreciate all your hard work for this fantastic module!
- Status changed to Fixed
over 1 year ago 7:15pm 7 November 2023 - 🇺🇸United States DamienMcKenna NH, USA
I'm sorry you ran into that problem, but it was noted in the 2.0.0 release notes. I'm glad you were able to update your code to accommodate the changes.