Jump to content
thirty bees forum

All Activity

This stream auto-updates

  1. Yesterday
  2. Last week
  3. Okay, I also think that's an exaggeration just because you haven't seen any activity for x weeks. A project like this isn't so short-lived that it needs an update every week. Many developments certainly require several weeks of work or even longer, especially if you're not doing ThirtyBees programming full-time. The internet and everything connected to it is fast-paced, that's clear. But the rule still applies: if you're in a hurry, go slowly. It's nice to get an update from Acer, even if it doesn't bring anything new.
  4. Since there had been absolutely no activity on GitHub for over six months, I assumed the project had been abandoned and stopped submitting pull requests, considering it a waste of time.
  5. Your drive for more founding is clearly visible in the 1.6 Version. Annoying is the least. How about a founding round and invite some active investors?
  6. 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.
  7. Sure I did understand, just there more than one channel. Who did you try to contact?
  8. I use option BCC when sending e-mail, so I can see what I'm sending. Of course this depend how heavy outgoing traffic is. I suggest for better result there is possibility to use shop logo when product picture is not available (what ever this reason may be) or at least this looks better for me.
  9. I have this issue also but i haven't noticed it until now, i simply forgot we are sending the images too.
  10. Hi Will try, because this may be the reason. But in this case I'm the only one who run this format ? I haven't seen that someone else is having this problem and I highly doubt that I'm only one using this module. Thank You
  11. 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
  12. I have this module. Somehow there is error. When client get this email there is only language relates flag picture instead of product picture. Can someone point me in correct direction to find out why is this ? I haven't changed anything in system. So I have no idea what can be the cause. Thank You
  13. 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.
  14. It is not dead, if you need something done you have several channels. Not everything needs to be handles by staff. What do you need? TB has one of the most helpful people in the forum. Developers read here too something other forums won't have. It is a self help shop system. It has hints in some of the files to explain what else is connected. Something I have not seen elsewhere. It runs on php8.3 and most likely on 8.4 too.
  15. This project is dead. Even if You are paying, there will be even no answer to email.
  16. Hi, I understand your concerns. Generally, I still see great potential in Thirtybees. It's just perhaps not being fully realized. It's also difficult to break into such an environment. Either you have good programmers or you have good salespeople. It seems you don't have both, or, as is so often the case, the team fails. But I also understand your concerns, and of course, Thirtybees currently carries a lot of baggage at its core. We know where it comes from... and yes, to lead it into the future, a thorough overhaul would be necessary. But please, no symfony-style strategy 😞
  17. Great notion +1 I guess there is little trust to accept more people, all needs to checked before going public. That is a clear sign that of bureaucracy is creeping in. When getting older we tend to find ways not to fall into action. How many people are candidates to become parts of the outer ring and how many are willing? @wakabayashi is a candidate.
  18. 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
  19. Earlier
  20. Error log is saying Once enabled the homeslider module delivered the header image
  21. 1 st part is correct it works with index.php annexed. And mod_rewrite is active on the server.
  22. @wakabayashi I would like to.... I wouldn't need to buy modules ;) but unfortunately no, you're wrong. I like to share good experiences when I have them and I've always had a great experience with PS... I don't think it's a crime to talk about them since they are excellent professionals... maybe they are your competitors, I don't know, if so I'm sorry, I apologize but I trust them and, I repeat, I don't think there's anything wrong with reporting good experiences.
  23. Bro you are not a normal thirtybees user, you are a module seller 🤷‍♂️
  24. So now you have domain.com/admin/index.php and domain.com/index.php - and this is working but with domain.com/ and domain.com/admin/ it is not working? Then you do not have mod_rewrite active on the server, and you can't use 'pretty URLs' or Friendly URL as it's known in BO.
  25. I added the name files name: index.php, into the URL, Sorry if I was that unclear. Anyway the greyed not found issue is still present. 1.5 and 1.6 are displaying a similar behavior.
  26. @Yabber Just look at the screenshots I posted to understand how the module I'm using works. The withdrawal function is so simple: just click the "orange button" in the order detail and confirm with a second click (red button in the confirm page). No form, no data entry, everything is automatic, exactly as required by the directive. I invite you to reread it again, perhaps with the assistance of one of the many feared German lawyers. Sorry to repeat myself, but in this post you're just continuing to create unnecessary confusion. P.S. I apologize for the quality of the images, but I'm not a graphic designer or a technician. I'm just a thirtybees user.
  27. You should always have index.php in every folder. This is not a fix. Something is breaking the installer. Did you have a running install on this setup before?
  28. I used now TB 1.5 and adding the index.php to the admin folders name did reveal the login page. With TB1.6 that did not work.
  1. Load more activity
×
×
  • Create New...