• Hi, I’m having multiple issues with the way MLP works with thumbnails in the database. I’m able to work around them, but it causes me headaches if I don’t follow a certain procedure.

    1. When new images are uploaded via MLP and then shown on a page or post, the srcset attribute is not properly generated. When the “Regenerate Thumbnails” command is used, srcset then works correctly on the image. (By the way, there’s a typo on “Thumnails”.)

    2. When images are renamed or moved to another folder, the original thumbnails stay in the original location, orphaned from the database, while new thumbs are generated for the new name or new location. Instead, in the case of renaming, the original thumbs should be renamed, not regenerated; and if an image is being moved, the original thumbs should follow the primary image to the new location – either moved or copied according to user command – again, not regenerated. If the Sync command is used in a folder after an image is moved out or renamed, each orphaned thumbnail is added to the database as its own image, and new thumbnails are regenerated for each of those added images. It’s really annoying.

    3. I use the Post Thumbnail Editor plugin to customize the crops of many of my thumbnails. When PTE saves the updated thumbnail, it saves as a different filename with a 10-digit number appended to the end (the old version is automatically deleted). WP has no trouble finding and displaying these thumbnails with new filenames, but MLP does not recognize them. So, when I use Regenerate Thumbnails, the PTE-generated files still exist and are orphaned (I would expect them to be deleted or replaced with the newly generated thumbs). That means when I’m adding new images via MLP, I have to be sure to Regenerate Thumbnails first so srcset works, then do my edits with PTE. If I use the MLP Sync command after I’ve used PTE on any image within a given folder, I get a big mess: the thumbnail paths for PTE-edited images are messed up, the PTE-edited thumbs are added as original images with their own thumbnails, and I have a bunch of useless files to clean up. If I move, copy or rename images with PTE-edited thumbnails, I lose that work because the thumbnails are always regenerated instead of moved/copied/renamed along with the original image size (and as noted before, if I move them, I’m once again left with orphaned thumbnails).

    • This topic was modified 9 years, 1 month ago by wasionthenet.
    • This topic was modified 9 years, 1 month ago by wasionthenet.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author AlanP57

    (@alanp57)

    wasionthenet,

    Thank you for you detailed description of these issues. I will look into them and get back to you in a few days.

    Alan

    Plugin Author AlanP57

    (@alanp57)

    I had an opportunity to review your issues and I found that they are cause by the non-standard file naming convention of the Post Thumbnail Editor. I think it is safe to say the format of image thumbnails should be <unique-file-name>-<thunbnail-width>x<thumbnail-height>.<extention>. But the post thumbnail naming convention goes against this by using <unique-file-name>-<thunbnail-width>x<thumbnail-height>-<ten digit number>.<extention>. The ten digit number needs to be before the file size.

    And concerning the use of srcset infromation, WP 4.7.2 does not include the srcset when I upload and insert from the Media Library. And the same is true if I use Media Library Plus. How is it that WP includes the srcset info on your site?

    Plugin Author AlanP57

    (@alanp57)

    Also, the name you see under the image in Media Library Plus comes from the post_title field. The Post Thumbnail Editor does not change it when it changes the image’s file name.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Issues with srcset, orphaned thumbnails, Post Thumbnail Editor’ is closed to new replies.