[FR] Support Vizy fields as meta source fields

[yoannisj]

Describe the bug

Vizy fields don't appear in source field dropdowns in the Content SEO settings for entry sections.

To reproduce

1. Add a Vizy field to a given Entry Type
2. Go to SEOMatic > Content SEO > Entry Section from Step 1
3. Select the Entry Type from Step 1 in the dropdown on the top left
4. Select "SEO Description Source > From Field"
5. Open the "Source Field" dropdown
6. The Vizy field from Step 1 is not listed in the dropdown options

Expected behaviour

Vizy fields can contain text which may be useful for SEO descriptions. It would be great if we could select Vizy fields as SEO field sources, for both the "From Field" and "Summary from Field" options.

Versions

• SEOMatic version: 3.4.24
• Vizy version: 1.0.12
• Craft version: 3.7.32

[khalwat]

Changing this to a feature request

[engram-design]

@khalwat Is there a mechanism for me to add support for Vizy fields, or is that all more or less hardcoded on your end?

[khalwat]

Hard-coded-ish on my end, but shouldn't be too hard for me to add here: https://github.com/nystudio107/craft-seomatic/blob/develop/src/helpers/Field.php & https://github.com/nystudio107/craft-seomatic/blob/develop/src/helpers/Text.php

[yoannisj]

Just realised that it would make sense to support Vizy field as source for Asset fields in sitemaps:

We often use Vizy fields as rich text fields (i.e. without adding any block type) because of how it stores the formatted the text as JSON (which gives us more control on how to render the field in the frontend).

For example: in the screenshot below Assets in the "Images" volume have a block-less Vizy field named "Description" where editors can add a caption to the images. The text stored in that field would be the best match for the Asset's "Caption" field in sitemaps, but it is currently not selectable:

[gregorydavidjenkins]

Would also love to be able to add a Vizy field as the source for SEO description. Specifically "Summary from field".

[khalwat]

Very doable

[torgeirbeyer]

Any updates on this?

[khalwat]

I'm planning to slate this for the next release!

[torgeirbeyer]

Has this been released @khalwat ?

[khalwat]

Not yet; sorry for promising it in the next release, and not delivering.