The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I'm testing this out for a site that has thousands of duplicate images based on a Commerce Feeds Import workflow. (The first product image was unique and the second image was a shared/common image that imported as a duplicate.)
All that to say, as I began testing I noticed a spelling error. Patch coming shortly.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Before.png | 17.69 KB | krina.addweb |
| #3 | After.png | 22.02 KB | krina.addweb |
| #2 | spelling-2893634-comment2.patch | 769 bytes | laryn |
Comments
Comment #2
larynPatch is attached.
Comment #3
krina.addweb commented@laryn, Thanks for the typo correction. It works well. PFA
Comment #5
fietserwinThanks for reporting. Fixed and committed. BTW: I am interested if this module works fine on your scale as well, please let me know your findings.
Comment #6
laryn@fietserwin,
I'm actually not having much luck yet in bulk. I have tried disabling md5, not showing any thumbnails, restricting the maximum quantity down to 10 to test, and disabling most of the image styles (We have a ton of image styles defined) -- which seems to work, but if I try to run in bulk it gets through to the "Find Usages" page and then hangs (or goes back to the first page). I saw the other issue about a drush command and something like that could be ideal, or a page to configure settings to use and have it run automatically for a certain quantity on every cron run (similar to the way that search indexing happens). That way it could slowly chew its way through all the duplicates without me having to slowly go through the whole process repeatedly.
We do have file_entity and media installed on the site, although I haven't been able to do enough testing yet to say for sure that things are working perfectly with them.