Lots of problems. Deleted images. Crashed DB

  • braintraincoach

    (@braintraincoach)


    1 month, 2 weeks ago

    I had very high hopes. The bulk optimization somehow deleted images from my media library and thus from the website, too. How does this happen? My media files showed a blank icon where they used to be. At least, the backup originals worked so I could go into my hosting file manager and see the images which were deleted and resurrect them.

    I also used the database cleaner briefly after the optimization. This created huge problems such that I had to use a week+ old backup and site restore with a lot of work lost on a new template. I don’t know what happened. It was just a mess. My media images did not restore. HOW?

    Then, in an attempt to recreate the images and fix what was needed within that plugin, I had to buy a month of service to use the optimization again.

Viewing 1 replies (of 1 total)
  • Plugin Support Saransh

    (@saranshwpm)

    1 month, 2 weeks ago

    Hi @braintraincoach,

    I’m really sorry to hear about the experience you described. I understand how frustrating it must be to deal with missing images and restoration work.

    Imagify itself cannot delete images from the WordPress Media Library. What the plugin does is optimize the existing images and replace them with their optimized versions. If the backup option is enabled in Imagify settings, the original images are also kept safely in a backup folder so they can be restored at any time.

    In some rare situations, layout or display issues can occur when the <picture> tag method is used to display next-gen images (WebP/AVIF). If that happens, disabling the “Display images in next-gen format” option or switching the delivery method usually resolves it. However, this would not delete images from the media library.

    Since you also mentioned using the database cleaner and performing other operations around the same time, it is possible that another plugin or a conflict may have affected the media entries in the database.

    If you’re open to it, I’d really recommend reaching out to our support team or replying to any existing ticket you may have so we can properly investigate what happened and help prevent it from happening again.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.