Dynamic metadata not showing up until edit
I added a new dynamic metadata checkbox with one item (value is Yes) and default = true. If I look at existing assets, the checkbox doesn't exist (and doesn't appear in index blocks). If I edit the asset and submit, the metadata is created. I think that the checkbox should be added to existing assets without having to edit each one. I'm using 6.10.9
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Ryan Griffith on 19 Nov, 2012 01:42 PM
Hi Sara,
It sounds as though you are running into this known defect in which dynamic metadata fields added after an asset was created are not present until after the asset is modified again.
Please feel free to track the progress of this issue to see if it has been resolved in a future version of Cascade.
In the meantime, the workaround for this would be to edit the asset(s) that have this new field. Another option could be to use web services to essentially "touch" each affected asset by reading and editing the asset, but not changing anything.
Please let me know if you have any questions.
Thanks
2 Posted by harlenweb on 19 Nov, 2012 01:57 PM
Thanks, Ryan - that is the problem - I appreciate your pointing that out. I was able to get around this because I didn't have many existing assets (just developing the site) and I could edit each one. But this would be difficult if there were many existing news articles, e.g., and the client would like to add a new feature. In that case, it might not be practical to edit each article. And not all clients use web services. For that reason, just as a feedback point, this bug doesn't really seem minor to me.
3 Posted by Ryan Griffith on 19 Nov, 2012 02:07 PM
Hi Sara,
Glad to hear your site was small and you were able to remedy things.
I agree the workarounds are not ideal if we're talking about a larger site or clients who do not use web services. For that reason, we have moved the issue further up on our development timeline.
Have a great day!
Ryan Griffith closed this discussion on 19 Nov, 2012 02:07 PM.
harlenweb re-opened this discussion on 19 Nov, 2012 02:20 PM
4 Posted by harlenweb on 19 Nov, 2012 02:20 PM
thanks, Ryan!
--
Sara Haradhvala
Manager, Harlen Web Consulting LLC
[email blocked]
Tim closed this discussion on 19 Nov, 2012 02:58 PM.