Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    I’ll take a look on my own site to see if I notice anything.

    In the meantime, turn on EWWW’s debugging, and see if that makes any difference (it has the side effect of disabling background optimization).

    Plugin Author nosilver4u

    (@nosilver4u)

    Works perfectly on my dev server, so let’s narrow it down like so:

    1. Disable all plugins, does it work now?

    2. If not, switch to one of the default themes, does it work now?

    3. Assuming you have it working with “stock” settings now, enable EWWW. Does it work?

    4. Keep activating plugins until it breaks again, there’s the real culprit.

    Thread Starter Novelty

    (@candied)

    Sorry for the late reply I thought wordpress would email me for updates. I was able to solve the problem by turning off the “delete originals” option. It might be a good idea to put this in the option as a side effect. Thanks for an awesome plugin and keep up the good work!

    Plugin Author nosilver4u

    (@nosilver4u)

    So you were using image conversion options? Like GIF2PNG or one of the others? That’s the only time the delete originals option does anything at all. Otherwise, I would wonder if that was just a coincidence, and the last update fixed something unexpected.

    Thread Starter Novelty

    (@candied)

    Yes, I currently have that option checked. It still happens whenever delete originals is enabled. I checked it to save space, if this is a bug please let me know when it gets fixed or if this was by design maybe you could guide me into which options I should use?

    Plugin Author nosilver4u

    (@nosilver4u)

    Ok, that gives me more to go on, so I’ll see what happens there. I suspect though, that the editor is trying to load the image that was deleted, and I don’t know if there is a way to catch it before it does that.

    So that I’m clear on this, these images you are cropping were not converted yet, but they are getting converted at some point during the cropping operation, right?
    If you can give me a little idea of the exact workflow here, that would help a lot, plus if you could post links to a couple of the originals, that would be really useful too.

    Thread Starter Novelty

    (@candied)

    I think they are already converted because the image was already saved in the post then later opened and edited by another account.

    The workflow process, first they create a post. The featured image is uploaded by someone then saved as draft. Later, another account would open the post and double check if it looks good. This is where it happens, when an editor decides to crop the saved featured image inside wordpress nothing happens. They are able to see the cropped version on the image editor screen but not on the edit post page and published post.

    Here is a link for an image created when delete original was still checked. Now that it is unchecked I am able to crop it, I guess WordPress detects it as the original again.

    Plugin Author nosilver4u

    (@nosilver4u)

    Ah, I wonder if the featured image information doesn’t get updated. EWWW updates the attachment meta, the mimetype, etc. And then it updates any posts that contain the image. But a featured image isn’t in the content, it’s probably stored in the post meta or something like that. I’ll see what I can do.

    Thread Starter Novelty

    (@candied)

    Thanks, I appreciate it.

    Plugin Author nosilver4u

    (@nosilver4u)

    Ok, so I dug into this today, and while I found a couple other glitches with the conversion process, the featured image stuff should be completely unaffected. What I found is that the featured image is simply stored as a post ID. I couldn’t find any instances in my database where the original filename was stored, except the GUID, which is not supposed to be changed. It’s stored as a url, but it isn’t supposed to be used as a url. Kind of weird, I know, and something that could affect a poorly written theme/plugin, but certainly not something that would affect WP core, as they never use that field to load the image.

    I then tried to see if perhaps it was a permissions thing where the authors were uploading images that didn’t get optimized/converted, and then during editing perhaps it was being converted, but with background optimization, that simply isn’t feasible.
    I even tried with background optimization disabled, like it would be if you were using the Shield plugin, and it takes a while longer, but it still seems to work just fine for me.

    From what you said, the image only “disappears” on the post editor and the actual published post, so my suspicion is that something is referencing the GUID, that’s the only thing that would make sense to me at this point.
    Would it be possible for you to contact me here: https://ewww.io/contact-us/

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘When plugin is enabled cropping featured image doesn't work’ is closed to new replies.