It appears that date_constructor->set_value() in feedapi_mapper_date.inc doesn't know know what to do with timestamps. As a result unix style timestamps are always resolved as the current time.

CommentFileSizeAuthor
#2 feedapi_mapper-515166.patch1.04 KBhalstead
#1 feedapi_mapper-515166.patch1.07 KBhalstead

Comments

halstead’s picture

halstead commented
Status: Active » Needs review
StatusFileSize
new feedapi_mapper-515166.patch1.07 KB

It seems that letting the function know about the start_stamp and end_stamp keys fixes the problem.

halstead’s picture

halstead commented
Assigned: Unassigned » halstead
StatusFileSize
new feedapi_mapper-515166.patch1.04 KB

This still seems to be an issue. A fresh patch against HEAD is attached.

halstead’s picture

halstead commented
Status: Needs review » Fixed

This appears to be committed into 6.x-1.3.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.