There are still some pages that are broken in Tomcat 7, I haven't got
around to fixing them, but I think I've fixed the most pertinent ones. The
main problem is that Tomcat 7 disallows accessing the class as a property
on an object (eg, myobject.class) because it says that class is a reserved
keyword, where Tomcat 6 was totally fine with this. Things associated with
managing/viewing plugins I think still heavily use this. I'm still using
Tomcat 6 myself.
However, I don't think an upgrade will help, there is nothing changed
between Pebble 2.5 and 2.6 that should have any impact on tags.
The tag index and lucene are two separate things. Don't ask me why, I'm
guessing it's all based on the history of how pebble was developed, and I'm
only relatively new on the scene. Let me explain:
* The tags page and tag cloud use their own index, in the tag.index file.
This is a flat file, and has nothing to do with lucene. You can open this
file in a text editor, it is in format tag name followed by an equals sign
followed by a comma separated list of blog post ids. You can then check
those blog posts manually, to make sure that the actually don't have those
tags.
* When you click on a tag, to view the blog posts associated with it, this
uses the lucene index to find the blog entries.
Now, clicking around your blog, it seems that only the tags that are just
numbers don't return entries, is that right? Sounds to me like it's a bug
with tags that are just numbers. Could you check your tag.index, find the
blog post ids and then the associated blog posts (the id is a timestamp in
ms since epoch, so you can convert it to a date and find the blog post that
way), and see if those blog posts do actually have those tags? I suspect
they will, and either tags that are numbers aren't being indexed properly,
or something about the query parsing when tags are numbers is broken.
Cheers,
James
On 11 December 2012 23:05, Alan Burlison <[email protected]> wrote:
> On 11/12/2012 11:22, pieroxy wrote:
>
> > I would suggest :
> >
> > 1. shutting down your webserver
> > 2. removing the tags.index file in the indexes directory of your blog
> > 3. restart your app server and reindex
> >
> > Of course, do not delete the file, just move it somewhere, just in case.
>
> Tried that, didn't work. I've looked at the tags section in the blog
> post XML files and I cant find the problematic tags in there so I'm
> guessing that Lucene has got its indexes in a twist. Where does it keep
> them and is it safe just to manually delete them?
>
> > If that doens't work I would suggest migrating to the latest version
> > (2.6.4).
>
> Yeah, that's on my todo list, I'll do that later today. What's the
> current recommendation for a Tomcat version for use with Pebble? The
> website says Tomcat6 but I see there are comments in the changelog about
> Tomcat7 support.
>
> > If all of this doesn't work, please report back and I'll try to
> investigate
> > tonight at home.
>
> I'll let you know how I get on, thanks.
>
> --
> Alan Burlison
> --
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Pebble-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pebble-user
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Pebble-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pebble-user
