[Fixed in 7.1] Movie Dates all 01/01/9999 ?

[michae1a1ee]

Thank you for working on new code to correct this! Much appreciated. I will NOT attempt an uninstall/reinstall.
I don't want to keep you from your work, but I wanted to make an observation and ask a couple things...

The observation I've made with your latest input is that in my example, the ReleaseDate and the ReleaseDateDisplay are in different formats, yours are the SAME as each other. I believe what I'm seeing on my side is that the ReleaseDateDisplay is stuck in the original Short Date format I had set on the PC forever (since MM was installed), while the ReleaseDate format appears to change with Windows Regional Format changes given that it's Month-first (although mysteriously not using the currently-set slashes in Windows Regional Format for the XML file; while Collection Management IS displaying the Disc Release date with slashes in MM/DD/YYYY format matching the Windows Regional Format). This CM display format is 100% being taken from the individual PC as I can get Collection Management to display the date differently on two different PCs at the same time pointing at the same MM database. Just to document this, here is the same movie record being clipped from Collection Management on two different PCs with their corresponding & different Regional Format settings:

MM API Key Server:

image.png (5.63 KiB) Viewed 264 times

image.png (35.38 KiB) Viewed 264 times

CCC Desktop PC:

image.png (4.66 KiB) Viewed 264 times

image.png (28.04 KiB) Viewed 264 times

You've commented on not knowing why there are both of these Date fields in the XML file, I'm just adding that your set of two fields seem to be in sync with each other, mine are not. The strange thing to me is that ReleaseDate data in the XML file more closely matches what I'm seeing in Collection Management, not the "ReleaseDateDisplay" format which one would expect would relate to how the date will be displayed/shown, etc.

The question I wanted to ask is what you want me to do with my Regional Format settings... should I put them all back to how they were at the start of this troubleshooting? I've gathered from what you've said prior that my CCC Desktop PC can be whatever I want, so during my testing I've put it back to the original settings as you saw from my screenshots above. My understanding from what you've said is that the only PC that matters for the XML data and CMC's Disc Release date display is the PC that CCC points to, which is running My Movies and providing the API Key. So on the MM API Key machine, do you want me to set the Regional Format section back to the original Canadian settings I had with a Short Date of YYYY-MM-DD, or does it need to stay as shown above with the English (United States) options and MM/DD/YYYY Short Date?

Thank you again for your time and commitment to working on and fixing this issue. I hope my input is helpful in you improving the application overall.

[Pauven]

Since the region changes we both attempted had zero impact on the MM API data, my recommendation is to set them to whatever you prefer. CCC and CMC currently do not utilize these Windows settings, so it doesn't affect my software.

I've long believed that MM Collection Management also uses the API to retrieve data, an assumption of mine based upon a few factors. Primarily, it makes the code maintenance easier if you only have to maintain 1 function to retrieve data, not 2. And secondly, some of the slowness I see via the API is also evident in the GUI, as if the GUI is reaching through the API to retrieve data. I'm not foolish enough to think the GUI solely utilizes the API, after all there are many tasks that are impossible via the GUI with are performed in CM. It also might be that the GUI talks directly to a background service that handles both the API and the GUI requests, so that the functions are shared at a deeper level without the GUI talking to the API directly.

But the date display in the GUI has me second guessing myself. Obviously the API isn't following the Windows Region settings while the GUI is. That might suggest a different data pathway altogether, or simply a bug/limitation in the API logic.

[Pauven]

Hey, do me a favor and open this URL on your My Movies PC:

http://localhost:51415/?command=GetTitleList&SortBy=ID&FieldList=%22ID,LocalTitle,%22&APIKey=12345

You'll need to change the 12345 to be your API key. Then post me 1 or 2 lines from it, like this:

<Title id="1" recordChanged="5/28/2021 2:39:42 PM" personalDataChanged="8/3/2023 12:32:50 AM" worksAsTVSeries="false" localTitle="Eulogy"/>
<Title id="2" recordChanged="8/8/2017 6:31:42 PM" personalDataChanged="8/3/2023 12:35:47 AM" worksAsTVSeries="false" localTitle="Like Dandelion Dust"/>

What I'm interested in is the date format. I'm worried that the API is also using dashes here on your setup. CCC uses these dates to identify when changes have occurred, and I need to make sure this works consistently.

Also, word of warning: The My Movies General Service crashed on me this morning (service entered STOPPED state in Windows Services). I haven't experienced this issue in a very long time, well over a year. Seems suspicious that it happened today, after I changed the Windows Region Short Date format and did a fresh boot. Might be a coincidence, but also might be that I caused some type of mismatch that is generating errors in the service, ultimately causing it to crash. For this reason, probably best to set it back to what you had originally.

