* Check for possible duplicated Media 1.4

[tatewise]

I cannot explain 1. as I have plenty of examples of two identical files with different file names that get reported.

Regarding 2. can you check the All tab of those Media records to see if they have two File links?
That might explain my plugin report and why Jane's and yours miss them.

[jelv]

The Bloomfield family spans both pages so two file links is a possibility.

[Mark1834]

Interesting - one of the two Media Records had a second file tucked away under the All tab, a forgotten relic of experimenting with multiple files before deciding that FH7 support for that new feature was patchy at best.

The plugin should report that scenario specifically rather than leave users guessing, so I’ll add it to the new plugin report before releasing it.

[David2416]

I have tried the versions from the Plugin store, 1.41 and 1,42 from this thread and am getting a "copy operation failed" message on, it seems, every media file. I had to cancel the plugin from the Task Manager. I did note that this plugin is likely to be withdrawn, thought I would mention the error anyway. OneDrive is running and all FH media files are present on the local hard drive (C: ....................)

Copy op fail 2023-12-12 085516.jpg

[peterbel]

Fascinating to read the direction this PlugIn is taking.
Happy to be a tester if it helps!

[tatewise]

David, that 'Copy operation failed' error is very odd.
All it is doing is copying the Media file to the FH public ProgramData file:
C:\ProgramData\Calico Pie\Family Historian\Plugin Data\Check for Possible Duplicated Media
Can you please check if that file exists or not? It has no file extension.

[David2416]

David, that 'Copy operation failed' error is very odd.
All it is doing is copying the Media file to the FH public ProgramData file:
C:\ProgramData\Calico Pie\Family Historian\Plugin Data\Check for Possible Duplicated Media
Can you please check if that file exists or not? It has no file extension.

File definitely exists and has an extension albeit .JPG (in caps) ; the plugin is reporting this error on every file.

The path C:\ProgramData\Calico Pie\Family Historian\Plugin Data\ exists, but no sub folder Check for Possible Duplicated Media

I had to stop the plugin via Task Manager.

[tatewise]

Check for Possible Duplicated Media is meant to be a type-less file, not a folder.
The .JPG extension may be the problem, so try deleting that Check for Possible Duplicated Media.JPG file and run the plugin again.

[David2416]

Check for Possible Duplicated Media is meant to be a type-less file, not a folder.
The .JPG extension may be the problem, so try deleting that Check for Possible Duplicated Media.JPG file and run the plugin again.

Hi Mike, apologies I misunderstood (thought you were referring to the file the plugin failed on )
I deleted the file Check for Possible Duplicated Media. and re-ran the plugin. It proceeded for a while and then experienced a "Copy operation failed" error repeatedly. Clicking either OK or Cancel proceeded to the next file and repeated the error message. I had to cancel the "Searching All Media Please Wait" process via the Task Manager. Then clicked OK on the outstanding "Copy operation failed" MessageBox to close the plugin. It either reported no duplicates found or duplicates found as below. Duplicates were only found having deleted the file Check for Possible Duplicated Media. before re-running the plugin. The same result was experieced whether or not I had closed FH after the error was experienced.

It did report three duplicates as shown in the attached screenshot. Running again the "Copy operation failed" comes up immediately.

[tatewise]

I'm not sure why it is failing in that way, but it may not be worth my investigation because I believe Mark's version will not need to copy Media files to obtain their content and hex encode them.
That is because there is a Windows certutil -hashfile command that does a similar job directly on the file.
Both I, and presumably Jane, were unaware of that function.

[David2416]

Fair enough. I'll remove the plugin and await Mark's version.

[Mark1834]

Now available here.

Does that resolve the various issues reported in this thread?