Conflict with SPCDM plugin

  • Resolved OMP

    (@spiderdudececil)


    8 years, 8 months ago

    So after days of digging around and testing an issue with another plugin on my site, I discovered that EWWW Image Optimizer was causing a conflict with another plugin, SP Client Document Manager.
    In the EWWWIO plugin’s Conversion Settings tab, the option: “Alternative WebP Rewriting Uses output buffering and libxml functionality from PHP. Use this if the Apache rewrite rules do not work, or if your images are served from a CDN,” when checked would cause SPCDM’s file manager UI to malfunction.
    Unchecking the option, the SPCDM UI is functional again. Posted about this issue at SPCDM’s support page, in the hopes that the devs could connect and sort it out.
    I can’t say what other conflicts there might be, but this is what I’ve found so far. I’ll be posting back if I notice other issues in my setup.

    https://www.ads-software.com/plugins/ewww-image-optimizer/

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

    (@nosilver4u)

    Can you provide a link to the SPCDM plugin? I’m not familiar with that one.

    I’ve resolved some conflicts that sound very similar to this one in the upcoming 2.6.0, so it should be relatively easy to fix. Just need to get my hands on it to see what needs fixing.

    Thread Starter OMP

    (@spiderdudececil)

    Hey NoSilver. Glad to hear that you may already be have this taken care of. I honestly could not do without EWWWIO. I eagerly await 2.6.0.
    SPCDM is a somewhat obscure plugin, but gets the job done, at least for my specific purposes. Have a look: https://www.ads-software.com/plugins/sp-client-document-manager/

    Plugin Author nosilver4u

    (@nosilver4u)

    Sorry, I didn’t mean I had fixed that specific bug, but that I had fixed some similar sounding bugs which should make this one easier to work around.

    Unfortunately, it wasn’t quite what I expected. It appears they are using invalid html, which the libxml parser is trying to fix. In the process of “fixing” it, the javascript is broken. I’ll try to find a fix, but this could be a tricky one.

    Plugin Author nosilver4u

    (@nosilver4u)

    Ok, so there is nothing I can do in EWWW, as the libxml parser is simply following the HTML5 spec properly. But, I did figure out how to fix the SPCDM plugin, and I posted my findings (with the fix) on your other thread.

    Thread Starter OMP

    (@spiderdudececil)

    Well, at least you got to the root of the problem. Now I face a dilemma, and I suppose I’ll end up going the htaccess route for WebP rewrites.
    I can’t tell you how much I appreciate you taking the time to look into this issue.

    Plugin Author nosilver4u

    (@nosilver4u)

    As long as you do not use a CDN or proxy cache like Cloudflare, or Sucuri Cloudproxy, the .htaccess rules will work just fine. In fact, that is the preferred way to do it, because it never touches the html of your site, and is faster.

    Thread Starter OMP

    (@spiderdudececil)

    hmm.. I do use Cloudflare. Haven’t noticed an issue as such, but could you elaborate on how Cloudflare’s service could affect rules for webp images in .htaccess? My understanding of network processes is pretty rudimentary at best.

    Plugin Author nosilver4u

    (@nosilver4u)

    If you use Cloudflare, they will be caching images that are different with the same image name. The way the .htaccess rules work is that your image urls do not change, but the server swaps in the webp version transparently for supported browsers. So a url like https://mysite.com/wp-content/uploads/1234.jpg will be a normal JPG image for Firefox and IE, but it will actually be a WebP image for Chrome. When you bring Cloudflare into the mix, it will cache whichever of those is requested first. If Firefox requests it first, a JPG is cached, and all browsers will get a JPG, regardless of if they accept WebP. If Chrome requests it first, a WebP image is cached, and all browsers will get a WebP image whether they support it or not, and for those that don’t support it, it will show up as broken/missing images.

    Thread Starter OMP

    (@spiderdudececil)

    Wow. Okay, hadn’t considered it that way. Food for thought. I’ll be starting my cross platforms tests today then, and report back if things look wonky. Thanks again for all your help and feedback.

    Plugin Author nosilver4u

    (@nosilver4u)

    Just wanted to also clarify on the fix that I presented to the SPCDM devs, that the only one required to fix the Webp stuff is #3, and it only involves adding a single slash to that line, so I think you could fix it yourself pretty easily (until they get to releasing it officially).

    Thread Starter OMP

    (@spiderdudececil)

    Thank, mate. That should do it for a bit until, as you’ve said, they push out the fix in a new release, if they do. You’ve been most helpful.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Conflict with SPCDM plugin’ is closed to new replies.

Tags