oliiix

Dear all Just had the problem that the core updater didn't update itself. When I clicked on update in the module menu it said it updated the module, but the version was still the same. So I downloaded it from TB site and uploaded it manually, no problem there, it's now the latest version installed. But there's another problem when trying to update wishlist block v2.0.0. This one says it needs an update, core updater says it did the update but it didn't like when I tried to update the core updater itself. When trying to download it manually from here... https://store.thirtybees.com/shop-modules/front-office/block-wishlist?search_query=wishlist&results=1 ...the download button is linked to the shops home page instead of the file 😉 Just thought of telling you quickly 😉 Have a good day everyone! Oli

Well that's not so good that there's no contact possibility listed on thirtybees marketplace page! Why is something that important missing? What if a module doesn't work, what if support is needed? What if money needs to be refunded because the module is just broken and the creator doesn't care? Why does thirty bees not answer in the first place as it's clearly their job to answer when there's no other contact options available (which should be mandatory for every module creator to list on their modules pages)...

hehe yes I know, but it doesn't tell which images have been processed and as there wasn't any file with webp extension to be found, I did them all 🙂 Well, after doing them I have no idea what exactly happened. Image sizes are the same, all still with jpg extension (is there any reason to this? I mean that they all end with jpg even though they are png?). No sign of them having changed to webp. Tried uploading a webp image manually to a product and it tells me webp isn't a valid format :'D But if we look at the statement in the image settings again, it says: " Serve smaller images in the webp format to browsers that support it " First of all actually the first post here in this thread was right, it clearly says "smaller images" are being served in the webp format. Might be just incorrectly written. Second of all else: It says serves. That clearly leaves no indication that any pictures are being changed, it almost sounds as if the pictures are being converted to webp on the fly on page load, which of course shouldn't be the case, but still everything about this is simply unclear, especially because it doesn't seem to work AND I cannot even add a webp image manually to any product.

As i know from prestashop, not sure about TB, at least PNG images keep the JPG extension even though it's PNG (complete nonsense, but that's how it is), might be the case as well for webP? So the jpg images might actually be webp, but to be sure u'd need to inspect them. The thing here I'm not sure of as it's not written, if I activate webp in TB and regenerate all images, are they converted? Or would they stay PNG if they were PNG already? That is kinda unclear 😉 But trying this right now and will update here when the thousands of images have been processed^^