This Question is Answered

1 "correct" answer available (4 pts) 1 "helpful" answer available (2 pts)
12 Replies Last post: Feb 21, 2008 9:01 AM by r10  
r10 Novice 182 posts since
Aug 1, 2001
Currently Being Moderated

Dec 11, 2007 10:13 AM

Community tab plugin problem

Hey guys,

 

I've got a problem where a plugin that worked in 1.7 doesn't in 1.9.  I've tracked the problem down to the plugin XML (I think).  The following XML creates the tab correctly but builds a url of the form /clearspacex/communityexample and not /clearspace/community/communityName?view=example as it should.  The plugin XML for the tab is: 

 

 
<tab id="community-tab" name="Example Community Tab"
description="Example of a new community tab." cssClass="jive-link-community">
<url>example</url>
</tab>

 

Has something changed between versions with the way plugins are inserted into the community tab structure?

 

Thanks!

Jay

Aaron Johnson JiveEmployees 1,164 posts since
Jan 7, 2004
Currently Being Moderated
Dec 11, 2007 2:38 PM in response to: r10
Re: Community tab plugin problem

hi Jay,

 

I think the XML should look something like this:

<components>
  <component id="community-tabs">
    <tab id="example" name="Example Community Tab"
      description="Example of a new community tab." cssClass="jive-link-community">
      <url>example</url>
    </tab>
  </component>
<components>

 

Let me know if that works.

 

Cheers,

 

AJ

Jason Burkhardt Novice 31 posts since
Nov 5, 2007
Currently Being Moderated
Dec 17, 2007 8:16 AM in response to: r10
Re: Community tab plugin problem

 

I had to make the following change in plugin.xml for my community-tabs component to work in 1.9 (coming from 1.7):

 

 




&lt;url&gt;
&lt;![CDATA&gt;&lt;/url&gt;


 

 

Where &lt;action name&gt; is the action defined in xwork..

 

 

Not sure if it's the same thing you're running into but it may be worth a shot

 

 

Jason Burkhardt Novice 31 posts since
Nov 5, 2007
Currently Being Moderated
Dec 17, 2007 8:26 AM in response to: Jason Burkhardt
Re: Community tab plugin problem

Argh sorry, it sucks trying to post this without it getting edited..  anyway here's what I had to change my community-tabs plugin.xml to:

 

Aaron Johnson JiveEmployees 1,164 posts since
Jan 7, 2004
Currently Being Moderated
Dec 18, 2007 12:02 AM in response to: r10
Re: Community tab plugin problem

hi Jay,

 

The example plugin should have a working plugin.xml, let me know if that helps (or not).

 

Cheers,

 

AJ

Aaron Johnson JiveEmployees 1,164 posts since
Jan 7, 2004
Currently Being Moderated
Dec 24, 2007 11:14 AM in response to: r10
Re: Community tab plugin problem

hi Jay,

 

Sorry for the run-around: yes it looks like the way that links are rendered in community tabs are different in 1.9. You can see the logic for the rendering in /template/global/include/community-header.ftl.  In short, it looks like we used to automatically add the name of the tab to the current URL along with a 'view=' prefix. Now we require the full URL to your action. I'm looking at the source code for 1.10 right now and the code inside the CDATA section of the example plugin plugin.xml looks like this for the community tabs part:

 

<@ww.url value="/example-community.jspa?communityID=${community.ID?c}" />

 

Does that work for you?

 

Cheers,

 

AJ

Aaron Johnson JiveEmployees 1,164 posts since
Jan 7, 2004
Currently Being Moderated
Jan 22, 2008 11:08 PM in response to: r10
Re: Community tab plugin problem

hey Jay,

 

k, I've got the example plugin that you posted installed on 1.10. I bring up 1.10 and I see the example community tab show up in the community. It points to the appropriate place, on my machine it points to:

 

http://localhost:8080/clearspace/example-community.jspa?communityID=2000

 

When I click on that link, I'm taken to a page that shows an error:

#  Status Code: 500
# Exception Type:
# Error Message: Unexpected end of file reached.
# Request URI: /clearspace/example-community.jspa

 

Is that what you see as well?

 

If I look at the file example-community.ftl, there's freemarker tag that looks a little wonky:

</
@ww.action>

 

That might be the problem.

 

Cheers,

 

AJ

More Like This

  • Retrieving data ...
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.