Return to Jive Software

Skip navigation
Up to Discussions in Developers
3,813 Views 6 Replies Last post: Jun 12, 2009 5:26 AM by bcswissre RSS
whoiskevin Novice
whoiskevin
121 posts since
Jul 23, 2007
Currently Being Moderated

Oct 13, 2008 12:43 PM

Use @resource.javascript in custom theme

Is there a way to use the @resource.javascript feature in a custom theme?  It appears that it attempts to load from the classpath and that doesn't work for /themes/<theme_name>/ paths.

Tags: themes, freemarker
karlcyr Jive Employee
karlcyr
9,390 posts since
Mar 12, 2008
Currently Being Moderated
Oct 14, 2008 4:29 PM in response to: whoiskevin
Re: Use @resource.javascript in custom theme

Hi,

 

I actually was able to achieve this with a very simple "Hello World" type test, so I did confirm that it will work. However, my test doesn't confirm that it will work for all usages. Can you describe how you are using the @resource.javascript tag?

 

Regards,

Karl

whoiskevin Novice
whoiskevin
121 posts since
Jul 23, 2007
Currently Being Moderated
Oct 15, 2008 4:23 AM in response to: Karl Cyr
Re: Use @resource.javascript in custom theme

Thanks for the response.

 

The use was in a theme using  2.5.2 version of clearspace.

 

Simple use.  It was in the themes directory in the template.ftl file.  path:  <theme_name>/template/decorator/default/template.ftl

 

The @resource call looked like this:

<@resource.javascript file="/template/scripts/showHide.js" header="true" />

 

Originally this ftl file and template directory was embedded in a plugin under the resources directory of the plugin.  It was moved to a standalone theme (recommended practice I believe).  At that point it would fail to load.  Perhaps the full path has to be coded when it is in the themes directory such that it would be (/themes/<theme_name>/template/scripts/showHide.js).

whoiskevin Novice
whoiskevin
121 posts since
Jul 23, 2007
Currently Being Moderated
Oct 15, 2008 4:56 AM in response to: whoiskevin
Re: Use @resource.javascript in custom theme

Tested it with the full theme path and it still errors out.

 

ERROR file.DefaultResourceLoader - An Exception occured loading resource /themes/<theme_name>/template/scripts/showHide.js

karlcyr Jive Employee
karlcyr
9,390 posts since
Mar 12, 2008
Currently Being Moderated
Oct 15, 2008 3:02 PM in response to: whoiskevin
Re: Use @resource.javascript in custom theme

Hi,

 

I am also having a problem loading a javascript file from the tag, though the script runs fine if I put the code directly in my FTL. Let me see if I can find out anything else about this problem.

 

Just to clarify, you said that this did work when you had it running as a plugin?

 

Regards,

Karl

whoiskevin Novice
whoiskevin
121 posts since
Jul 23, 2007
Currently Being Moderated
Oct 15, 2008 5:00 PM in response to: Karl Cyr
Re: Use @resource.javascript in custom theme

Well it worked in 2.0.4 when the theme directory was in the resources folder

of a plugin.  So yes.

 

 

From: Karl Cyr <communities@jivesoftware.com>

Reply-To: communities <communities@jivesoftware.com>

Date: Wed, 15 Oct 2008 15:02:22 -0700

To: Kevin Brown <kbrown@solutionset.com>

Subject: http://www.jivesoftware.com/jivespace/message/132324#132324/Developers New message: "Use @resource.javascript in custom theme"

http://www.jivesoftware.com/jivespace/message/132324#132324/1UUsLu-9aI-ypm

>

whoiskevin,

>

A new message was posted in the thread "Use @resource.javascript in custom

theme":

>

http://www.jivesoftware.com/community/message/132268#132268

>

Author  : Karl Cyr

Profile : http://www.jivesoftware.com/community/people/karlcyr

>

Message:

 

bcswissre Beginner
bcswissre
397 posts since
Jan 9, 2009
Currently Being Moderated
Jun 12, 2009 5:26 AM in response to: Karl Cyr
Re: Use @resource.javascript in custom theme

Hi Karl,

 

I'm now encountering the same issue in SBS 3.0.4.

 

Was there a resolution to this problem?

 

Thanks,

Ben.

More Like This

  • Retrieving data ...

Bookmarked By (1)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.