Field value saves @seo: prefix even when using Antlers

[godismyjudge95]

When saving a field value with Antlers value is being saved with a prefix of @seo: which causes any included Antlers to fail. You can manually edit the yaml and remove the prefix and that resolves the issue.

Relevant lines I found:

• Returns early before the @seo: is parsed out - https://github.com/statamic/seo-pro/blob/master/src/Cascade.php#L216
• Always prefixes the data with @seo: even if Antlers is being used in the field - https://github.com/statamic/seo-pro/blob/master/src/Fieldtypes/SourceFieldtype.php#L52

I placed a dd() call in the Cascade before the Antlers is parsed and that is how I found the @seo: prefix was still there.

[jesseleite]

In the CP, have you selected Field or Custom in the dropdown?

Could we see a screencast showing it happening in CP?

[jesseleite]

Going to close this for now, but if this is still an issue for you, please re-open and we'll absolutely take a look!