roller-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Schmidt" <>
Subject RE: Optionally indexing comments
Date Wed, 14 Dec 2005 15:38:54 GMT
Here's the adjustment to IndexOperation.  It's listed as a class called
DZIndexOperation.  Lines 62-67 are new as are 97-119.  There's also a new
property in listed as search.index.comments=true.  It goes
just under the search.index.dir property.  


-----Original Message-----
From: Anil Gangolli [] 
Sent: Wednesday, December 14, 2005 10:24 AM
Subject: Re: Optionally indexing comments

These both sound good to me.


I also volunteer to do the integration work if you send me the patches.


Matthew Schmidt wrote:

>Hi guys.  During my work to migrate cleanly to Roller 2.x, I've come across
>an interesting problem.  I'm currently trying to use the custom directory
>prevent myself from changing core files.  The problem is that I need to
>change IndexOperation to not index comments (causes indexing to slag the
>machine when rebuilding the index).  Would it be possible to have another
>roller property for optionally indexing comments?  It seems like a trivial
>change and helps performance for large sites.  It would also keep me from
>having to change a core class :)  
>Another proposal I have is to add in user-agent checking to RefererFilter.
>We do this at JROller to exclude google and other spiders from the dayhits
>(when google hits you 80k times a day, its definitely needed). I have a
>small patch for this if you guys would like to add it to the core.
>Alternatively, is there a way I can override RefererFilter with my own
>version without causing duplicate class errors?  Perhaps a way to remove it
>from the generated filter list and replace it with my own?  All without
>tweaking the core code? :)
>-----Original Message-----
>From: Anil Gangolli [] 
>Sent: Tuesday, December 06, 2005 11:08 AM
>Subject: localization guide and question
>I'm adding a localization guide to the wiki.
>In documenting current Roller i18n support, it appears that we use the 
>server JVM's default locale rather than the user browser's locale for 
>selection of the resources in all of the JSP-based views.  Is this 
>intended?  Is it a regression? or have I got it wrong?

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message