Custom content provider means "CMS don't know anything about the content, and you provide all the necesary information about content through your custom content provider implementation" - some details can be seen here https://docs.developers.optimizely.com/content-management-system/docs/content-providers
So for methods you mention to work, you need to implement necessary logic inside your custom content provider.
For example, DefaultContentModelUsageService.ListContentOfContentType internally goes through all the registered content providers, and calls ListContentOfContentType for those - so you need to implement that logic in your custom content provider to receive those content, etc.
Thanks, Vladimir.
The problem then becomes how to implement that listing in out content provider. Again, the end goal is to simply(?) list all the content of a certain type. I was hoping that it would be registrered by CMS internals somewhere for easy retrieval, but it sounds like that might not be the case here.
Unless if your content provider overrides and implements ListContentOfContentType, it will fall back to the base class which returns empty. otherwise it sounds like a correct approach.
A word of caution though - avoid using DDS, as it's terrible for performance Dynamic data store is slow, (but) you can do better. – Quan Mai's blog (vimvq1987.com) . but maybe you know that already
Hi! We have this scenario:
Searching around, I've found some approaches using
IContentTypeRepository
andIContentModelUsage
to load all content of a specific type like so:However, despite using a few images on the site and the
type
seemlingly loading correctly,usages
always end up empty.