This depends on where you save the area script. If you save it in the /templates/areas folder as given above, the templateScript node value should be /templates/areas/mainArea.ftl.

Hi Mike,

Docs are catching up with development. The STK section needs updating for sure. However, here are some up-to-date docs on the topics you listed.

Templating tutorial for 4.5 http://documentation.magnolia-cms.com/templates/i...
Blossom 2.0 http://documentation.magnolia-cms.com/modules/blo...
Module mechanism http://documentation.magnolia-cms.com/reference/m...
Series of blog posts by Greg on how to build project http://dev.magnolia-cms.com/~gjoseph/dont-build-m...

Hi Kunal,

I assume the video file is in the docroot directory of your webapp, not in the DMS root. So you are linking to a resource on the file system.

You should not need to add special rules. The default set of rules will work. See how the stkVideo component works. The definition is in Templating Kit > Template Definitions > /components/content/stkVideo. By default a DAM control allows the user to either upload a video or select one from the DMS. Add your own edit control to the dialog that allows the user to type a path to a video on the file system.

Regardless of where the video file resides, the stkVideo component renders an HTML5 compliant video player on the page. The video starts playing when the user clicks Play.

See also Magnolia Community Forums: Get help with Magnolia: Storing documents directly to file system?

When you generate a new key (Tools > Activation), the system writes the key into the keypair.properties file. So the file won't be empty anymore.

Also, see MAGNOLIA-4068 about the changed key name and location since 4.5.2. http://jira.magnolia-cms.com/browse/MAGNOLIA-4068

Good catch. Fixing this now.

Great! Please post your complete solution on the Magnolia forum, Kunal. That way you get most viewers. I will link to your post from official documentation.

text/xml worked for me. I also tried with application/xml MIME type which did not work - the browser downloaded the file.

Check that your sitemap file has the a .xml extension. Flush Magnolia and browser caches.

Hi Kunal,

By default, content served from the DMS workspace is treated as an attachment rather than inline content. This means that the browser downloads the content rather than displays it on the page. You can turn off this behavior per MIME type. See http://documentation.magnolia-cms.com/modules/dms...

In your case, add "text/plain" as a rejected MIME type. Flush the cache (Tools > Cache tools in Magnolia 4.5) and your browser cache before reloading. If you have other .txt content that you still want to serve as downloads, use the path option instead, documented on the same page.

Yes, Scheduler 1.4.3 should work with Magnolia core 4.4.6. You can check dependencies on the core and other modules in a module's pom.xml file (Project Object Model). The pom for Scheduler 1.4.3 says it depends on Magnolia core 4.3. So the later 4.4.6 should work too.

Looks like I was wrong about the zip upload. It is not available in the resources workspace. Zip upload is available in the dms workspace where theme images used to prior to Magnolia CMS 4.5. It is definitely a feature that is needed in resources so I'm sure it will be added soon.

To upload a single image file:
1. Right-click a folder in the resources workspace and select Create a new item.
2. Double-click the "Missing:" value in the Resource type column. The value changes into a dropdown. From the drop down, select Binary.
4. Double-click the name "Untitled" and type a new name for the image. This is the name that is used when referencing the image from CSS for example. Magnolia replaces spaces and other illegal characters with hyphens.
5. Double-click the file icon. The edit dialog is displayed. Browse to an image file on your computer.
6. In the same dialog, go the Advanced tab and type the file extension into the Extension box, for example "jpg". Click OK.