'Whats new' asset relative date range double-up

(Nathan Booth) #1

Hi there

 

I've set up a website and intranet newsletter with 'latest news' (Whats new asset), 'latest documents' (Whats new asset) and 'upcoming events' (asset listing).

 

Latest news and latest documents have been set-up with a relative date field for previous 2 weeks:

 

DETAILS screen

Date range settings

Date field: Last published date

Range type: Specified range

date range from: period relative to current date and time > 14 days in the past

Date range to: period relative to current date and time > 0 days in the past

 

Asset selection/locations ok.

 

List formatting

List format: standard

assets per page: 0

 

DATE RANGE screen

Title: date

Range type: Specified range

date range from: period relative to current date and time > 14 days in the past

Date range to: period relative to current date and time > 0 days in the past

 

------

 

When I go to preview the newsletter, it randomly orders items and they go back to first published content (20 January 2013) for the website, and lists nothing at all in the intranet newsletter.

 

Any thoughts?

 

 

 

 

 

(Bart Banda) #2

What sort order have you got specified on the asset sorting screen of the what's new asset? Make sure that they are ordered by published date in there as well, not sure if that is the issue though or if it will make any difference. 

 

I normally never use a what's new asset for this type of listing, just use an asset listing and set it to list a maximum number of assets as you might have 2 weeks of almost no new published content, and the next 2 weeks of heaps of published content, the length of the listing would become very inconsistent. But all depends on your requirements of course.

 

Another thing to check is the date on the server, make sure it's set to the current date (unlikely cause). 

 

Also, are you saying that your first whats new listing works but not the second one?

(Nathan Booth) #3

Hi Bart

 

I initially selected 'publish date' (system) as asset sort (descending), not specific metadata field that is manually applied when content is first published (which works for full history in asset listings such as media releases, etc).

 

A workaround that seems to have solved the issue is using 'creation date' (which is fine as long as the asset is published on the same day).

 

Neither what's new listing worked based on system publish date (the server date was ok too).

 

Cheers

Nathan

(Bart Banda) #4

Hmm, that does sound buggy, what version are you on? Maybe it has been fixed in recent versions? If not, it might have to get reported as a bug for Squiz Labs to investigate.

 

Good that there is a workaround. If you are worried about assets being created on one day and then published on another, you could even go a step further and set up a trigger that changes the asset's Created Date when the Asset's status is set to Live.