Sitecore - What are the pitfalls of storing content in the renderings field -
I want to know if someone has experience using parameter fields to store in site content. If so, what are the flaws?
In some cases, it seems like a lucrative idea because you can add subtle outlets to a page several times without creating a child's items and setting one's data source to each one of these children. Item .... but there are some disadvantages of inserting content in the rendering field:
-
This solution is not localizable because the reading field is shared, so no good for multi-language Sites
-
To edit the content (using the content editor) you will need to switch to the presentation tab, click on the details, select the celebration and then render Edit the parameters with a bit cumbersome.
Is there any more serious consequence of adopting this approach?
- There is no way to enable the field for page editor.
- You can complete it easily by using Page Edit R and setting up a data source template and data source location on your sublayout.
- I will repeat some things that you have already told - this is a shared field, so the content can not be localized.
- There is no way to reuse content stored in the parameter field.
- Even if you do this, it is difficult to obtain data from the parameters because they are XML-based (signal: add an image rendering parameters and see what you will get back) < / Li>
Overall, you are breaking the content and presentation partitions that are to be provided in the layout field. Please do not do that, one day a developer running your footsteps will come over it and then spend the whole day.
Comments
Post a Comment