-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
setMeta and setMetaDefaults not working as expected #662
Comments
Could you please provide the code that shows how you're using it? Thanks! :) |
Sure, I can commit it later ... :) What's the intended behaviour for each though? |
I don't personally have the knowledge of what each one does exactly, I do know |
Ah, ic :) Here's how I use it to allow posts for multiple site areas:
Within YAML I set
... and doing so just now ... it actually works ... tadaaa :D ... seems like some automagic got it working. Reverting to previous versions did not reveal a typo, different YAML or else :/ |
So How is |
|
Thanks Benjamin. Where can the MetaDefaults and their respective default values be found and looked at? |
Closing due to age. Ecosystem has likely fixed this. Try again with v6.80 or later. |
Trying to overwrite documents' meta info in docpad.coffee I tried
I.
setMetaDefaults
at first but it seems thaturls
gets not set?II. ... switching to
setMeta
thenurls
does not get reset when already defined in YAML?Is both the expected behaviour?
What I'd somehow expected is
setMetaDefaults
to set the defaults for any key passed in andsetMeta
to set any key to the value passed in, hence overwriting both default and a documents' property if defined in YAML.Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: