- Issue created by @monaw
- πΊπΈUnited States DamienMcKenna NH, USA
How did you create the field without the typical "field_" prefix? I wonder if there's a collision happening somehow?
- πΊπΈUnited States DamienMcKenna NH, USA
Please try naming the field something different, e.g. "meta_tags", see if that works. If it ends up being a compatibility issue we can add a note to the docs and via hook_requirements().
i upgraded to 2.1.0 and created a meta tag field named "meta_tags" in my test content type and was able to add a new test content without the above error. i'm not quite sure whether the upgrade to 2.1.0 or naming the field "meta_tags" or both solved the problem but i consider this problem solved so feel free to close this issue, thanks!
- πΊπΈUnited States DamienMcKenna NH, USA
I'm glad you were able to work out a solution.
Let's turn this into a documentation task so others can be aware of the problem.
ok, i did a bit more testing:
- if i name my meta tag field "meta", then it doesn't show up in my create/edit form, whether the form widget is configured to use the sidebar or not; if i name it something else (like "metatags"), then it shows fine on the create and edit forms
- since i am now able to add test content nodes, it is safe to assume that version 2.1.0 fixed the WSOD error mentioned in my original issue text