While the main fields are updated to store data in JSON format, the revision tables are not.

Comments

DamienMcKenna created an issue. See original summary.

damienmckenna’s picture

Assigned: Unassigned » damienmckenna
damienmckenna’s picture

Status: Active » Needs review
StatusFileSize
new3.53 KB

This seems to work locally.

damienmckenna’s picture

StatusFileSize
new8.59 KB

The correct patch.

The last submitted patch, 3: metatag-n3364475-2.patch, failed testing. View results

Status: Needs review » Needs work

The last submitted patch, 4: metatag-n3364475-4.patch, failed testing. View results

  • DamienMcKenna committed 54147e31 on 2.0.x
    Issue #3364475 by DamienMcKenna: Update scripts to convert JSON data on...
damienmckenna’s picture

Status: Needs work » Fixed

Committed.

damienmckenna’s picture

Assigned: damienmckenna » Unassigned

Status: Fixed » Closed (fixed)

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

jklmnop’s picture

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!

damienmckenna’s picture

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.