musicmaster

Impossible. I am using the Mollie module.

I need to add additional data to my .htaccess file. I have a hosting provider who doesn't believe in php error logs and the only way to get a php error log is to add something to your .htaccess. The first line is "php_flag log_errors on". So I added the text at the beginning of my .htaccess - before the reserved part of Thirty Bees and I pressed the save button. At first sight everything seemed to work ok: in the refreshed page the added text was still there. But when I downloaded the renewed .htaccess file the added text was missing. And when in the backoffice I went to some random other page and then back to SEO&URL's the text was missing there too. NB: this is TB 1.4

Yesterday morning I found my shop down since about 3 o'clock in the morning. This is a shop on TB 1.4 (still waiting for the Mollie update). It turned out that the file /classes/PrestaShopAutoload.php had been reduced to length zero. I have no idea why. Anyway, I replaced the file and the shop worked again. This morning I once again found the shop down. It was the same problem and it had started at about the same time. Does anyone have an idea what could be the problem here?

Together with uploading the software also generates the derived images (123-small.jpg, 123-large.jpg, etc). This often takes more time than the uploading itself. So you should check which image types you have enabled. Maybe you can reduce their number.

I am using Enormail.

Found it! In the past I had first used the Eicaptcha module and then I had switched to the Thirty Bees module and disabled Eicaptcha. However, somehow the Eicaptcha override was still present. Now that it is removed things work again.

I noticed that my "Contact us" page doesn't work. You see for a short time the wheel turning and then the page turns back in what it was. I tried both in Chrome and Firefox with the same result. I did the mail test in the backoffice and that still works. I looked for error messages in the browser console but the only error is a " Fetch failed loading: POST "https://region1.google-analytics.com/g/collect?v=" (I have omitted all the arguments). This caused by the TB ganalytics module (latest version) but likely is not relevant for this case. I am using TB 1.7 Bleeding Edge.

Shopify makes its money with the modules. When you see the base price it seems not that expensive. But every module is another monthly expense.

https://www.prestashop.com/forums/topic/1104807-prestashop-has-a-new-owner-d/ PrestaShop has new ownership as of December 2025, acquired by Polish tech group Cyber_Folks (through its subsidiary Cyber_Pixel) along with Sylius and BitBag, forming a major European e-commerce ecosystem, moving from its previous owner, MBE Worldwide (now Fortidia). This acquisition combines PrestaShop's open-source platform with headless (Sylius) and custom solution (BitBag) tech, aiming to create a strong European alternative to global players, with Cyber_Folks holding a majority stake in the new structure.

A short time ago you wrote that you used the Prestashop module. It left me a bit puzzled as you mentioned version number 4.5.4. But when I checked the Mollie Github the 4.x versions (the last supporting PS 1.6) didn't go further than 4.4.3 from december 2021. What are your experiences with this version and why are looking for a TB version anyway?

The connections table can only store IPv4 ip addresses. All IPv6 addresses are stored as 0.0.0.0. Prestashop has the same problem. It looks like both assume that you are using Google Analytics or a similar third party service, so this piece of pre-historic code is left unchanged.

1.5.1 should work. 1.6.0 is not supported as far as I know.

I only now see this post. The post of 30knees didn't work. It would have been better when you had posted it in the Prestools thread. You can also email me. Prestools doesn't prompt you for a domain from which you search. You mention typing filenames. That puzzles me. As you have used it previously the address bar of your browser should have stored valid addresses. One possibility is that some kind of anti-virus software is blocking the software.

I get the impression that Prestashop is increasingly targeting big companies and is getting less interested in the small outfits. That could open an opportunity for Thirty Bees. Recently I encountered this article. It is about a Dutch company that makes themes and other parts for Magento, specifically targeting parts that Magento considers less attractive. It is kind of what to me seems a logical future for Thirty Bees. It wouldn't be hard to stay compatible with Prestashop regarding the business data of the database. That way you can offer a very easy migration between Prestashop and Thirty Bees - both ways. The business data changes very slow. Almost all the "innovation" at Prestashop concerns Symfony adaptations.

Here is the discussion on the Smarty Github: https://github.com/smarty-php/smarty/discussions/967