Sort news by inverted date in the taxonews block (last news on top) ?
yagraph - July 20, 2009 - 10:39
| Project: | Taxonews |
| Version: | 6.x-1.0 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi, and thanks for your great module !
I'm using your module for a client's website, and I need a little detail with taxonews...
Did I miss something, or it's impossible to sort news inverted in the block (last news on the top) ?
It work well in the "Archive" page (last new is on top, as I wish), but not in the block...
To illustrate what I want to say, please see the attached screen-shot, and visit this page : http://www.aquter.fr/aquter/category/actualites/actualites
I've checked the php file, but I don't know php very well... So I don't know if this issue is a bug report or a feature request.
Here is the Taxonews Id for the module I use : $Id: taxonews.module,v 1.10.8.10 2008/10/13 09:09:10 fgm Exp $.
| Attachment | Size |
|---|---|
| Capture-1.png | 327.14 KB |
#1
Hi,
Ordering is dependent on several factors:
I suspect you have enabled both statistics.module and one of the ponderation factors in taxonews settings. Try making sure you have validated "Ponderate sorting by" as "Creation date", and not one of the other choices, and confirm.
#2
Thanks for your attention,
I did checked that, statitics.module was disabled, and it was sorted by Creation date....
I've tried others options with no more success.
But deleting the node and re-creating it, it now work !
On the other hand it appeared that the client antedate one node to re-order it... And it seam that has troubled taxonews.
So my issue is fixed (thank you !), but you may check taxonews comportment with antedating... I let it to your appreciation.
Thanks again !
#3
Thanks for the details. Since you appear to have identified an antedating problem, could you list the steps to reproduce it, so I can see how to fix it, or whether this was actually intended behaviour ? You seem to imply that the person doing the node creation had modified the "later" node date to an earlier date relative to the other node. If so, was it in a revision, or on the original node ?
#4
I double-checked the code: ordering is performed based on "node.created DESC, node.changed DESC", which seems to preclude the type of behaviour you describe IF admins don't use their powers to mess with creation dates.
Makes for a nice additional feature: order on changed date instead of creation date. Creating issue for this.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.