Forum Replies Created

Viewing 15 replies - 136 through 150 (of 1,405 total)
  • Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    Thank you for your feedback and it is indeed a good thought. My honest answer is that I indeed don’t know πŸ™‚ not until I do some relatively thorough testing. This is on my list, but, unfortunately I am not there yet.

    If that helps, I will try and explain a bit how the plugin works.

    Now, when a web page load the plugin serves a bit of Javascript that sets a cookie on the user browser containing the size of the user’s screen. Then this cookie travels back and forth on any HTTP communication the browser does with the server.

    When the browser requests an image by the server the plugin hijacks this requests and tries to deliver an as small as possible image to the browser. This decision is made by combining the plugin settings that the website admin has set and the device size.

    The issue with Multisite would be on the way this hijacking is done. In a normal WordPress installation there is one /wp-content/uploads folder, but on a Multisite there are multiple ones. And, should one try to overcome this, they should take into account the htaccess files rewrites that are necessary as well as the PHP code to which these rewrites ultimately point to.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    I am so sorry to disappoint you but the plugin does not support Multisite at all. If something is actually supported in this respect it would be be sheer coincidence!

    As far as the Imsanity plugin is concerned, yes, there should be no conflict with these two plugins because they operate on a completely different level. Imsanity resizes your original images and afterwards, only when they are requested, Adaptive Images delivers them to the mobile devices resized according to screen size.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, there,

    Thank you for reaching out to us!

    There are many reasons this might happen. Some of them might concern your host and their setup and others might even be a bug. Also sometimes it is a matter of correct configuration. Good thing is that the Adaptive Images plugin does not touch your original images, so they remain safe in their place after you disable it.

    Now as a first thing, I would like to ask of you to momentarily enable the plugin and send me the result of the Print debug and Print diagnostics buttons in the plugin settings page, if it is possible. From that I will be able to draw some first conclusions.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, there,

    I am really sorry for this my friend, but usually this works the other way around. A plugin is not considered to be Mu compatible unless it specifically says so. However, we do not wish to cause any confusion and we will add such a notice in the plugin description.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    One more word though: the redirect I am talking about is not an HTTP redirect like the 301. It is an internal redirect where the server is handing the control for the current request over to some bit of code or module that it possesses.

    I would love it if you could share your solution with us when you make it!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, there,

    Now this is something we have not tested, but I believe should work at least in principle. What needs to be done manually (after the plugin is activated and its settings saved) is to redirect image requests internally to the Adaptive Images script which is the adaptive-images-script.php file inside the plugin files.

    This is something I have no idea how to do in IIS and would certainly need some testing and perhaps debugging afterwards. In Apache one can easily (more or less) tamper with the htaccess file and do these things automatically. In NginX one needs to make some manual changes, but these are more or less standard.

    Let me know if this helps and how it goes. I would love to hear that we can ultimately support IIS!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, again,

    Well, if the problem is solved, then this is great!

    Let me know if I can help any further in future.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    Thank you for reaching out!

    The plugin is designed to never crop image. It only resizes them according to device size. Usually, when an images seems cropped in the browser, this is usually due to the theme, its layout and CSS. However, could you please point me at some particular image to check?

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, @k3nsai,

    The answer to your question could possibly be a hook or filter of the theme, one that might allow you to play with the original product image url. But this is up to the theme I guess…

    The only other viable (and easy) solution that you might consider is the one I already mentioned, adding big enough breakpoints in the plugin settings. It is a compromise of course.

    All in all I know it is a bit frustrating, but it is almost impossible for the plugin to automatically predict which images might need special handling and thus not be resized.

    Cheers,
    Takis

    PS: Yes, we do accept both! πŸ™‚

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, again,

    I think I know what you mean now. You are talking about the zoom function on the single product image after it pops up on the user screen.

    That is a tricky one!

    First of, the Adaptive Images plugin is trying to handle all your images unconditionally and transparently. So it handles that image as well. This means that the image you are seeing there is indeed the original image, but the plugin has resized in the background in order to make it fit the device dimensions and thus save some bandwidth. I realise this is not entirely desirable in your case.

    And, as I said it is a tricky one!

    Unfortunately, the Adaptive Images plugin can only make an exception on an image, if you refer to that image with a GET parameter at the end of its url like https://gooakoo.com/wp-content/uploads/2019/03/EX4106TCSBLBK-PowerToolRack.jpg?resolution=original. But I guess this is not very practical on a ready-made theme.

    One other solution is to have bigger breakpoints in the plugin settings. For instance instead of the default “480, 768, 1024” you could set “768, 1280”. This way the images produced will be bigger for all device sizes and this will partially solve your issue. (Remember to clean up the plugin cache when you change the breakpoints.)

    Apart from the above there is not much you can do really. The particular case you have at hand goes against the very idea of the Adaptive Images plugin, which is to downsize all images on mobile devices in order to save bandwidth. So, ultimately one needs to make some choices I’m afraid.

    Let me know if this makes sense.

    Cheers,
    Takis

    PS: Yes, we will definitely keep an eye on Webp, that is for sure!

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello,

    No, unfortunately we do not support the Webp format yet. It is under our radar for future versions, though!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, @k3nsai,

    Thank you for your kind words!

    The issue you are describing sounds like a theme issue at first. It is the theme’s job to select the correct thumbnail size at each point of the layout and for each user function (like the product zoom/popup image). I would need to take a look at your website to be certain, though. Could you share the website url with me perhaps?

    Cheers,
    Takis

    Thread Starter Takis Bouyouris

    (@nevma)

    Hello, Marko,

    Thank you for your answer. Isn’t 430KB too big for the HTML of a blog article? I know you can’t say for sure, but I suspect there is something wrong here. This size is really too big and the cache never gets purged, not even when I purge it manually, not even when I disable the page cache!

    Cheers,
    Takis

    Thread Starter Takis Bouyouris

    (@nevma)

    Hello, Marko,

    This is why my original 2 questions were:

    1) Is it natural for a blog with 7000 posts to get a page cache as big as 3GB just by storing the HTML of the posts?

    2) Why isn’t the disk space become free when emptying the page cache manually from the plugin settings?

    Cheers,
    Takis

    Thread Starter Takis Bouyouris

    (@nevma)

    Hello, Marko,

    The Garbage collection interval is set to 14400 seconds.

    Cheers,
    Takis

Viewing 15 replies - 136 through 150 (of 1,405 total)