Page 1 of 1

Bugs In News Module Found

Posted: Tue Feb 26, 2008 4:53 pm
by applejack
I have come across a number of bugs in the News module v2.6.1.

sortby="news_category" option does not work. Whether or not this is because of using the browsecat function I don't know but surely the point of sortby="news_category" is to use it for that very purpose.

Also if I have e.g.

Latest News
{news browsecat="1" browsecattemplate="browsecat.tpl" sortby="news_category" detailpage="articles" detailtemplate="detailed.tpl" summarytemplate="summary.tpl"}

Archive News
{news browsecat="1" browsecattemplate="browsecat.tpl" showarchive="1" sortby="news_category" detailpage="articles" detailtemplate="detailed.tpl" summarytemplate="summary.tpl"}

In the archive news listing if there is only one article in a category and even though the article has not expired the category link becomes active but of course if one clicks on it then the summary page is empty.

The counter function to show the number of articles does not understand if an article is expired or not i.e. both latest news and archived news shows the same count number next to each category.

All templates are the standard ones.

Re: Bugs In News Module Found

Posted: Tue Feb 26, 2008 4:57 pm
by calguy1000
The docs don't say it, but the sortby parameter does not work in browsecat mode.

Re: Bugs In News Module Found

Posted: Tue Feb 26, 2008 5:17 pm
by applejack
Hi Calguy

OK re the sort any plans to include this as part of the browsecat function? What about the counter and the show archive issue as I don't think my client is going to be too happy about this?

Re: Bugs In News Module Found

Posted: Mon Apr 07, 2008 5:48 pm
by Nullig
You can edit the action.browsecat.php file to change:

Code: Select all

$query .= ' ORDER by hierarchy';
to:

Code: Select all

$query .= ' ORDER by long_name';
Nullig