Dave, I'm sorry, I'm just getting back to this. I've removed all of the
external blogs from my planet config, refreshed everything and I'm still
seeing nothing. Any ideas? I'd prefer to not upgrade to 3.1 right now,
but if thats my only option I can pull it off. Thanks
Matt
Dave wrote:
On 5/7/07, John Haren <[EMAIL PROTECTED]> wrote:
I'm using roller3.1, deployed on tomcat 5.5.17, against MySQL 5.0.27-
standard db with a mysql-connector-java-3.1.13 connector.
I can add a single subscription to the planet aggregator, and all is
well. Triggering the refresh entries results in something like:
HibernatePlanetManagerImpl:refreshEntries - --- DONE --- Refreshed
entries in 0.435 seconds
Next, I add another subscription, refresh the entries, and get:
ERROR HibernateUserManagerImpl:getWeblogHandleLetterMap - Getting
weblog letter map
java.lang.ClassCastException: java.lang.Long
at
org.apache.roller.business.hibernate.HibernateUserManagerImpl.getWeblogH
andleLetterMap(HibernateUserManagerImpl.java:885)
at
org.apache.roller.ui.rendering.model.SiteModel.getWeblogHandleLetterMap(
SiteModel.java:259)
<snip>
This *only and always* happens with multiple subscriptions. I've run
through several test scenarios and have found that all the feeds I'm
subscribing to work fine, provided there is only one subscribed feed.
Actually, there is one exception to the above: when I place a feed in
a custom group, I get the same error, regardless of how may
subscriptions I've set up.
Any ideas?
Rats. We fixed that class-cast bug in a lot of places, but it looks
like we missed that one. However, I don't understand why adding feeds
to planet causes that bug to appear. The getWeblogHandleLetterMap
query doesn't involve any of the planet tables.
I reported this as a bug against 3.1.
http://opensource.atlassian.com/projects/roller/browse/ROL-1410
Unfortunately, there is not a good work around -- other than
completely avoiding use of the User Directory page in the front-page
theme.
I'm thinking we are going to need to get a Roller 3.1.1 release out
quickly to fix this, another XSS problem that was reported last week
and any other 3.1 small issues that come up in the next week or so.
- Dave
