Adding nested content area to parse file


(Oliver Kass) #1

Hi folks,

 

Hopefully this is quite a simple question with quite a simple answer but not having a great deal of experience with parse files and MySource tags etc I thought I'd seek some advice. 

 

I'm looking at adding a new nested content area to our site's parse file in order to get Google Tag Manager's script to appear directly after the body tag on all pages.

 

On the surface it looks like all I need to do is add something like this after the body tag in the parse file then I'm good to go with nesting the new code snippet via our main customisation:

 

<MySource_AREA id_name="google_tag_manager" design_area="nest_content" cache="1" />

 

Is it really that simple or do I need to take anything else into consideration before committing to changes on the parse file?

 

Thanks

 

Oli

 


(Nic Hubbard) #2

You need to do something like the following:

<mysource_area id_name="main_search" design_area="nest_content">        
    <mysource_set name="type_codes" value="page" />
</mysource_area>

You would then need to create a Design Customization to configure the nested area. After you have done that, make sure to apply the design customization to the pages/site that you want by going to the Settings screen of those assets.


(Oliver Kass) #3

Thanks Nick. Is updating the parse file process heavy in Matrix i.e. is it a big ass Hippo job or just a quick refresh?  

 

Also I'm assuming it won't have any effect on current customisations until I configure the new area? At the moment we only have a handful of customisations I just want to avoid breaking anything on the front end.


(Nic Hubbard) #4

The Hipo time depends on how larger your parse file is and number of customizations.

 

If you have a top level customization then you can configure the nested content area into that one. If not, you will have to do it for each customization where you are wanting to use the nested area.


(Oliver Kass) #5

OK. Thanks. We've got a top level customisation so should just have to add it there.