d00zah 128 Posted February 13, 2019 Share Posted February 13, 2019 (edited) I was checking to see if the weird date added issue in mixed content libraries had been addressed in the new release (no), & noticed something new. This applies to all libraries I've looked at, so far. Date added/released fields are blank in the editor even tho date added displays on the detail screen & both appear correctly in .nfos. You can add a new date & it'll stick, but never displays in the editor fields. - Verified 'Date added behavior for new content:' is still set. - Ran full library scan. Problem persists. Edited February 13, 2019 by d00zah Link to comment Share on other sites More sharing options...
d00zah 128 Posted February 13, 2019 Author Share Posted February 13, 2019 Just me, then? Reverting to v4.0.1.0, said dates reappear. Link to comment Share on other sites More sharing options...
Happy2Play 8282 Posted February 13, 2019 Share Posted February 13, 2019 I am not seeing this behavior on my Windows 4.0.2.0. Link to comment Share on other sites More sharing options...
d00zah 128 Posted February 13, 2019 Author Share Posted February 13, 2019 I am not seeing this behavior on my Windows 4.0.2.0. Well, that's strange. This is a brand new db as of v4.0.1.0. 1st update ever. And it's consistent throughout. Any thoughts? <dateadded>2018-10-24 00:00:00</dateadded> <title>Bohemian Rhapsody</title> <originaltitle>Bohemian Rhapsody</originaltitle> <director>Bryan Singer</director> ... <rating>8.3</rating> <year>2018</year> <mpaa>PG-13</mpaa> <imdbid>tt1727824</imdbid> <tmdbid>424694</tmdbid> <premiered>2018-10-24</premiered> <releasedate>2018-10-24</releasedate> Link to comment Share on other sites More sharing options...
Happy2Play 8282 Posted February 13, 2019 Share Posted February 13, 2019 Was there anything in the 4.0.2.0 log? Link to comment Share on other sites More sharing options...
d00zah 128 Posted February 13, 2019 Author Share Posted February 13, 2019 Was there anything in the 4.0.2.0 log? Nothing of note. After reverting to v4.0.1.0, I re-ran the update & now everything looks OK. WTF!!!!??? Thanks for your time. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now