Return to Jive Software

Up to Discussions in Support

This Question is Answered (go to answer)

1,827 Views 9 Replies Last post: Oct 9, 2008 10:55 AM by dpmccabe RSS
dpmccabe Novice
dpmccabe
86 posts since
Oct 1, 2008
Currently Being Moderated

Oct 1, 2008 12:43 PM

Editing "Recent Content" widget when "Customize" not available

I've just joined a project working with Jive Clearspace Community 1.10.7.  The last developer heavily customized a page using the FTL file and as a result we no longer can see the "Customize" link (logged in as an admin) which allows for the editing of widgets.

 

I have been asked to customize the "Recent Content" widget so that no Discussion posts appear.  I know this is as simple as changing a radio button when the ability to edit a widget is there, however I don't have this option.  Would there be a way to write logic in the FTL file which would discriminate any Discussion activity from appearing in the widget?

Tags: customization, widget, customize, clearspace_community, recent_content_widget
Diana Dukart Jive Employee
Diana Dukart
157 posts since
Aug 25, 2008
Currently Being Moderated
Oct 3, 2008 9:53 AM in response to: dpmccabe
Re: Editing "Recent Content" widget when "Customize" not available

That code doesn't actually happen in the FTL.  It might be easier to try and get the edit back.  Have you tried that yet?

 

Diana

Diana Dukart Jive Employee
Diana Dukart
157 posts since
Aug 25, 2008
Currently Being Moderated
Oct 3, 2008 10:57 AM in response to: dpmccabe
Re: Editing "Recent Content" widget when "Customize" not available

Hi,

 

So I was wrong before, I found a way you can do this in the FTL. 

 

In the recent-content.ftl there is a section commented " <!-- BEGIN recent community content -->"

 

Pretty close to the top of that section is the list iterator tag: <#list content as object>

 

Inside that list tag, wrap all the content with this if statement: <#if (object.getObjectType() != JiveConstants.THREAD)>

 

That will stop all the Discussion posts from appearing.

 

Hope this is what you need,

Diana

dpmccabe Novice
dpmccabe
86 posts since
Oct 1, 2008
Currently Being Moderated
Oct 3, 2008 12:10 PM in response to: Diana Dukart
Re: Editing "Recent Content" widget when "Customize" not available

Thanks for the tip!

 

That's great!

 

Now the only issue is that the majority of the activity on my community is forum posts.....which means now that I have excluded discussions from the feed nothing appears because of the recent content is discussion posts!

 

Any thoughts how to overcome this?

Diana Dukart Jive Employee
Diana Dukart
157 posts since
Aug 25, 2008
Currently Being Moderated
Oct 3, 2008 2:03 PM in response to: dpmccabe
Re: Editing "Recent Content" widget when "Customize" not available

You could increase the number of results, but you can't do that in the FTL.  Probably the best solution is to try and get the customize link back for the Widget, but if worse comes to worse, these settings are stored in the database.

 

Diana

dpmccabe Novice
dpmccabe
86 posts since
Oct 1, 2008
Currently Being Moderated
Oct 9, 2008 9:51 AM in response to: Diana Dukart
Re: Editing "Recent Content" widget when "Customize" not available

I would like to increase the number of results but haven't even explored the DB yet.  Where would I find this property in the DB?

Karl Cyr Jive Employee
Karl Cyr
6,819 posts since
Mar 12, 2008
Currently Being Moderated
Oct 9, 2008 10:26 AM in response to: dpmccabe
Re: Editing "Recent Content" widget when "Customize" not available

Hi,

 

I think what would work best for your scenario would be to make some changes to the Widget's properties in the database. If you had the "Customize" link on your widget, you would be able to set the radio button "Show Discussions" to "No" on the edit widget view. This radio button maps to the property showDiscussions in the database. If you look at the table jivewidgetfrmprop you can find this property and set it to "false". Just be careful to make sure that you are applying the change to the correct "Recent Content" widget, as there may be many stored in the database. To tell exactly where your widget is displayed, map the communityID to the space name for which you are trying to edit the widget.

 

Hope that helps!

 

Regards,

Karl

dpmccabe Novice
dpmccabe
86 posts since
Oct 1, 2008
Currently Being Moderated
Oct 9, 2008 10:47 AM in response to: Karl Cyr
Re: Editing "Recent Content" widget when "Customize" not available

Thanks Karl,

 

I was able to eliminate the discussions from the feed using the FTL:

 

<#assign counter=0>
<#list content as object>
   <#if (object.getObjectType() != JiveConstants.THREAD)>    <#--Conditional to remove discussions from feed-->
      <#if counter < 5><#--Conditional to set number of items in feed-->
         <#assign counter=counter+1>
         <#--create the table-->
      </#if>
   </#if>
</#list>

 

Would doing it in the database fix my problem of lots of discussion activity "pushing" any document/blog activity off the recent activity list? For example if 30 people post on a discussion in 2 days, I don't see the document that was posted 3 days ago.

 

Thanks,

 

Damian

Karl Cyr Jive Employee
Karl Cyr
6,819 posts since
Mar 12, 2008
Currently Being Moderated
Oct 9, 2008 10:52 AM in response to: dpmccabe
Re: Editing "Recent Content" widget when "Customize" not available

Hi Damian,

 

If you flip that switch in the database, you will be telling the RecentContentManager to stop adding discussion threads to its list. So once you've done that, your problem should go away, and there shouldn't be any need to suppress the discussions from being displayed at the UI level.

 

Regards,

Karl

dpmccabe Novice
dpmccabe
86 posts since
Oct 1, 2008
Currently Being Moderated
Oct 9, 2008 10:55 AM in response to: Karl Cyr
Re: Editing "Recent Content" widget when "Customize" not available

Thanks, I'll give that a try!

More Like This

  • Retrieving data ...

Bookmarked By (0)

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.