Post Reply 
Sort value conflict for Date filter
17-04-2023, 20:19 (This post was last modified: 17-04-2023 21:55 by simbun.)
Post: #2
RE: Sort value conflict for Date filter
If I understand you correctly, for artists that have released multiple albums in the same year you've modified the Date tag to now include the month and day e.g. YYYY-MM-DD.

When using a tag for an index MinimServer needs to know the value that you want displayed, and where to place that value in the index.
With the setting <Date.yearOnly.index> you're truncating all the Date values to just YYYY for use in the index (that's what the index part of Date.yearOnly.index means), but that produces a mapping of (using the first couple of rows from your log file):

Code:
Index Value    Sort Order
1976           1976-06-01
1976           1976

Given MinimServer no longer has a way to establish exactly where that index value should appear within the list, it issues the warnings. To fix this you need to modify your tagOptions so that the sort value is also truncated:
Code:
Date.yearOnly.index.sort
This tells MinimServer to use the truncated Date for both the index and the sort order.

Hope that makes sense.


EDIT: Corrected from Date.yearmonth to Date.yearOnly
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Sort value conflict for Date filter - simbun - 17-04-2023 20:19

Forum Jump:


User(s) browsing this thread: 1 Guest(s)