Closed (fixed)
Project:
Schema.org Metatag
Version:
3.0.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2026 at 16:53 UTC
Updated:
29 Apr 2026 at 08:35 UTC
Jump to comment: Most recent
Comments
Comment #2
damienmckennaComment #5
ptmkenny commentedI made a first pass at this because updating metatag to the latest dev release (April 1) caused a WSOD because I also have schema_metatag installed. My MR clears the WSOD but we should not need to change a constructor for a minor release.
Comment #6
damienmckennaFYI I opened #3583643: Revert accidental API changes because there shouldn't be API breaks in 2.2.1.
Comment #7
damienmckennaI fixed the API regression in MetaNameBase, hopefully everything else works correctly now too.
Comment #9
damienmckennaThe latest MR shows that the module works correctly with Metatag 2.2.x, so this is a-ok now, we don't need to make any changes to Schema Metatag after all.
Comment #11
ptmkenny commentedThat's fine, but I needed to use the dev version of schema_metatag with the dev version of metatag; if I use the 3.0.4 version of schema_metatag with dev version of metatag, I get a WSOD:
So the next version of schema_metatag may need to require the next version of metatag.