mseb

I deactivated the Plugin and activated again, now it works again…

Thanks, I can just add that code to the functions.php and then it will be deactivated, correct?

Great thanks… But somehow I am getting 72.5KB for the extended subset, not 11KB, or was that 77kb for ext and 11kb for normal?

Hi Daan,

allow me one more question.. If I would replace the huge font in the cache folder from OMGF by the smaller one from the url you posted above, would that help? Or would OMGF overwrite this again e.g. overnight?

Thx
Mirko

Hi there, I have updated to v2.5.2 but in your wiki I cannot find any instructions on how to deactivate the cookie, could you please let me know? Thx, Mirko

Yes, indeed, I don’t even know how that happened ??

However I am left with the fact that based on the size a 300×300 is requested (and coming) but then downsized to 200×200… Adding the new 200×200 size unfortunately also did not work out. Would that be a bug somewhere to be reported or any suggestions?

I would be happy with 200×200… as somehow these dimensions are defined as width and height while loading in the img src, apparently by the WordPress function the_post_thumbnail but if easier also 300×300 should be fine.

Just tried to add a 200×200 size and use that, but then it takes 225×300…

Try this url:
https://www.wroclawguide.com/en/have-you-been-to-these-unusual-cafes-in-wroclaw/

And here screenshot of media:
https://www.dropbox.com/s/4q2sh1j6qwo559h/media.PNG?dl=0

Thanks again!

Hi there,

Thanks for the great and detailed feedback, I just checked it in more detail.

Actually ashe-full-thumbnail is defined as 300x300px in the media settings, but then I would expect that the picture is then also rendered with 300px and not somehow magically downsized to 200x200px, loading and requesting the 300x300px image.

Funny enough there are 200x200px versions of the pictures available, just exchanging the URL of the 300x300px image is proving that, but in the media settings there is no definition of any 200x200px size, hence rebuilding thumbnails does not even offer me the 200x200px size (well, I guess not required if the 200×200 version does exist).

Any suggestion you would have? Probably creating a new size name with 200×200 and replacing “ashe-full-thumbnail” by this one in the code?

I can set up one… How can I best submit login details to you?

Correct… now I found out, when I am logged out all seems to work fine but when I am logged in as Admin, the issue persists. Why could that be?

Ok done now and cache cleared, will leave it active for one hour now before rollback again as it means that the shop won’t be available.

In addition, not sure if that is a co-incidence or not, since the day this has happened the first time, we see a huge drop in organic traffic in Analytics (-80%) while in Search Console the clicks are quite stable…

Yes sure, just head to wroclawguide.com and select either book or shop from the main navigation menu, with anything above 2.6.0 that won’t work. But now I am running on 2.6.0 again, do you want me to update to 2.6.2 for a couple of minutes?

Unfortunately issue still exists here with 2.6.2…

Updated again to make another test, cleared cache, and getting 404 from menu permalinks. Rollback to 2.6.0 and it works again.

I did and didn’t help…. Also the cached files would be supposed to work due to my roll back before.