topic Markup directive in head.ftl haven't been processed in Alfresco Archive

Markup directive in head.ftl haven't been processed

webdesigner — Sun, 03 Feb 2013 06:33:41 GMT

Hi,as asked by Dave Drapper in the comment:http://blogs.alfresco.com/wp/developer/2012/05/22/customizing-share-javascript-widget-instantiation-part-1/#comment-660this topic is created.1. Alfresco VersionI'm running Alfresco 4.1.1.9 (Un upgrade to 4.1.2 is planed, but later)2. Are you creating and de

Re: Markup directive in head.ftl haven't been processed

afaust — Sun, 03 Feb 2013 14:08:52 GMT

Hello,

I have never tried to target a .head.ftl with a customization, since it is always easier for me to simply add a JS / CSS dependency in the <customization>-tag, like David outlined in <a href="http://blogs.alfresco.com/wp/ddraper/2012/01/04/extensibilty-updates-roundup/">this blog post</a>. Since you're not doing anything different (and .head.ftl are hopefully going to be dying out in one of the next releases), I would advise you to use this approach, save yourself the need to modify core code and be upgrade-safe.

Regards
Axel

Re: Markup directive in head.ftl haven't been processed

webdesigner — Sun, 03 Feb 2013 18:55:40 GMT

Hello Alex,

this approach works!

Thanks for hint, module dependencies are of course much better as patches in the core files.

Regards
Vitali

Re: Markup directive in head.ftl haven't been processed

ddraper — Mon, 04 Feb 2013 08:53:45 GMT

The main thing to be aware of is the following…
.head.ftl files are processed in the same way as .html.ftl files. It is possible to extend a .head.ftl file (although not-advisable from 4.2 onwards as they're deprecated) but not via <@markup> directives… essentially anything you add in a custom .head.ftl file will be appended to the <head> element of the HTML page (the reason for this is that the content of a .head.ftl file can only go into one place - the <head> element - the content in a .html.ftl file can be targeted at different sections of the HTML page).

Your suggestion for the custom includes isn't really relevant going forwards… you can append, prefix, remove or replace any imports defined in a .html.ftl file and there are now consistently named <@markup> directives across all the Share WebScripts for you to do this. Since .head.ftl files are being removed and don't support <@markup> directives there is no point in adding this additional extension point.

I hope that explains everything,

Regards.
Dave

Re: Markup directive in head.ftl haven't been processed

webdesigner — Mon, 04 Feb 2013 09:56:51 GMT

Hi Dave,

thanks for your answer. I think the best way for custom includes is using of <dependencies> tag in customisation packages (as Axel suggested in the previous post). t doesn't require any core changes and is very flexible.

So no patches of head files anymore…

Best regards
and thanks for your help.

Vitali