Welcome to the Invelos forums. Please read the forum rules before posting.

Read access to our public forums is open to everyone. To post messages, a free registration is required.

If you have an Invelos account, sign in to post.

Invelos Forums->Posts by MikeDStoke Page: 1  Previous   Next
Message Details
Regional settings are correct and the only date that is complained about is the purchased date. I even tried updating the purchase date on an entry and after entering a valid date it then complained about the very same date when requesting an update of the profile. The date format in use is a UK based date ie dd/mm/yyyy. When the date is displayed as in error it shows '2017-09-26' is not a valid date, I assume given that the year is displayed first that the format it is showing is yyyy-mm-dd and last time I checked 26th September 2017 was a valid date and it is still displayed correctly and shows correct calendar information when entering the date in the personalise settings. I even tried setting the date to the release date which was 8th August 2017 and the message displayed that '2017-08-08' is not a valid date.

The only way I have found around this is to completely blank out the purchase date - but given that I have about 3000 discs this would take some time and would lose some valuable information.
Posted:
Topic Replies: 2, Topic Views: 577
I reported this error when version 4 was in Beta and it is still unresolved. When trying to refresh a dvd profile/images it fails with an error dialogue suggesting a database rebuild - then subsequently it displays a second dialogue saying (for example) 'Wed 18 10 2017' is not a valid date - the date concerned is the purchase date and is valid for a UK formatted date and if I try to update the purchase date it still remains in this format.

This applies if refreshing a single DVD or when doing a scan for entire collection - when doing this over the entire collection it means for every DVD I have to go through two error dialogues and still do not get updated profiles.

I have also tried a database rebuild and a total reload of the product and the error remains.
Posted:
Topic Replies: 2, Topic Views: 577
Invelos Forums->Posts by MikeDStoke Page: 1  Previous   Next