While the main fields are updated to store data in JSON format, the revision tables are not.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | metatag-n3364475-4.patch | 8.59 KB | damienmckenna |
| #3 | metatag-n3364475-2.patch | 3.53 KB | damienmckenna |
While the main fields are updated to store data in JSON format, the revision tables are not.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | metatag-n3364475-4.patch | 8.59 KB | damienmckenna |
| #3 | metatag-n3364475-2.patch | 3.53 KB | damienmckenna |
Comments
Comment #2
damienmckennaComment #3
damienmckennaThis seems to work locally.
Comment #4
damienmckennaThe correct patch.
Comment #8
damienmckennaCommitted.
Comment #9
damienmckennaComment #11
jklmnop commentedFYI, 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!
Comment #12
damienmckennaI'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.