Forum Replies Created

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

    (@nevma)

    Hello, my friend,

    Yes, 644 should be correct!

    Can you check with your host if your htaccess is writeable via your web server user? It might be possible that they are protecting it some other way or that your user is not the owner of the file.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    It seems that PHP falsely reports your htaccess file as non writeable for some reason. We have not figured this out yet. On the one hand, this issue could only be reported in the Adaptive Images settings area. On the other hand, in cases where the issue is real, it is an issue that the website owner definitely needs to fix!

    We are trying to find a solution for this!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    I am very sorry for the late reply, but the email notification got somehow misplaced.

    I looked at your staging url but it seems not active at the moment. If your issue still persists and you can activate the url again, I would be glad to take a look!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    Can you check the permissions of your htaccess file, please, and tell me what they are?

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    No, you should not do that because it might break the functionality of the theme or plugin that created them. It is the idea of separation of concerns.

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello,

    The Adaptive Images plugin does not mess with your original images or the thumbnails that WordPress creates at all. It has its own cache and creates its own thumbnails. But it only creates them when they are requested and if they are requested at all. Also, you may flush this cache from the plugin settings page. And if you actually have big images then the size of the cache will probably only be a small fraction of the total size of the original images anyway.

    Hope this helps!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, again,

    In Firefox it sounds quite strange, to be honest, unless something weird is happening in Mac and Javascript is reporting the screen size and not the browser window inner size.

    As far as Safari (in Mac and iOS) is concerned I’m going to have to run some tests under these specific conditions and see what’s wrong there.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, again,

    Unfortunately, no, this is the case that is currently impossible to work. It grieves me to say so, but this is how things are.

    However, I always present the argument that, if a website is not high traffic or does not have users distributed all over the globe, then the benefit of using a CDN might be minimal or even unnoticeable especially compared to the effort and cost the CDN ultimately has.

    But, of course, I am aware of all the counter-arguments, too! 🙂

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    Thank you for reaching out!

    The issue you are describing touches the core of how CDNs work indeed. And it all boils down to the question “who is the one who actually delivers the image to the browser”. When a CDN is used it is the CDN who does that. It is the CDN alone who communicates with the browser and can make decisions as to what it might deliver at each time.

    Unfortunately, when CDNs use a subdomain it is impossible for the original WordPress installation to communicate with the CDN and instruct what to deliver to the browser. As far as I know CDNs use subdomains but not always, not even in the majority of the cases. And you can use SSL in any case, this has nothing to do with subdomains or not.

    When you use a CDN without a subdomain it is possible to make the original WordPress installation work with the CDN in order to deliver adaptive images to the browser by enabling the CDN support option in the plugin settings page. This adds a url parameter at the end of the image urls for this purpose. Of course this option is a bit experimental. Nothing risky there, just some images might be delivered in original and not resized versions.

    We are trying hard to tackle this general issue, but we haven’t come up with a full solution yet. Keeping our fingers crossed!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    Thank you for your kind words!

    Can you tell me what browser you are using in each case? I suspect it might have something to do to with the browser or the browser version.

    Cheers,
    Takis

    Hello, @tigroumeow,

    Plugin used to work for me, then, suddenly the Scan process either freezes right away and I see an empty Ajax request in the browser console or it produces an error popup with a message saying “524 No Reason Phrase”.

    Not sure if this is the same issue like the one you are describing in your post.

    I do not have WooCommerce or Flatsome and I have tried the Reset process and also deactivating and even totally deleting and reinstalling the plugin.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, my friend,

    Thank you for your message, you are right, this is a case that was missed in the original plugin development and the message can indeed get annoying, always appearing in one’s /wp-admin. We are trying to squeeze an update for this in our development process in one of the next versions.

    Hope you can bear with it a little bit longer!

    Let me know if I can help any further.

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Apache standalone should behave as designed and this is what my test in your website show, as I mentioned in my first comment (https://prnt.sc/pyxrd2/).

    I will try to dig into this a little bit more in the next weeks though!

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, Peter,

    Normally caching plugins do not handle images. However, if you are using a caching server (like NginX) or a CDN, then, yes, these will be handling and delivering images and they can even not let the image requests reach your website at all (for instance a CDN with a subdomain for serving static files).

    Cheers,
    Takis

    Plugin Author Takis Bouyouris

    (@nevma)

    Hello, Peter,

    As far as I know and have researched Google has not mentioned anywhere that it uses any of the known tools (like Pagespeed or Lighthouse) to measure automation. And, as I explained earlier, this does make sense, in my mind!

    What it does use is the browsers’ Javascript perfomance API, which it can invoke through Google Analytics. And there is one more argument to support that: this way it knows a lot more about all of the requests a website serves and not just on or a few.

    Also, what makes even greater impact is the fact that fast web pages create users who are happier and spend more time in one’s website and that is one of the strongest assets Google measures and has nothing to do with on-site or off-site SEO. It is the actual user behaviour towards one’s content. And speed is a major factor to affect it!

    Now, about Webpagetest, I am a little bit surprised because all my earlier tests showed that it did detect downscaled images when I set it to load them from a mobile device. I will need some time to double check this and debug it a little bit deeper though!

    Cheers,
    Takis

Viewing 15 replies - 76 through 90 (of 1,405 total)