Closed DavideTriso closed 4 years ago
Weird, seems that YAML is claiming something is wrong in the format, but I cannot replicate the problem.
The error appears every time I set 'changefreq' to 1 in the admin plugin. I have made some tests and changing the validation type to 'number' for 'header.sitemap.priority' in the blueprint sitemap.yaml seems to solve the problem.
Cannot replicate. If anyone else stumbles on this, comment here
Setting the changefrequency to 1 causes an error:
"cannot resolve a node with !<tag:yaml.org,2002:float> explicit tag at line ..., column ...: priority: !!float 1"