Difference between revisions of "Issue:Use of multiple dates"
(New page: {{Issue |Type = Bug |Extension = DPL |Version = 1.8.9 |Description = Use of multiple dates in ordermethod |Status = open }} == Problem == I have a dpl query as fol...) |
(→Problem) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 27: | Line 27: | ||
the expected behavior because i have the addeditdate parameter would be that %DATE% is the edit date, this is true. however the sorting is only sorting on the last value from ordermethod and not obeying the firstedit. | the expected behavior because i have the addeditdate parameter would be that %DATE% is the edit date, this is true. however the sorting is only sorting on the last value from ordermethod and not obeying the firstedit. | ||
| + | |||
| + | i have found if i remove lastedit from the ordermethod then %DATE% is the firstedit date which is not the expected outcome. so inorder to display the edit date i must have the lastedit value in the ordermethod, but this breaks everything. | ||
| + | |||
| + | i given that it wouldnt make sense to add %DATE1%, %DATE2%, etc... it could stand that the order of the dates replaced could be tied to the ordermethod parameter so i could change my query to include both. although i would prefer to just use the ordermethod and variable separately. | ||
== Reply == | == Reply == | ||
Latest revision as of 23:48, 23 February 2010
| Description: | Use of multiple dates in ordermethod |
| Extension / Version: | DPL / 1.8.9 |
| Type / Status: | Bug / open |
Problem
I have a dpl query as follows.
<dpl> debug=1 category=Scrum ordermethod=firstedit,lastedit addeditdate=true userdateformat=Y-m-d listseparators={{{!}} class="wikitable sortable" cellpadding="2" border="1" width="100%" \n {{!}}- bgcolor="#ffcc33" \n {{!}} Iteration\n {{!}} Updated\n ,\n{{!}}-\n{{!}}[[%PAGE%{{!}}{{SUBPAGENAME:%PAGE%}}]],\n{{!}}%DATE%\n,\n{{!}}} nottitlematch=%Template% include= titlematch={{BASEPAGENAME}}/% includetrim=true stablepages=only </dpl>
the expected behavior because i have the addeditdate parameter would be that %DATE% is the edit date, this is true. however the sorting is only sorting on the last value from ordermethod and not obeying the firstedit.
i have found if i remove lastedit from the ordermethod then %DATE% is the firstedit date which is not the expected outcome. so inorder to display the edit date i must have the lastedit value in the ordermethod, but this breaks everything.
i given that it wouldnt make sense to add %DATE1%, %DATE2%, etc... it could stand that the order of the dates replaced could be tied to the ordermethod parameter so i could change my query to include both. although i would prefer to just use the ordermethod and variable separately.