EDIT: You can probably disregard that warning. I found the error in the logs, and it's happened a few times in recent weeks, and appears to be related to folder monitoring.

[michae1a1ee]

Here are the first several lines from that URL output, directly from the browser on my MM Server with API Key:

<Response status="ok">
<Titles>
<Title id="604" recordChanged="12/30/2020 7:25:26 PM" personalDataChanged="12/24/2021 3:52:27 AM" worksAsTVSeries="false" localTitle="10,000 BC"/>
<Title id="607" recordChanged="3/12/2019 1:07:23 PM" personalDataChanged="12/24/2021 3:52:28 AM" worksAsTVSeries="false" localTitle="17 Again"/>
<Title id="609" recordChanged="12/14/2023 7:11:18 PM" personalDataChanged="12/24/2021 3:54:14 AM" worksAsTVSeries="false" localTitle="2 Fast 2 Furious"/>
<Title id="610" recordChanged="4/10/2017 1:30:22 PM" personalDataChanged="12/24/2021 3:52:29 AM" worksAsTVSeries="false" localTitle="2012"/>
<Title id="611" recordChanged="3/3/2020 6:59:58 PM" personalDataChanged="12/24/2021 3:52:29 AM" worksAsTVSeries="false" localTitle="21"/>

I have not yet changed the Regional Format on that PC yet - it's still set to US with Short Date MM/DD/YYYY.
You're saying now that really doesn't matter, but I wanted to provide full disclosure as those dates above are clearly showing MM/DD/YYYY too.

[michae1a1ee]

I now changed the MM Server/API Key machine back to English Canada with 2024-04-28 showing as the Short Date.

Refreshed that URL you had me load and I don't see any difference:
<Response status="ok">
<Titles>
<Title id="604" recordChanged="12/30/2020 7:25:26 PM" personalDataChanged="12/24/2021 3:52:27 AM" worksAsTVSeries="false" localTitle="10,000 BC"/>
<Title id="607" recordChanged="3/12/2019 1:07:23 PM" personalDataChanged="12/24/2021 3:52:28 AM" worksAsTVSeries="false" localTitle="17 Again"/>
<Title id="609" recordChanged="12/14/2023 7:11:18 PM" personalDataChanged="12/24/2021 3:54:14 AM" worksAsTVSeries="false" localTitle="2 Fast 2 Furious"/>
<Title id="610" recordChanged="4/10/2017 1:30:22 PM" personalDataChanged="12/24/2021 3:52:29 AM" worksAsTVSeries="false" localTitle="2012"/>
<Title id="611" recordChanged="3/3/2020 6:59:58 PM" personalDataChanged="12/24/2021 3:52:29 AM" worksAsTVSeries="false" localTitle="21"/>

So it would seem you're correct that there is no bearing on your software.

[Pauven]

Thanks for doing that test. I didn't see any change on my end either, even with it set to YYYY-MM-DD, the API still output MM/DD/YYYY.

The good news is that I won't have to make any code changes to handle this area, since for once My Movies is being consistent. I had been wondering why you didn't complain about changes not being picked up (that's what these dates control), but since the dates were in MM/DD/YYYY that means it was working for you all along.

By the way, I think I've made my last change for v7.1 Beta 1, so I'll be working on bundling it up today. I also added you to the Prerelease Testers group, so that gives you access to a new section on the forum, so you will have access to Betas from here on out.

[Pauven]

CMC v7.1 Beta 1 is now available. Please visit the Prerelease post here: viewtopic.php?t=566

Since you're new to the Prerelease Group, the standard practice is to reply to that test thread with any bugs/issues you discover during testing. You can still comment here on this thread for any comments regarding the 01/01/9999 date issue, to keep that all in one place.

[michae1a1ee]

I'm going through the threads on the Prerelease Group now.
I get that the CCC version has to match CMC version. I'm using CMC installed in C:\CMC as per your documentation. To upgrade this app should I just be extracting the 7.1 Beta into that C:\CMC folder and overwriting existing files?
Or, if I make a C:\CMCBETA folder (which I did originally), how do I get that separate copy of CMC to use an updated CCC? Is it a separate instance of CCC that I have to setup/configure?

[Pauven]

While you can easily run multiple versions of CMC on the same PC (simply by placing them in different folders), CCC is not really designed to be used this way.

My recommendation for you is to just extract the full zip into your existing C:\CMC folder.

V7.1 is mostly just a bug fix anyway, very minor changes, so it's low risk to simply upgrade your existing 7.0 install.

[michae1a1ee]

Took your advice and just extracted to C:\CMC rather than creating a second BETA instance/folder structure and complicating the matter.
Started CMC 7.1. Did a Full Export with "the firm" in the filter field. Launched CMC and...

image.png (49.63 KiB) Viewed 227 times

You figured it out!
I guess now it's time for another Full Export with no filters.