Magnolia Community Forums: Get help with Magnolia: A couple Magnolia 4.5 questions

• 

  Tom Duffey (Not registered)

  A couple Magnolia 4.5 questions

  #1 by Tom Duffey (Not registered) on Jun 18, 2012 8:35:29 PM

  Hi Everyone, This morning we started playing around with Magnolia 4.5 and immediately ran into two problems that were a bit surprising based on our experience with earlier versions. 1) Missing or hidden TLD for stkfn. Historically we have been using JSP and I cannot find a TLD for the stkfn tags. The docs do not include a URI for the taglib. Does this exist? 2) Values of binary nodes now output as the binary data rather than the path. Previously, if we had a dialog w/control type "file" and did something like: ${content.headerImage} Magnolia would output the path to this image. Now it outputs the actual image data. Is there a new way to get the path to binary data like an image, PDF, etc.? Tom -- Tom Duffey tduffey@trillitech.com 414-751-0600 x102

  Hi Everyone,
  
  This morning we started playing around with Magnolia 4.5 and immediately ran into two problems that were a bit surprising based on our experience with earlier versions.
  
  1) Missing or hidden TLD for stkfn. Historically we have been using JSP and I cannot find a TLD for the stkfn tags. The docs do not include a URI for the taglib. Does this exist?
  
  2) Values of binary nodes now output as the binary data rather than the path. Previously, if we had a dialog w/control type "file" and did something like:
  
  ${content.headerImage}
  
  Magnolia would output the path to this image. Now it outputs the actual image data. Is there a new way to get the path to binary data like an image, PDF, etc.?
  
  Tom
  
  --
  Tom Duffey
  tduffey@trillitech.com
  414-751-0600 x102

• 

  mjablonski

  Full name: Maik Jablonski

  Posts: 29

  Last post: May 23, 2013 9:30:48 PM

  Registered on: Jun 12, 2012

  Re: A couple Magnolia 4.5 questions

  #2 by mjablonski on Jun 22, 2012 9:49:25 AM

  Hi Tom, [quote] 2) Values of binary nodes now output as the binary data rather than the path. Previously, if we had a dialog w/control type "file" and did something like: ${content.headerImage} Magnolia would output the path to this image. Now it outputs the actual image data. Is there a new way to get the path to binary data like an image, PDF, etc.? [/quote] without STK you can simply use [code]${cmsfn.link(content)}[/code], for STK it should be something like [code]${stk.getAssetLink(content, 'image')}[/code]. HTH, Maik

  Hi Tom,
  
  

  
  2) Values of binary nodes now output as the binary data rather than the path. Previously, if we had a dialog w/control type "file" and did something like:
  
  ${content.headerImage}
  
  Magnolia would output the path to this image. Now it outputs the actual image data. Is there a new way to get the path to binary data like an image, PDF, etc.?
  

  
  
  without STK you can simply use ${cmsfn.link(content)}, for STK it should be something like ${stk.getAssetLink(content, 'image')}.
  
  HTH, Maik

• 

  edgarvonk

  Full name: Edgar Vonk

  Posts: 58

  Last post: Apr 23, 2013 2:55:31 PM

  Registered on: Dec 1, 2010

  Re: A couple Magnolia 4.5 questions

  #3 by edgarvonk on Jun 22, 2012 10:34:01 AM

  Hi, regarding 1: I am also looking for the DTD (TLD) of the Magnolia 4.5 JSP taglibs. The [url=http://nexus.magnolia-cms.com/content/sites/magnolia.public.sites/ref/4.5.1/magnolia-templating-jsp/apidocs/index.html?overview-summary.html]API is documented[/url] but in my IDE (IntelliJ) these taglibs give an error because the IDE cannot find the DTDs. Can Magnolia make these available? Preferably on the URLs of the taglibs but anywhere is fine really. [code]xmlns:cms="http://magnolia-cms.com/taglib/templating-components/cms" xmlns:cmsfn="http://magnolia-cms.com/taglib/templating-components/cmsfn"[/code]

  Hi,
  
  regarding 1: I am also looking for the DTD (TLD) of the Magnolia 4.5 JSP taglibs. The API is documented but in my IDE (IntelliJ) these taglibs give an error because the IDE cannot find the DTDs. Can Magnolia make these available? Preferably on the URLs of the taglibs but anywhere is fine really.
  
  xmlns:cms="http://magnolia-cms.com/taglib/templating-components/cms"
xmlns:cmsfn="http://magnolia-cms.com/taglib/templating-components/cmsfn"

Sign in

To login on this forum, you can use your Magnolia Forge, Support or Partner account, or, below, your Google, Yahoo! or OpenID account. If you have trouble logging in, or any other sort of issue, please let us know in the Meta forum, on the user-list, or simply by email at forum-admin at magnolia-cms dot com.

... or sign in with: