DISQUS

Olli · 11 months ago

With JSP one uses the custom magnolia JSP tags inside page templates to enable the "add/edit/remove paragraph" functionality. How does this work with Freemarker templates?

Boris Kraft · 11 months ago

Olli, this works pretty much the same as before. You can "import" the JSP tags and then use them. YOu can mix and match Freemarker and JSP paragraphs as well. So you can continue to use whatever work you have done so far, but still profit from the new power.

Example:

1. make the tag libraries available
[#assign cms=JspTaglibs["cms-taglib"]]
[#assign cmsu=JspTaglibs["cms-util-taglib"]]

2. You can use the tags like user-defined directives:
[@cms.editBar /]

Easy enough? Thought so! See http://wiki.magnolia-cms.com/display/DEV/Roadma... for preliminary release notes on 4.0 and more examples.

Edgar Vonk · 11 months ago

Excellent news Boris! Looking forward to using Magnolia 4.0.

A small question: is there any reason why you are still shipping Tomcat 5.5 with the Magnolia bundle downloads and not Tomcat 6.0? As far as I know Magnolia runs just fine on Tomcat 6. We do anyway. ;-)

Boris Kraft · 11 months ago

The reason is that by bundling with Tomcat 5.5, we clearly indicate that we support the Servlet Spec 2.4. The bundle's intention is not to provide a deployment-ready download (we prefer separate machines for deployment).

If you prefer to run on Tomcat 6, simply download the war-files instead.

- Boris

Edgar Vonk · 11 months ago

PS: we as a web agency do not believe in developing templates (or CSS files) within Magnolia. We believe templating is part of software development and belongs in the realm of IDE's, Subversion, Maven, etc. We have experience with other CMS's that offer web-based template development (and storage of templates within the CMS) and our experience is far from positive. For us it makes for much harder development (much easier to make mistakes, the browser is not an IDE, etc) and harder to do quality control. However I understand your motivation and am happy to hear that you fully understand and continue to support our way of work as well.

Cheers,

Edgar

Boris Kraft · 11 months ago

Edgar,

thanks for your comments. I completely agree. The "in-place templating" part is meant as an easy entry into the system (I definitely would not call Magnolia's inplace-templating "web-based template development"). It is very useful for those that have never seen a Magnolia template before (or for demo's) and it will help to understand how Magnolia works. This is somewhat aimed at PHP users who are used to mess around with the code in such a direct way (no flames please).

Anybody who has seen how easy Magnolia templating actually is will soon want to understand more and naturally progress towards an environment within an IDE. But making that entry hard is what has held people back from using Java-based systems. (I still remember the day I first heard of CLASSPATH. If Apple would have invented Java, CLASSPATH wouldn't exist.)

Magnolia lowers the barrier of entry to a Java-based CMS significantly. I for one find that outlook rather exciting.

Cheers
Boris

Edgar Vonk · 11 months ago

One more question about Magnolia 4.0. It may have been answered elsewhere already. Does Magnolia 4.0 intend to ship with Jackrabbit 1.5?

Boris Kraft · 11 months ago

Right now it does not but it is not completely out of the question. On the other hand we do intent to ship 4.1 about 3 months later, so if we don't ship JR 1.5 this time, the wait won't be long. If you have time to test against 1.5 let us know your findings, this will make it easier on us.

Neal · 9 months ago

How to use your new STK just copy all over ? how to
I'm totally new to Magnolia

Boris Kraft · 9 months ago

Did you read the release notes?
http://documentation.magnolia-cms.com/releases/...

We are working on docs how to use STK, but "copying all over" is exactly what you DONT do, please.

DE · 7 months ago

Fine. Almost your entire Documentation is under construction. Instead of telling him HOW to proper implement the STK, you point him to link with an incomplete documentation.

Since 24 hours we try to get some pages generated from Magnolia. it seems to be a very nice system, and we planned to purchase the Enterprise Edition for our clients, as we are a European WebHosting Company offering as well J2EE hosting with GlassFish.

But first of all: we are suffering problems even with the CE of Magnolia, and following the instructions given at: http://magnolia.sourceforge.net/21/qs/04_templa... leads to a disaster as the intro-page still says we have to install STK and no function can be seen to create a simple site.

I totally agree to Edgar's statement. Most CMS require agonycing pain to develop templates: Typo3, OpenCms, CMSMadeSimple, Mamboo. This is something what could be changed in future. As from my point of view a CMS doesnt make sense to avoid development of html/css/js/jsp/perl/php/python on the one hand, but on the other hand you spend weeks to create a proper template.

Meanwhile we are very close to the edge to give up with magnolia.
Regards,
DE.

Boris Kraft · 7 months ago

Dave,

I was in the process of sending you our draft docs. The link you have followed is documentation that is about 4 years old, as the 2.1 in the link should indicate (we are at 4.0). We should probably make sure we get rid of the old docs at Sourceforge; I was unaware it is still there.

I will contact you shortly
Regards
Boris

Boris Kraft · 7 months ago

Dave,

one more comment. None of our published documentation is "under construction". We only publish final documentation. Please visit http://documentation.magnolia-cms.com

Thanks
- Boris