• Resolved ryancyan1

    (@ryancyan1)


    Hi, the magnifying tool no longer works when I hover over the images used. They used to work though, so I’m unsure where the problem lies. Any help would be appreciated, thanks.

    Ryan

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author SilkyPress

    (@diana_burduja)

    Hello Ryan,

    it has to do with the fact that the images URLs contain commas. Normally there aren’t supposed to be any commas in the URLs, as they should be encoded with the %2C character. See this article.

    Thread Starter ryancyan1

    (@ryancyan1)

    Thanks Diana,
    That’s strange because it’s only if I right-click and ‘View Image’ that I can see this in front of my usual URL: “https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_733/”

    Do you know why this is? I use an image optimize plugin called Smush, do you think that could be the cause?

    Thanks

    Thread Starter ryancyan1

    (@ryancyan1)

    What I mean is, if I look at the code in the Editing page it simply appears as this:
    <img src="https://cyan-designs.co.uk/wp-content/uploads/2018/05/folio-12.png" alt="" width="733" height="252" />

    • This reply was modified 5 years, 10 months ago by ryancyan1.
    • This reply was modified 5 years, 10 months ago by Andrew Nevins.
    Plugin Author SilkyPress

    (@diana_burduja)

    Yes, the “https://cdn.shortpixel.ai/client/q_glossy,ret_img,w_733/&#8221; in front of the images URLs is causing the issue with the zoom.

    No, it is not coming from the Smush plugin, but from the “Optimize Images” option on the WP Admin -> Settings -> Autoptimize -> Images page from the Autoptimize plugin.

    Currently you’ll have to choose between using the image zoom or the “Optimize Images” option from the Autoptimize plugin. But until the next plugin’s release I’ll look for a proper solution to the issue.

    Thread Starter ryancyan1

    (@ryancyan1)

    Excellent – that’s sorted it.

    Thanks for your help Diana

    Hey Diana;
    I’m Autoptimize’s developer, just quickly chiming in here concerning the comma not being %-encoded: the comma in this context acts as a sub-delimiter (with / being the gen-delimiter) to separate the values q_glossy, ret_img and w_733, so the comma is used for it’s reserved role and hence should not be %-encoded as that way it would loose it’s role as sub-delimiter. There’s more info in e.g. https://www.ietf.org/rfc/rfc3986.txt on this topic.

    Hope this clarifies,
    frank

    Plugin Author SilkyPress

    (@diana_burduja)

    @optimizingmatters Yes, you’re right. I’ve also took a closer look at the issue and stumbled upon the RFC3986.

    I’ll find a solution on my side that takes into account commas in the URL.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘No longer working’ is closed to new replies.