Thank you for your response, Sara. You confirmed what Richard Hauer's suggested (he and I had a chat after I posted this but before your response).
This is the path I will take. Thanks again Tiffany, Sara, AND Richard for your help. Regards, EMB On Friday, May 31, 2013 6:00:18 PM UTC+10, Scodazzi wrote: > > Hi EMB, > i think you could develop a custom plugin performing all the steps you > described. > > So, when you are on a "foundation template" page instance, instead of > using the standard "Create page" functionality on "con_1", provide a > custom plugin in order to perform all the steps as you described: > 1) creation of a page (based on layout template) on "con_1" container > 2) reference from "layout template > con_2" to "foundation template > > con_1" > > Open Text supports all the RQLs to do that. > > Best Regards, > Sara. > > On Friday, May 31, 2013 6:03:38 AM UTC+2, [email protected] wrote: >> >> Hi, Tiffany. >> >> Thank you for your response. >> >> I tried it and it doesn't seem to work. >> >> I apologise for not being clear in my previous post. Here is what I'd >> like to be able to do: >> >> 1) Expand foundation template. >> 2) Double-click con_body container to put in clipboard. >> 3) Expand layout template >> 4) Select con_body container and click 'Reference Element in Clipboard' >> (Reference shows) >> 5) Create new instance of foundation and layout template (using a page >> definition) >> 6) Expand layout template instance >> 7) Reference to foundation's con_body kept >> >> I was able to get something similar working by decoding the HTML of the >> foundation's con_body in a render tag. I was just hoping that I could 'keep >> it clean' by using references or the like. >> >> Regards, >> EMB >> On Friday, May 31, 2013 12:54:42 PM UTC+10, tportman wrote: >>> >>> preassign the containers at the template level...that should do it for ya >>> >>> >>> On Thu, May 30, 2013 at 7:17 PM, <[email protected]> wrote: >>> >>>> Hi, everyone. >>>> >>>> I have this problem that I hope some of you can help with. >>>> >>>> So, say I have a container (con_1) on a foundation template and another >>>> container (con_2) on a ‘layout’ template. This layout template reside in a >>>> 'layout' container on the foundation template. After creating an instance >>>> of both content classes, I’m able to use con_2 to reference con_1 on the >>>> foundation. (See caveman diagram below) >>>> >>>> Foundation template >>>> >>>> ---con_1 >>>> >>>> Layout template >>>> >>>> ---con_2 >>>con_1 >>>> >>>> >>>> This works for what I’m trying to do as it allows me to keep my >>>> original content in the appropriate fields and just alter the layout using >>>> the ‘layout’ template. This is needed for content migration purposes. >>>> >>>> Now my question is can this be automated on the ‘layout’ template so >>>> that whenever an instance of the layout template is created, it knows to >>>> reference the foundation page’s container? I'm trying to do this for the >>>> benefit of the client's content editors ongoing maintenance. >>>> >>>> Any help is much appreciated. >>>> >>>> Regards, >>>> >>>> EMB >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "RedDot CMS Users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at >>>> http://groups.google.com/group/reddot-cms-users?hl=en. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> >>> >>> >>> -- >>> 312-515-0480 >>> www.tiffanyportman.com >>> [email protected] >>> >> -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
