This post is relevant to Sitecore solutions where user should login before accessing of user data. Below described 5 simple but important steps that should be taken into consideration to improve application security.
Very often every Sitecore developer has faced with the following situations:
- there is a shared content between multiple sites.
- there is a content tree that shouldn’t be exposed outside
In such a case would be great to have ability to manage url that is returned by LinkManager.GetItemUrl(). In order to accomplish this there is a need to implement a custom LinkProvider and configure Sitecore to use it.
Very often every Sicore developer fas faced with the necessity of adding new fields for some particular template. And this task is pretty easy! After new field has been added it appeared in Sitecore Content Editor.
But let’s imagine the situation when there is a need to associate new field with a template and not to show it in Sitecore Content Editor for everyone by some condition or don’t show it for anyone at all.
Once you decided to build the site the following most known difficulties be present during site’s construction:
- Complicated business logic.
- Significant number of stakeholders.
- Need to support several cultures (even you never heard about some of them)
- Plenty of content
Fortunately, Sitecore solves (or at least gives convinient way) most of them. But you should keep in mind that Sitecore is not a magic pillis, but it’s more than up to the challenge when it comes to building sites.