I tried, and failed, to add the SEO Checker data types in to my Fluidity set-up. While I hacked and hacked I have given up because there are too many locations where SEO Checker, perhaps not unreasonably, hits the ContentService (according to dotPeek).
It would be really wicked if instead of null references (for example) the data type just rendered a default view. Is that possible? I appreciate that this isn't exactly the purpose for which it was intended but none the less it would be really good if that was possible and it didn't look like it would be hard to achieve.
Sorry that you are having issues with this. Both datatype and metadata libvrary use context of the page to determine some defaults. It's on the list of things to improve but not the highest prio. Sorry about that.
Data types to not assume the property is part of a content item
I tried, and failed, to add the SEO Checker data types in to my Fluidity set-up. While I hacked and hacked I have given up because there are too many locations where SEO Checker, perhaps not unreasonably, hits the ContentService (according to dotPeek).
It would be really wicked if instead of null references (for example) the data type just rendered a default view. Is that possible? I appreciate that this isn't exactly the purpose for which it was intended but none the less it would be really good if that was possible and it didn't look like it would be hard to achieve.
Hi David,
Sorry that you are having issues with this. Both datatype and metadata libvrary use context of the page to determine some defaults. It's on the list of things to improve but not the highest prio. Sorry about that.
Best,
Richard
is working on a reply...