Description
The regexes used for recognizing Category pages are not working since my upgrade to 1.6.0. You can see the problem by simply looking at CategoryHomepage. There are several pages there that shouldn't be. E.g., CodingStyle, which doesn't have a ----\nCategoryHomepage marker.
Steps to reproduce
Just look at the regex on CategoryHomepage:
Known homepages in this category: <<FullSearchCached(regex:(----(-*)(\r)?\n)(.*)CategoryHomepage\b)>>
Component selection
- query parser:
(20:25) < johill> <<FullSearchCached(regex:(----(-*)(\r)?\n)(.*)CategoryHomepage\b)>> (20:25) < johill> the query parser will see that as (20:26) < johill> regex:(----(-*)(\r)?\n) (.*) CategoryHomepage\n (20:26) < johill> and search for an OR between those three for some reason (20:27) < johill> there's supposed to be an implicit AND anyway
Details
This Wiki.
Workaround
None that I know of!
may you can use only <<FullSearchCached(linkto:CategoryHomepage)>> ... -- MarcelHäfner 2008-01-11 09:11:28
Or you could use <<FullSearch(category:CategoryHomepage)>> .
This is especially useful, if you patch PageEditor.py around line 833 and add a variable 'CAT': self.page_name . This allows you to add a line like this to your CategoryTemplate: <<FullSearch(category:@CAT@>> to list the pages in your category. -- ThomasWerschlein 2008-01-30
1.6.0 and 1.6.1 automatically added "Category". This is of course faulty, because we can also have translated Categories (e.g. KategorieFehler in german, using a modified category pagename regex). Therefore this magic was removed for 1.6.2, that means you have to give the full category name, e.g. category:CategoryHomepage or category:KategorieFehler.
Discussion
I spoke with ThomasWaldmann on IRC and he confirmed and suggested I file this bug.
This is a big problem that effectively breaks the category mechanism for every 1.6 installation.
Plan
- Priority: showstopper
- Assigned to:
Status: fix category pages to use <<FullSearch(category:CategoryFoo)>> and use 1.6.2+