On 7/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I also saw this problem in Roller 3.1. The blacklist update works in
Server Admin:Configuration for someone with the global admin privilege.
The blacklist update fails in Preferences:Settings for someone has either
global admin or weblog admin privilege. When it fails, the java exception
points to HibernateRefererManagerImpl.applyRefererFilters() method.
Allow me to be more specific. The Server Admin:Configuration calls
RollerPropertiesAction.update(). It comments out the call to
HibernateRefererManagerImpl.applyRefererFilters(). I quote the code below
for your reference.
// this operation causes OutOfMemory exceptions on sites with
// lots of referers so i am disabling it until it's
// not as dangerous -- Allen G
//mRoller.getRefererManager().applyRefererFilters();
The Preferences:Settings calls WebsiteFormAction.update(). It fails at the
call to HibernateRefererManagerImpl.applyRefererFilters(). I comment out
the call and the blacklist update appears to work.
Questions:
1. Is it a known behavior in Roller 3.1?
2. Is it fixed in Roller 4.0?
3. Should we comment out the call to
HibernateRefererManagerImpl.applyRefererFilters() from
Preferences:Settings to make it work? Will it break Roller 3.1 referrer
feature?
4. Is there a better work-around?
That call should remain commented out until somebody comes up with an
efficient way to clear the old referrers list based on the new
blacklist changes.
Even with that call commented out the blacklist changes will still go
into effect and will be used against all new incoming
comments/referrers.
- Dave
