This kind of one-piece-of-information-reused-on-many-pages-situation is probably handled very well by the OOTB dynamic content "property from page". You could store all data like that on a specific page and then use this DC to include it in any editor.
Or am I missing something?
We did a token replacement system (twice, in fact). Users could enter this in TinyMCE:
[[SomePropertyName]]
When the page rendered, it would replace that with the contents of "SomePropertyName" off the start page. We did it with a control adapter. Worked quite well, and did have the overhead of interface complicated of Dynamic Content, plus the editor could see the placeholder and what property it corresponded to.
Hello Deane,
Thanks for the reply. Can you just paste some sample code on how it was achieved?
Hello All,
In a project can we have more than 20 dynamic content? Is it feasible to have that much. In our project there are more resuable sections so we have created a dynamic content controls. Take an example of WebSite name[Yahoo]. The site name will be used in almost all the pages. So if we want to place the site name in tinymce, i think from my knowledge we should create a DynamicContent for that. So till now for small small stuffs like FirstName, Last Name where there is resuable, we are creating a dynamic content.
Please let me know if i am in the right direction.
Thanks
RachappaSwamy