Leaderboard

Hi everyone, hello @datakick, @Smile and @Acer My premium membership just expired, which felt like the right moment to pause and reflect on the current state of the project. I’ve been here since day one and truly appreciate everything achieved over the years. thirty bees has been a solid foundation for a long time, but I am seriously concerned about its future. Official commits on GitHub have become rare; while community PRs are still coming in, they often seem to go unnoticed. There is a lack of transparent communication regarding the roadmap. This leads me to a point where I have to ask: Is it still worth building on the thirty bees core, or is the project effectively dead as an open-source endeavor? Technical Hurdles and Workarounds In my daily work, legacy issues in the core are slowing me down significantly. Address handling is cluttered, and features like multishipping (used by maybe 5% of merchants) make the code unnecessarily complex and bug-prone. A prime example is the "splitting order" issue that hits me every few months—a bug known in the PrestaShop community for 15 years. To keep the system extendable, I’ve developed a "best practice" over the last few months using classes like OrderDetailExtension or ProductExtension that share the ID key to manage new columns. It works, but it’s a lot of overhead that only makes sense if maintaining backward compatibility with the core actually provides long-term value. If the project is stagnating, it would be more efficient for me to drop compatibility and modify core files directly. Waiting for Features Over a year ago, I had an intensive talk with Petr about a credit system for customers. Since I need exactly that, I waited—but I’m still standing here without a solution. In recent weeks, I haven't been able to reach Petr at all. While there was a recent sign of life on GitHub, it’s not enough for professional planning. I would love to see a Version 2.0 that modernizes the system radically: A rigorous code rewrite (even if it breaks old modules). Support only for currently supported PHP versions and updates for components like Smarty. A Backoffice designed around merchant needs, not just a collection of controllers. Clean Code as AI Foundation: clean, unambiguous codebase is essential today. If the core is logically structured, any AI can easily generate high-quality modules. If the base is "spaghetti," the AI will only produce more spaghetti code. Conclusion Is this vision of a Version 2.0 shared by the team, and is it something being actively worked towards? If not, that is perfectly fine. But then I have reached the point where I will likely move in this direction alone and radically decouple my own codebase from the core. Best Regards Emanuel

Hi @led24ee @led24ee No, the project is not dead. And Petr is still around - he's just working on things that are not currently committed to GitHub, but will be in the future. Yes, we only have 1 core developer, and the concerns you have, imo, are valid - which is something we've been wanting to change for a long while. We've been trying to drive "support Thirtybees" campaigns, so we can boost funds and hire more developers and hire some of us full time. Which will result in a massive injection of energy and improvements and new life for ThirtyBees. Unfortunately, it's been a bit of a struggle as I'm sure you've seen with our reminder posts or mentions on the topic from time to time. Chicken and egg scenario, and that is the truth. That being said, there is movement albeit slow, and there are plans, and eventually (hopefully soon), you will see more movement and obvious progress. But yes, more support will be beneficial for ThirtyBees. Don't give up on us yet - see what you can do to help, and hopefully we can all see an improvement soon. Thank you You can DM me directly if you need an email answered - I will share Smile's email address.

I checked the code, and revws module only supports jpg files. Which was ok in the past, but now when you can have your product images in webp or other formats, it can cause troubles. If your store uses webp images, edit file modules/revws/controllers/front/EmailAction.php and change lines private function getImage(RevwsEmail $email) { $email->markOpened(); $imageId = (int)$this->getValueOrThrow('image-id'); $type = $this->getImageType(); $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . $type . ".jpg"; if (!file_exists($file)) { $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . ".jpg"; } to private function getImage(RevwsEmail $email) { $email->markOpened(); $imageId = (int)$this->getValueOrThrow('image-id'); $type = $this->getImageType(); $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . $type . ".webp"; if (!file_exists($file)) { $file = _PS_PROD_IMG_DIR_ . Image::getImgFolderStatic($imageId) . $imageId . ".webp"; } I will fix this in next version of module

Maybe You don't understand this. I pay for this. They can at least answer. Even negative answer is better than nothing. But now some ... is saying that go look for some other ways. I spend about 3 month last year to try to BUY some extra things. They answered once a week. I offered extra payment but they couldn't understand or maybe they had already too much money. Result was zero. Now after about half a year later I renew my subscription. And now they even wouldn't answer. I wouldn't be moaning if I was some random jerk in forum. So yes this project is dead. Maybe there will be resurrection, but I doubt. I have no idea how long this current version will run. github shows almost zero activity.

This project is dead. Even if You are paying, there will be even no answer to email.