- Issue created by @fbreckx
- 🇪🇸Spain stadoom
Our customer requires to set several Questions and Answers into the metatag using the Pivot option, so it is better not to limit these fields maxLength and change the field type to textfield.
Here is the patch for 3.0 version. - last update
over 1 year ago 62 pass - Status changed to Needs work
about 1 year ago 4:09pm 20 July 2024 - 🇺🇸United States damienmckenna NH, USA
This is the wrong approach - the parent PropertyTypeBase class shouldn't know about individual tags.
- 🇳🇱Netherlands daluxz
The patches in this issue didn't work for me.
We are using the FaqPage Questions and Answers with quite long tokens like:
- [node:field_paragraphs:entity:field_node_faq:0:entity:title];[node:field_paragraphs:entity:field_node_faq:1:entity:title];[node:field_paragraphs:entity:field_node_faq:2:entity:title];[node:field_paragraphs:entity:field_node_faq:3:entity:title]
- [node:field_paragraphs:entity:field_node_faq:0:entity:field_text_long_answer];[node:field_paragraphs:entity:field_node_faq:1:entity:field_text_long_answer];[node:field_paragraphs:entity:field_node_faq:2:entity:field_text_long_answer];[node:field_paragraphs:entity:field_node_faq:3:entity:field_text_long_answer]
So these fields run out of space very quickly.I created a new patch in which a new parameter ("long") is added. Whenever a plugin uses this parameter, a textarea is used instead of a textfield, and the maxlength is removed in that case.
See the attached patch.
- Status changed to Needs review
2 days ago 9:06pm 4 October 2025