Sorry for the delay on this, I've been side tracked on a different project; but after relooking at this with a fresh mind, I've found it wasn't an issue with the STK after all... The new template was setup correctly, and not extended; however I just forgot to change the home page template to use the new custom template J Next time I'll sleep in the issue before posting!
Thanks for your time on this anyway Jan. Cheers, Brad From: [email protected] [mailto:[email protected]] On Behalf Of Jan Haderka Sent: Monday, 4 April 2011 5:58 PM To: Magnolia User-List Subject: Re: [magnolia-user] using stage element definition from incorrect template is by any chance your customHome extending the stkHome? that would be most likely reason for such merge. If not, can you post the whole site definition somewhere where we can see it? If you don't want to make it public, just open a support issue. HTH, Jan On Apr 2, 2011, at 6:17 AM, Brad Kazazes wrote: Hey Magnolians, I've got an interesting problem, which I think is a bug in the STK, but just wanted to make sure before I put it into Jira. When using the STK, I typically overriding the default STK template definitions with my own, as required, where I put them into my own project module. As I don't want the "stage" section used in my project, I've updated the prototype section to disable this element for all templates. I've then created specific homepage template definition, called customHome, which I want to use instead of the stkHome. While I've kept the original stkHome definition, I've removed it from the availability listing, and added my newcustomHome instead. Now, for some reason, when I display the homepage, I found that the stage section was continually being displayed. I even disabled it specifically in my customHome but still no luck. I was, however, finally able to remove it once I disabled it in the original stkHomedefinition, even though it was never referenced (nor inherited). I did a little debugging and noticed a bean merging section of the code which I assume is used to merge the prototype instance with the template instance, however for some reason it was merging three different Area instances which seemed to be the prototype,customHome & stkHome instances. Why its merging stkHome or even the enabled setting of this object is where I hit my debugging limits J Is this a bug or have I missed something? Cheers, Brad _____ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- _____ ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
