Open godismyjudge95 opened 1 month ago
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.
@seo:
Relevant lines I found:
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.
dd()
In the CP, have you selected Field or Custom in the dropdown?
Field
Custom
Could we see a screencast showing it happening in CP?
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:
@seo:
is parsed out - https://github.com/statamic/seo-pro/blob/master/src/Cascade.php#L216@seo:
even if Antlers is being used in the field - https://github.com/statamic/seo-pro/blob/master/src/Fieldtypes/SourceFieldtype.php#L52I placed a
dd()
call in the Cascade before the Antlers is parsed and that is how I found the@seo:
prefix was still there.