Help - Search - Members - Calendar
Full Version: Bug: Mtentries, Monthly Archives, And The Category Filter In 3.2.
Movable Type Community Forum > Other Product Discussion > Bugs and Odd Behavior
ragaskar
Using the following code in a monthly archive template that is designed to only show certain categories:

CODE
  
<MTEntries category="Bestsellers OR Promotions OR Recently Added">
                 ... display code here ...
</MTEntries>


This works *exactly* as expected until it reaches a month that does not contain any posts for the listed categories -- then it seems to display ALL posts (will have to do more checking to verify the ALL, but it is definitely displaying approved posts that are NOT in the MTEntries category filter).

IE, in my case, January does NOT have any Bestsellers OR Promotions OR Recently Added posts -- it *only* has Podcast posts -- and instead of appearing blank, as it should, it shows the Podcast posts.

This very much has the appearance of a zero-case that is not being properly handled.

Using 3.2. Thanks.

EDIT: Added a 'Bestsellers' post to January, and the Monthly view was correct again. After removing, got the erroneous view again.
Su-
Question:
Is there a reason you haven't updated?
It's all well and good to report this, but if confirmed, it's probably unlikely that it'll be fixed for 3.2.
3.3 has been out for some time now with several updates(not to mention new interface, etc), and there's already a new version in the works which will be a large departure from even that. Beyond security fixes, the code you're using should probably be considered essentially static
Checking on something that I think might be able to handle this case.
ragaskar
QUOTE (Su- @ Apr 10 2007, 03:23 PM) *
Question:
Is there a reason you haven't updated?
It's all well and good to report this, but if confirmed, it's probably unlikely that it'll be fixed for 3.2.
3.3 has been out for some time now with several updates(not to mention new interface, etc), and there's already a new version in the works which will be a large departure from even that. Beyond security fixes, the code you're using should probably be considered essentially static
Checking on something that I think might be able to handle this case.


I have brought up the likelihood of our install needing an upgrade within our group, however, this task is complicated a bit by the policies and configuration of our host. Upgrading for us would also mean a Perl upgrade, and an absolute bullet-proof upgrade path (we can't lose data). So, hopefully, upgrading is in our future (mostly because I'd prefer to use negation in our category filter as well), but yes, there is a reason why we haven't done it yet.

I did not see this as a known issue for 3.2, or as a bugfix for 3.3, so I assumed it may be still present (if it is indeed a bug).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.