the.rampage.rado

Can vouch for this module. Full of everything you'll ever need to advertise on Facebook and even more. Support is excellent with module's author replying in under 24 working hours. Highly recommend!

I use the free version of Google Tag Manager Consent Mode Banner Free v1.1.2 - by Tag Conciergе. Works OK, with one language but has no option to translate in more in the free version. Works flawlessly with Google's privacy requirements (not only a banner).

You can play with the additional settings in PHPmailer but for me the default ones work as expected. I had similar issues (emails were rejected) because the from email (the one from Store contacts) was different from the user email I was sending from for one shop few years back. Since I synced those - no issues. Could your host IP be blocked by google for previous spam issues (previous user)? Could you check its reputation?

That's true @Daresh. It is awesome that you support thirty bees in the majority of your modules and the community is really grateful as they are unique work that really adds value to any thirty bees shop. It would be awesome if we can spread the word about thirty bees and the project positive sides locally. At every occasion I have I try to do so in Bulgaria. Regarding the additional hooks and core development that will come handy in your work - the community will be very thankful if you can support the project with code @ https://github.com/thirtybees/thirtybees that you find useful! Cheers!

Go to Preferences -> Store contacts and enter your outgoing email there.

This is how it's for me: - all cache files are 777 - all translation files folders are 755 - all cache folders are 755

I created a small free module that updates all search engines that support the IndexNow ping protocol. As you might know Google is still not fully supporting it but other engines as Microsoft Bing, Naver, Seznam.cz, Yandex, Yep do. And if those are important for your markets this module might help you. https://github.com/therampagerado/tbindexnow/ Any help in developing the module is welcomed if you find this idea useful. Best regards, Rado

If the website is not reliable could you edit your post and simply attach the module here for now?

Did you try pointing to them with https? You can test if this is the problem by putting the images temporary on the 'faulty' shop and importing from there. Of course don't forget to edit the URLs.

I'm importing with enabled option 'Skip thumbnails regeneration' is my server is shared and when a product has few images the process does not play nicely. And I don't see this error. Maybe try this and then regenerate your product thumbnails in Images. Hint here - when you import products that have no generated thumbnails the Images section will show that you have such products. Don't reset the indexation status and only click 'Regenerate products'. This will only work on the missing thumbnails not all products.

@led24ee wrong thread or? I'll split it if you made an error?

Hopefully your SERP rankings wont suffer from this.

What do you mean by 'disabled'?

Check if sitemap module is set to offer larger image than the small version.

Please tell me more, do you have the link?

The current combinations import mechanism lacks knowledge of those ids in the database.

I'm not sure I follow you but how would you attach the impact on a row if this row does not specify the combination?

Try using chatgpt to build you a python script that manipulates your csv and adds the weights based on your request. You'll have to be descriptive in your request and try couple of times until you achieve the proper result but in the end it will make you the script. You'll have to install python and after that run single file in order to output your corrected csv that you can import in thirty bees.

Did you set your carriers for every shop?

If you want to serve the images under different ip you will have to figure out automatic sync of the files. The approach i suggested is delivering cookieless images but only for the core - products, categories, etc. Modules will continue to be served from the main domain, thus you saw increase in points because core images were replaced with question mark image which is very small.

Media servers in thirty bees should not be used as you did - make new copy of your files and put it on another place on your file system. Not at least if you only use one server. Point your media domain to the same folder where the website is. That way the shop will request all product images from the media server which will look in your current img folder and find what it needs. Don't forget to clear your cache and regenerate your htaccess after you make changes to the media servers as information should be automatically written there.

In order to add webp and avif support find only the main module file and substitute it's whole code and you can do the same for list.tpl (those changes aim to fix the drag n drop reordering function of the slides). Refresh your BO and you should be able to add webp and avif to the slider if your core installation supports it (enable in BO and supported by your server). All other file changes are not relevant to your request. Bees blog also is one of those modules that needs work - it also does not support multilanguage and other things but it's quite more complicated. EDIT: If you notice any errors with my fixes please write here and I'll try to help (if I can 🙂 )!

@Raymond could you tell me if the reordering feature works for you in Home slider? I'm now adding the native core image extension support to the module. You can try those changes: https://github.com/thirtybees/homeslider/pull/14

Do you see this "id_product_attribute" in the possible keywords when you set up your structure? Because I don't see it. In what use case you need this there?

1. Remove the ImageMagick module - it is not compatible with the recently rewritten image system of thirty bees. Nobody should use this module since thirty bees 1.5 version as it gives no benefits in 2025. 2. Configure webp or avif in Images as you did before and again regenerate all image thumbnails. As you see in this section thirty bees core is responsible for the images for manufacturers, products, scenes, categories, etc. Not for the module images - slider, blog, etc modules have their inner way of handling those and sometimes they are not compatible with webp or avif. 3. The slider module should be modified to support webp and avif and the modification i fairly simple. Look at the code. Soon this will be fixed in the codebase but the developer is currently working on other more pressing issues. Keep in mind you should add prepared and properly sized images here as the module simply stores them and shows them to the FO, it does not do any processing. Cheers!