Automatic image compression tries to compress manually uploaded plugins

  • Resolved aaylasecura

    (@aaylasecura)


    1 month, 1 week ago

    This is not a fatal issue, but thought I’d mention it. I have “Automatically compress newly-added images” enabled and every time I manually install a plugin zip file, I get an error logged in Query Monitor that WP-Optimize tried to smush the, now missing, zip file which was automatically deleted after plugin install.

    I think WP-Optimize should avoid processing non-images in the uploads directory.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Is there a specific reason why you are uploading plugins to the “uploads”

    If your uploads your plugins to the “plugins” folder do you get the same issue?

    I will have a go at replicating this as well

    Thread Starter aaylasecura

    (@aaylasecura)

    Thanks for replying. I’m just using the built-in WordPress upload plugin feature in Add new plugin, upload plugin. Then Query Monitor shows the below warning. Just noticed, the warning is due to trying to unlink the whole directory, actually, kinda strange:

    View post on imgur.com
    unlink(/home/customer/www/staging28.dev.meditateinwellington.org/public_html/wp-content/uploads/): Is a directory
    wp-content/plugins/wp-optimize/includes/class-updraft-smush-manager.php:1650
    • This reply was modified 1 month, 1 week ago by aaylasecura. Reason: Added text content of warning
    • This reply was modified 1 month, 1 week ago by aaylasecura.
    Plugin Support vupdraft

    (@vupdraft)

    Thank you. The “unlink” error message is normally related to file permissions

    What are the file permissions to: wp-content/plugins/wp-optimize/includes/class-updraft-smush-manager.php and your Uploads directory?. They should be 755.

    Thread Starter aaylasecura

    (@aaylasecura)

    The uploads directory is 755 and class-updraft-smush-manager.php is 644 (which is ok, because it’s a file and doesn’t need the execute bit). I’m wondering why the error seems to imply that the uploads directory was attempted to be unlinked. Looks like in the function unscheduled_original_file_deletion the original-file meta field was blank and so $the_original_file became just the base uploads directory.

    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Upon closer inspection , it looks like the plugin is looking for an file called. Extra-callbackups-for-jetengine-0.0.0.zip.webp

    It looks like you might have installed this plugin in your Uploads. Removing it should fix the issue

    Thread Starter aaylasecura

    (@aaylasecura)

    Thanks for looking into this. That’s the plugin I was installing via the built-in manual plugin upload of WordPress. I’ve never explicitly placed it into uploads, it looks like that’s what WordPress may do with it’s “Upload a plugin” for installation feature. It probably temporarily places it there before extracting and deleting it.

    Plugin Support vupdraft

    (@vupdraft)

    No problem, I would not have though that this will have been intentional. Plugins are always in the plugins or muplugins folder – otherwise you would not be able to be able to use them

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.