Contentprovider example for #EPiServer, Former PageProvider, Part one

Content Providers in EPiServer is a way of publishing external data as pages/blocks etc… but also a way of publishing content in several places on your web.

Last year I upgraded our web from EPiServer CMS 6 to 7.19, and later on to 8. One big breaking change was the Page Provider changing to Content Provider. I had big problems finding providers working for us. Not even the ClonedContentProvider from Alloy did work for us. Thats why I publish our solution of a ClonedContentProvider. The major difference in our version is that we don’t use GetDescendentReferences and ResolveContent, instead implementing ListMatchingSegments.

Content Providers in EPiServer is a way of publishing external data as pages/blocks etc… but also a way of publishing content in several places on your web. Due to the lack of publishing in several containers/parents, this is a way of cloning data and keeping friendly urls.

http://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/9/Content/Providers/Content-providers/

Registering a provider in webconfig / episerver

To not filter by Category, use -1.

ClonedByCategoryContentProvider

GIST: https://gist.github.com/LucGosso/

More reading Content Providers:

Like it? please up vote
0