Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content defaults for collection not used? #181

Open
marnickmenting opened this issue Sep 17, 2024 · 1 comment
Open

Content defaults for collection not used? #181

marnickmenting opened this issue Sep 17, 2024 · 1 comment

Comments

@marnickmenting
Copy link

I have set a content default for a specific collection.

CleanShot 2024-09-17 at 16 56 56

It shows correctly in the yaml file:

CleanShot 2024-09-17 at 16 55 15

But it does not effect the entry, not in front-end and not after publishing.

CleanShot 2024-09-17 at 16 57 17

I did not pay yet as I am testing, but assume that doesn't make a difference as other plugin functions work correctly.

Any clues?

=== Versions ===
laravel/framework: 11.23.2
statamic/cms: 5.25.0
withcandour/aardvark-seo: 5.0.0
laravel/sail: 1.32.0

@CandourDevs
Copy link
Contributor

Hi. Thank you for trying out our product. I have had a quick look at your issue. When you add content defaults for the meta title or meta description, they do not show up in the individual entries. Those fields will stay blank unless you choose to override the default. When I add some content defaults to a collection (leaving the entry fields blank), I can see my defaults in the front-end HTML - specifically in the <head>. The meta title property is shown in <title> tag and in the <meta property="og:title"> tag as content. I hope this helps. If you're still having trouble, let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants