wakabayashi

Yes. That will be a huge issue soon. It's very hard for small forums/plattforms to manage that. I believe we will see more closed communities where access will be restricted in some ways.

Nope. I don't think Yabber does the work and then pays additionally for it. 😅

Yabber can probably fix it himself, but it won't make it into the core.

You are right. It doesn't seem to make sense anymore to invest time in fixing stuff on public. In the code you posted, there is even the doc block: /** * @param int $idProduct * * @return array * @throws PrestaShopDatabaseException * @throws PrestaShopException * @todo Remove existing module condition */ The Todo was added in late 2022. So the problem is actually known, but there was never time to fix it cleanly.

I don't use this module. So I can't much for it. But filter modules are often the crucial point for speed. If it occurs on product pages, that is very dubious. What does blocklayerd make on a product page?

You can scroll down and there should be something like "doubles". I guess this section could be helpful.

Ah yeah I agree. It's a bad design. But likely not a classical bug, where you just can fix a few lines. But as I said, it would be interesting to see, which queries/functions are called that often.

Well, is it then even a bug? It would also be interesting to see, which queries are loaded that often. I personally tend to avoid attributes.

We are not talking about the same things. AI is just a powerful tool. It can be used for the good or the bad. I would consider myself as using it for the "good". Think of it as electricity. How many shitty things wouldn't happen, if humans don't have electricity... But also how many good things wouldn't be there? You cannot judge revolutionary techniques simply as "good" or "bad". Btw: why are you even on X? Isn't that pretty much the definition of a shitty place? 🫣

@zen no, i won't switch to any other plattform. I know this setup and I think it's actually still pretty ok. You are right!! But my main developper is called codex not claude 😅

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.

Your way of seeing AI is very narrow. I envy people who can afford that.

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. 😅

I don't wanna spread bad moods or so. But imo the signals are pretty clear. There won't be any big developments of thirty bees soon. On social media they would chose a clickbait title: "It's over".

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

Bro you are not a normal thirtybees user, you are a module seller 🤷‍♂️

I don't know the regulation and I am not affected by it. But in general I agree with @Yabber how it should be handled. A clean/standardized process, that is triggred by a button. Afterwards I would check if the order involves multiple products. If yes, I would ask the customer, if he wants to cancel the whole order or only some products. A contact form might work as the oldfashioned solution, but imo it has only drawbacks (for merchant and customer). I would only disagree with @Yabber, that cancellation and refund are totally different things. From a coding perspective, they are pretty strongly related. In both processes you have questions like: Needs the current_state (order) be changed? Is there a money refund involved? Is the whole order involved or only some products? In both cases restock might be needed. So in short I would say, cancellation is a simple case of returns.

Sure, there are some risks. But buying random modules on prestashop store is actually risky as well. Or downloading code from github. Isn't it even more risky? In my case it would just be a waste of not using AI. I have become a decent coder recent years, but some AI solution wear cleaner than I would have written it 😊

I never worked with claude yet. It seems to be the best model. But right now I can use Codex 5.3 with no limits in phpstorm. I only pay the 20$ plan. Codex 5.3 is very strong as well. Maybe there are "political" reason to leave OpenAI but pricing and quality aren't an issue for me right now 😅

Its completly sick, what you already achieved without writting code your own 😅

@vincentdenkspel amazing! 😏 Don't forget: be careful. I would always recommend to work with testshops at least. Also try to learn some basics (in case you don't know anything right now). But in general this so cool. Keep going! @30knees This was my first guess too. But we might be wrong. It could actually be, that thirty bees is a winner of this. We have an open architecture here. It's accessible for all AI tools. And the system itself was built for extensions/moduls.

It's a very interesting discussion here. I can understand both positions. It's really a chicken-egg game. But imo there is a huge game changer: AI. It has become way more simple and fast to write code. I am also not aware of the plans/roadmap of TB. But with the new AI tools, it's even possible for no coders to start modifying some stuff. Ofc it's always better, if you have some basic coding knowledge, otherwise you might mess things up. Even if you aren't brave enough to use AI yourself: I would guess, that prices for a custom module will come down a lot. @datakick what is your experience with AI these days? I would say it has speed up my developing work about 3-5 times. It's hard to tell, but it's for sure huge. The first time I have the feeling, that my todo-list may become shorter 🫣

Wtf. If this statement is true... 😵 Probably they are afraid of lawsuit against them.

Is this all information they gave? No technical details?

It's long ago, that I asked for this. But a few days ago, I finally used this solution and it works as described by @datakick 😏