[
https://issues.apache.org/jira/browse/ROL-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718107#action_12718107
]
Edd Grant commented on ROL-1793:
--------------------------------
Thought I should mention that, having changed absolutely nothing, this now
seems to be working. I'm thinking that this suggest that the problem may have
been with the feed that Twitter was putting out (perhaps it wasn't writing
dates correctly so Roller couldn't figure out how to exclude/ include certain
entries?).
It can be seen working here:
http://blog.mredd.co.uk/roller/planetrss?group=EddGrantTwitterFeed
So aside from my 3rd point (the ClassNotFoundException) this issue seems to be
resolved.
> Issues using PlanetModel in a weblog
> ------------------------------------
>
> Key: ROL-1793
> URL: https://issues.apache.org/jira/browse/ROL-1793
> Project: Roller
> Issue Type: Bug
> Components: Planet Aggregator
> Affects Versions: 4.0.1
> Environment: Roller 4.0.1 with MySQL 5, JDK 1.5 all on CentOS.
> Reporter: Edd Grant
> Assignee: Roller Unassigned
>
> Section 8.2.1 of the roller template guide states that the PlanetModel can be
> made accessible in weblogs, I have followed the instructions to do this and
> have added the following block to my roller-custom.properties
> # Set of models to be made available for weblog page rendering
> rendering.pageModels=\
> org.apache.roller.weblogger.ui.rendering.model.PageModel,\
> org.apache.roller.weblogger.ui.rendering.model.ConfigModel,\
> org.apache.roller.weblogger.ui.rendering.model.UtilitiesModel,\
> org.apache.roller.weblogger.ui.rendering.model.URLModel,\
> org.apache.roller.weblogger.ui.rendering.model.MessageModel,\
> org.apache.roller.weblogger.ui.rendering.model.CalendarModel,\
> org.apache.roller.weblogger.ui.rendering.model.PlanetModel,\
> org.apache.roller.weblogger.ui.rendering.model.MenuModel
> I have then setup a custom subscription group called "Twitter" in planet
> admin and have initially pointed this at my twitter Atom feed.
> I have then created a new 'Twitter' template (snippit below) which I am
> calling from weblog, this attempts to access the "Twitter" aggregation pager
> to display available entries from my twitter feed:
> #set($maxResults = 25)
> #set($since = 365)
> ## Get the aggregation pager object for the twitter subscription group.
> #set($twitterpager = $planet.getAggregationPager("Twitter", $since,
> $maxResults))
> <br />Number of tweets: $twitterpager.items.size()
> <div style="width:350px;border:1px solid red;">
> #if($twitterpager.items.size() > 0)
> <a href="$twitterpager.items.get(0).website.URL"/>My Twitter feed</a>
> $config.feedMaxSize
> #end
> #if($twitterpager.items.size() > 0)
> #foreach($entry in $twitterpager.items)
> <div class="entry">
> <a class="entryTitle"
> href="$utils.escapeHTML($entry.permalink)">
> ## Insert a link to the entry and display the entry's
> published time.
> #if($entry.pubTime)
> <a
> href="$entry.permalink">$utils.formatDate($entry.pubTime,
> $text.get("macro.weblog.date.toStringFormat"))</a>
> #end
> </a>
> <p class="entryDetails">
> These are the entry details.
> </p>
> <p class="entryDescription">
> #if($entry.displayContent)
>
> $utils.truncateNicely($utils.removeHTML($entry.displayContent), 240, 260,
> "...")
> #else ## planet entries don't have displayContent
>
> $utils.truncateNicely($utils.removeHTML($entry.text), 240, 260, "...")
> #end
> </p>
> </div>
> #end
> #end
> </div>
> I have the following problems:
> 1: http://blog.mredd.co.uk/roller/planetrss?group=Twitter only ever shows the
> latest entry from my twitter feed - I'm expecting it to show all available
> entries, is this a bad assumptiong?
> 2: My 'Twitter' template also only ever shows the latest entry from my
> twitter feed.
> 3: An aside really but I get a really nasty ClassNotFoundException when I put
> the PlanetModel last in the list of rendering.feedModels in
> roller-custom.properties, thought I'd mention in case it was related.
> I'm using Roller 4.0.1 with MySQL 5, JDK 1.5 all on CentOS.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
