• Resolved Nate LaChance

    (@archenemys)


    I used this plugin a few years ago but removed it for performance issues.

    I’m regenerating thumbnails and get an error that references EWWW Image Optimizer still in my data base. I search my database and find over 70,000 EWW_Image_Optimizer references… What in gods name is going on??? Thats a crap load of usless bloat to my data base.

    Why was this not removed and how the hell does one get rid if it???

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Shane Bishop

    (@nosilver4u)

    you can completely remove the ewwwio_images table, that’s normally the bulk of it.

    Thread Starter Nate LaChance

    (@archenemys)

    Yes, that was already done years ago. The ewww references are in the postmeta table.

    a:6:{s:5:”width”;i:383;s:6:”height”;i:500;s:4:”file”;s:31:”2-wheel-tuner-girl/2WTMag08.jpg”;s:5:”sizes”;a:9:{s:9:”thumbnail”;a:5:{s:4:”file”;s:20:”2WTMag08-114×150.jpg”;s:5:”width”;i:114;s:6:”height”;i:150;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:6:”medium”;a:5:{s:4:”file”;s:20:”2WTMag08-229×300.jpg”;s:5:”width”;i:229;s:6:”height”;i:300;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:12:”slider-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-383×395.jpg”;s:5:”width”;i:383;s:6:”height”;i:395;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:10:”blog-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-383×300.jpg”;s:5:”width”;i:383;s:6:”height”;i:300;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:12:”teaser-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-332×205.jpg”;s:5:”width”;i:332;s:6:”height”;i:205;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:15:”gallery-1-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-383×432.jpg”;s:5:”width”;i:383;s:6:”height”;i:432;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:15:”gallery-2-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-268×268.jpg”;s:5:”width”;i:268;s:6:”height”;i:268;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:15:”gallery-3-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-268×164.jpg”;s:5:”width”;i:268;s:6:”height”;i:164;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}s:11:”video-thumb”;a:5:{s:4:”file”;s:20:”2WTMag08-383×393.jpg”;s:5:”width”;i:383;s:6:”height”;i:393;s:9:”mime-type”;s:10:”image/jpeg”;s:20:”ewww_image_optimizer”;s:10:”No savings”;}}s:10:”image_meta”;a:10:{s:8:”aperture”;i:0;s:6:”credit”;s:0:””;s:6:”camera”;s:0:””;s:7:”caption”;s:0:””;s:17:”created_timestamp”;i:0;s:9:”copyright”;s:0:””;s:12:”focal_length”;i:0;s:3:”iso”;i:0;s:13:”shutter_speed”;i:0;s:5:”title”;s:0:””;}s:20:”ewww_image_optimizer”;s:10:”No savings”;}

    Plugin Author Shane Bishop

    (@nosilver4u)

    There isn’t an easy way to remove that, which is why recent versions of EWWW no longer use postmeta. It’s serialized data, so you can’t just use a search/replace, and cleaning all 70,000 records would take a very long time, thus there is no cleanup routine built-in.

    Basically, a cleanup routine would have to go through each attachment id, fetch the attachment metadata, unset the ewww_image_optimizer key/index, and then save the attachment metadata back to the db.

    Thread Starter Nate LaChance

    (@archenemys)

    So your saying that you do not have a way to remove 70,000 records of metadata bloat form my sites database that your plugin apparently “left behind”?… even though upon removal of the plugin it was confirmed to “remove” all files? And you knew this files would not be removable unless manually removed?

    Database bloat is what this plugin is supposed to eliminate, not add to!

    There are probably 1000’s of websites out there that have this issue and don’t even know it.

    So what kind of support do you provide for an issue of this magnitude where it is clearly a programming issue?

    Plugin Author Shane Bishop

    (@nosilver4u)

    Right, right, and right. It was a design I inherited from CW Image Optimizer (and it from WP Smush), and at the time it seemed the best way to do things (storing it elsewhere requires extra db queries when managing the media library).
    Unfortunately, for past users of EWWW IO, there are no plans to fix that.

    For current users, that data will begin to be cleaned out within a few releases, once I’m very confident that the migration routine is working as it should, and for the last few releases, the plugin has not added any new information to the postmeta.

    If you’re really that desperate to regain database space, you can enable the cleanup tool manually within EWWW (uncomment lines 4839 and 4845 of common.php), visit every page of your media library (increase the number of images per page to 200 or so), and that should move all the data from postmeta to the ewwwio_images table. Then delete the ewwwio_images table, remove the plugin and be done with it. It’s a lot of work, but far less than what you seem to be asking of me.

    Thread Starter Nate LaChance

    (@archenemys)

    Quick update for a fix if anyone has same issue. Cost of $1500 developer fees to basically clean up database from ewww. 🙁 Yup not happy. Thats the price you pay for trying to optimize over 20,000 photos…

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

The topic ‘completely remove this plugin’ is closed to new replies.