Leaderboard
Popular Content
Showing content with the highest reputation since 04/21/2026 in all areas
-
Hello everybody, TB is not dead .. it just smells funny, sorry that I couldn't resist. 😄 “Jazz isn't dead. It just smells funny.” ― Frank Zappa but it's up to us to make something different.. I have not much hope from the TEAM.. but from the community maybe things can go further. I still use and work with TB often, but now it's complicated to promote it to anybody because the lack of presence from the official communication. I still make many modules for some users, it's really fun to make modern modules with super cool looks on something that looks "dated", front and back end. Performances on TB are still the best ^^ php 8 does the job, no need for fancy framework. Best Regards to all of you guys !5 points
-
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.3 points
-
I have been here from the beginning. I can't remember any serious collaboration by the community. It were always individuals, that were investing some time here and there. There was once the idea of developping a new theme together. I failed very quickly. 90% - 95% of the improvements came from the core team. That's just a fact. It was Dekker, Traumflug and Datakick. Then there was Lesley and Smile who were more on the business side of the project. The core team isn't anymore active. That's why the project is likely to be dead. Who will fix major security issues in the future? Who will update to newer php versions? Who will handle github? There are 50 open PR. Who can update smarty? Who could fix the core updater if it breaks? These are the major questions. And the only decent answer in recent years was Datakick.3 points
-
2 points
-
2 points
-
OpenAI.. the company that is not ethical at all.. OK ^^ 😂 I banned them for all my usages.2 points
-
I use "Email Templates Manager" module: https://addons.prestashop.com/en/email-marketing-automation/25939-email-templates-manager.html To build email templates compatible with module, use Emails SDK: https://github.com/PrestaShopCorp/email-templates-sdk Like any Prestashop module, this one has a lot of bugs and needs to be fixed first. The screenshots show a sample email and the email configuration in the module.2 points
-
2 points
-
I found the cause of the product page crashing when there are a large number of attribute combinations and the “blocklayered” module is installed. In the Product class, within the two methods getAttributesInformationsByProduct() and getAttributesParams(), SQL queries have been added with the following condition: if (Module::isInstalled(‘blocklayered’) && Module::isEnabled(‘blocklayered’)) { And these are the ones generating such a huge number of SQL queries on the product page. Interestingly, after removing these SQL queries from the Product class, the navigation filter block on category pages works correctly 🙂 I would report this on GitHub, but there’s no point, because no one has been handling these issues for almost a year now.1 point
-
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 Emanuel1 point
-
"Transparency is one of the key foundations of every successful open source project. Without knowing the direction and priorities, it's hard to build trust and create a united ecosystem front." This statement was made on LinkedIn by the current owner of Prestashop/Sylius. I my opinion the lack of transparency, direction and priorities is exactly the problem with TB. Why spread the word of subscribe for a paid membership if one doesn't know what they support.1 point
-
Why I'm on X, to read several different opinions, and can adjust my own feed. Which is impossible to do in other "social networks". For some yes but for most no. I've seen people creating websites with AI, and no privacy rights, no details of who they are just the sales crap people push out. AI does not help if you don't know what to do. TB is also just a tool and it works, it is more dev friendly than most others. They are understaffed and remain so till they see the light.1 point
-
I don't know, how ecommerce is working in your niche and in your country. But here it's damn competitive. Not moving forward, means losing relevance. Automatization, Automatization, Automatization. Clean Proceses. AI Intgerations. If you don't need this, you are the luckiest ecommerce business owner on earth 😵 But I am a realist. I have to go my own way. It's ok. 😅1 point
-
Hi forum, I'm 'working' on a small module that swaps the default email templates with new custom ones that can be configured in BO - for v1 - only colors and email logo, more additions later. It also detects missing email templates during sending, so the merchant can later add them. The idea is to have granular per-shop control over the styling and the theme used. We would have the opportunity to have multiple themes and use them simultaneously for different shops. What current templates do you use? Are you stuck (as I am) to the default ones, or have you created/adapted the code to follow your FO design more closely? Can you add screenshots?1 point
-
You can get close by editing the product route in SEO settings, but the exact p/88-21 pattern usually needs a custom route override or a small module to handle that format.1 point
-
In that case, screenshots wouldn't be helpful. We have them as standard and have only really integrated the logo well. By "adjustments," I meant technical ones, like placeholders or modified uses for standard themes (such as notifications about partial deliveries). We use a third-party theme for the shop and the relatively clean standard emails are quite suitable for it (thankfully).1 point
-
Ok. I got it. This "0. Ignore this Column" is exactly what I need. Somehow I have forgotten all this. An there is even way to save what do You need. So there is no need to "play" every time what column You need to ignore. I use excel to make CSV. This way I can combine names because they vary, depends on functionality. And if there is 10 000+ items there's no way to edit all these by hand. Excel itself can't handle some specific symbols like Greek letters. So there are some formulas in on cell with 60+ variables. Also in my language there are letters that is best to give with CSV. And due to language peculiarity I need comma in description. So field separator is in my case semi-colon and for value separator I need to use this sign - &. Finally it is more confident to use Notepad2 where I can set encoding and line ending. I even don't dream that this is handy, but at least so far this all works for me. Anyway Big Thank You, if this is enough1 point
-
Hello thirtybees community, ours are: - https://www.duvalo.sk - https://www.hudobniny.net We rushed into production, so still tweaking some stuff.1 point
-
Thank you so much for your swift reply and suggested solution, @datakick! Much appreciated! The override worked like a charm! @DRMasterChief We didn’t try to do anything. It just happened from "one day to the next". I’m guessing we suddenly reached some kind of threshold. However, our store has been through a few facelifts. In some miraculous way, we’ve managed to upgrade from PS 1.4 all the way to TB 1.7, so who knows what kind of calls, requests and mysterious potions and bombs are being made. This is one of the reasons I mentioned the cleanup module as well. Would it be a wise move to run it, or is there little to gain here? And as a side question: Fiken is one of the most popular accounting apps in Norway for small businesses. I believe only WooCommerce and Shopify has a more or less seamless plugin/module for it. Could this be something for ThirtyBees - targeting the TB solution with a fiken module solution towards Norwegian customers? I know for a fact our accountant would love such a solution, so if you think this might be something, let us know, and we will chip in with fundings and other information you should need. All the best,1 point
-
Narrow? Why should I trust a software which spies on me and gives my 50% of lies (politely called hallucinations). That bubble is already bursting, you see that on the Twitter X shout outs of the known snake oil sellers.0 points