2012-04-02, 21:28
(2012-04-02, 17:11)Memphiz Wrote: cut 10 times and its still to short ...
Cutting things will always make things shorter... not longer
(2012-04-02, 17:11)Memphiz Wrote: cut 10 times and its still to short ...
(2012-04-04, 17:13)fatal. Wrote: Hey,
Will this new <dateadded> value be imported from local nfo files? If so, what is the tag in the nfo (assuming <dateadded>) and format of the date that would need to be populated for the tag?
Take Care
YYYY-MM-DD HH:MM:SS
(2012-04-12, 13:07)Montellese Wrote:(2012-04-04, 17:13)fatal. Wrote: Hey,
Will this new <dateadded> value be imported from local nfo files? If so, what is the tag in the nfo (assuming <dateadded>) and format of the date that would need to be populated for the tag?
Take Care
Yes <dateadded> is being read from NFOs. The correct format isCode:YYYY-MM-DD HH:MM:SS
<dateadded>2012-04-12 14:20:50</dateadded>
<dateadded>2012-04-12T14:20:50</dateadded>
(2012-04-12, 20:26)fatal. Wrote: Thank you very much, will look forward to this as it will improve the WAF as the dateadded will remain constant in the info even if the filename/location changes and is re-imported into XBMC!
So this field going to be in 24-hour format (as shown below) would get imported correctly into XBMC:
Code:<dateadded>2012-04-12 14:20:50</dateadded>
and doesn't require it to be in xsd:datetime format
Code:<dateadded>2012-04-12T14:20:50</dateadded>
Take Care
<createdate>20101218182418</createdate>
(2012-04-12, 21:17)rev105 Wrote: I use media companion and I only see
Code:<createdate>20101218182418</createdate>
I do not see dateadded in my NFO's