Skip to content

### Did not kick in, I think it does now #56

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.

Sign up for GitHub

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

Open
evertalbers wants to merge 1 commit into
base: main
Choose a base branch
from
Open

### Did not kick in, I think it does now #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,7 +87,7 @@ Then you can use the tag

```{{ alt_seo:schema }}```

### Collection-level Blueprint Overrides
### Collection-level Blueprint Overrides
Collection-level Blueprints introduce another layer of complexity with Addons, therefore we have made the decision to not support them by default. Setting an override at collection level (for example default field values) will have no effect.

To support maximum flexibility, you may set `ALT_SEO_SUPPORT_COLLECTION_BLUEPRINTS=true` in your `.env` file to support collection-level overrides. However, subsequent changes made to either the published base blueprint, or fields subsequently added or modified to the vendor base blueprint will not be present in collections where you have previously overriden Alt-SEO fields.
Expand Down