Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
One of the great advantages of Sitefinity is its flexibility and extensibility. A significant contribution for this has been made by the provider model that was chosen as essential part of Sitefinity’s architecture.
In simple words, what it gives you is the ability to connect Sitefinity to different data repositories (databases, xml files, file structure) so that you can pull content from multiple locations and mash it up in your pages. This means that you could simultaneously pull content items (news, events, images, taxonomy, user and role data… virtually anything that Sitefinity interfaces with) from your local Sitefinity database and other locations (your corporate CRM or ERP system or company website for example).
Additionally, providers allow you to have separate Sitefinity websites pull contain from the same data repositories, so that you can create content in one centralized place, and it would be reused by as many instances of Sitefinity as you need.
We will go through the steps to follow in order to achieve that result. First, let’s tackle this scenario: “We have several websites – a main corporate website and several subsidiary sites for some of our projects. We need to be able to create news and distribute it among all of them rapidly, with no duplication of effort. We should also be able to share categorizations and tags, as we would like to display only specific types of news (corporate news, project news, etc.) by filtering by taxonomy. Is that possible with Sitefinity?”
N.B. This is actual request I’ve received multiple times already.
The answer – just sit and watch!
For your viewing pleasure, I’ve gone through those steps in this video: Edit:
Note: One important thing to consider is permissions.
Since permissions are stored in the content item tables, they get carried across the different instances, i.e. are not independent on each Sitefinity website in this scenario. What you could do to ensure that permissions are set correctly on each website that shares providers is to create Roles with the same IDs and assign permissions to these. They will get carried across and work fine.
If you have any questions and comments, please do not hesitate to comment!
View all posts from The Progress Team on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.