Leaderboard

Hi all We understand that a lot of us have been wondering what has been going on and if Thirty Bees will continue. Everyone being quiet hasn't been helping, we know. Please see this post as assurance that we're on it 👍 We can't divulge much at the moment but suffice to say there is currently something in the works. We had hoped to say something to you all sooner. Unfortunately the negotiations has been taking a lot longer than initially expected. However, we feel pretty close and hope to have a proper announcement soon. One of the Core developers is involved so that should be reassuring. Can't say who just yet though. Either way, you'll be happy. For now, keep your fingers crossed, and please continue your contributions in the forum and keep using Thirty Bees. Also, please show your support by liking this post. There is a bright future for TB and we'd love to see your continued involvement, support and participation. More soon. Watch this space!

Hello everybody and happy new year. I spent a lovely Christmas / end of the year with my family, without access to internet, computers, and so on. I feel fully charged and ready for this new challenge. So let's do this. I must confess that I was a little dishearthed with the cold response to the announcement. While I understand you guys don't really care if this project continues under the same name, it's a big deal to us. Fork would be a very different starting point. It's very nice to have hundreds of active websites using our platform already. And it's amazing to inherit existing thirtybees infrastructure (forum, websites, demo, api servers, mail servers, translations, deployment, testing). If we were to start from scratch, it would take us a year to get to this point. The effort to achieve this would be huge, and nobody would really benefit from that. Especially not you, merchants. After a lot of mundane work we would end up at the very same spot we are now. If we weren't able to close a deal, I'm not sure if we would even try to do this. So yeah, we were really excited about it. But I am fully aware that you don't really care about all of this. You expect roadmap, business plan, etc... and it's a fair point. So let me talk a bit about this. Monetizing strategy: Our team have talked a lot about different ways to earn money that are needed to keep this project afloat. Realistically there is only a handful of them that we can pulled off, considering our limited resources. For example, we have dismissed the idea of providing SAAS or PAAS service. In the first few months, the majority of revenues will come from the support services that we will provide to merchants. This means that portion of my development time will be allocated to paid support. We believe that this is the best way to bring in some money right away. Also, the existence and availability of official support will surely make platform more attractive to undecided merchants. Support services revenue model does not scale well, though. There is only finite amount of time we can provide. Even though we want to bring other developers aboard, the time will still be a limiting factor. We are fully aware of this and we have few other plans for a long run. Development: First of all, I want you to know that I will devote 100% of my time to this project, starting February. Currently I'm finishing my current development contract, and closing my existing activities (for example support service I provide via datakick agency). That means that this month I will work on thirtybees only part time. But come February you will start to see some real progress. As I wrote above, part of my time will be dedicated to support, something between 30% and 40%. The rest of my time will be dedicated to github maintenance - I will scrub and address each and every issue, pull requests, doing code review, etc. bugfixing - issues will be categorised by severity, and some of them will be fixed. Not all - that's just not possible. I expect to spend 15% of time on this. That should be good enough to fix around 40 serious issues per release. new feature work - for every release we will select (with your help) some new features, and we will commit to implement them. I expect to spend around 25% of my time on this area. If you have some ideas what you would like to see in the core, or idea for new module, let us know (unless it's multiple feature value, I've heard that one 100 times 🙂 platform enhancements - the rest of my capacity will be dedicated to platform enhancements. These are development tasks that you, as merchants, will not immediately benefit from. But they just need to be implemented. Some of these tasks will not be very popular, I'm sure. For example, I want to implement some tracking in order to have good knowledge about system usage. Such information will allows us to focus our efforts on areas that are heavily used. (But don't worry, we will be very correct. No data without your consent will be sent to us). Other tasks from this area will be more appreciated, such as php 8 support. Or tool to create custom field for product or customers, or to edit properties of existing fields. Release cycle: Our main focus always was, and will continue to be, on stability. Based on our experience we strongly believe that merchants don't really want, or need, too many releases. So we decided to have just two major releases per year. Other than that, we will have monthly bugfix releases, that will contain high severity bugs only. There will also be bleeding edge release that will always point to the latest development (just for brave). Bleeding edge is de facto Release Candidate. All of these releases will be available for download, and of course via core updater. The first official release will be prepared in a few days. It will be branched from current bleeding edge. Partnerships: For thirtybees to succeed we need to have thriving ecosystem. That means both merchants and third party developers. We have quite a lot merchants using our system already, which is a good news. Unfortunately the situation with module and theme developers is more worrying. Sad fact is that there aren't many developers that support our platform at the moment. And we need to change that. We have a plan to actively outreach to them, offer our help with adapting their modules and themes, make it easier for them to become part of our platform. If you know about some module you would like to see adopted, PM me details!

I'm very happy to announce that we have officially released thirtybees version 1.2.0. This version consists of a lot of enhancements and bug fixes that were implemented in the last (almost) 2 years, including stuff like: PHP 7.4 compatibility - this version is fully compatible with PHP 7.4 Object model audit - database and php model are now in sync. This fixes a lot of weird issues and problems Ability to auto migrate database during update - missing database tables and columns are automatically created by core updater Installation fixes - a lot of bugs were fixed in installation process. Installation should now run more smoother Bug fixes - many issues were solved and more... You can simply use core updater module to update to latest stable release. Or you can download installation package and install it on your test server. I will deploy this version to the official demo servers in upcoming days, so you will have an opportunity to test this version even without the need for installation.

Hi everyone We know it's now been a while since our first post. While we'd love to have new news to share, we're still waiting for some important documents to continue the negotiations. Someone here mentioned that buying a company can sometimes take months. Unfortunately we're seeing that this may be the case here too. We are eager to pick up the reigns and move TB forward, but will have to ask you all for your continued patience while we sort out all the details of purchasing TB. We're picking up that it could still take many weeks before this thing has been finalised. On the plus side, we do have some info to share: The Core Developer has essentially been finalised and has indicated that he is on board (subject to the sale of TB being concluded and other details, of course). We will reveal who, once everything is sorted. He will be full-time. And you will be more than happy 😉 We plan to move TB forward with continued maintenance and improvements and evolution. Making TB better, by building on its solid foundation and listening to the community. Not ripping it up and starting again. So no plans to change architecture or any crazy Prestashop 1.7 or Symfony ideas. There will be roadmaps, bug fixes, new features, enhancements, support and massive community involvement, feedback and participation. We look forward to finalising the negotiations and purchase of TB. We will provide feedback within the next few months. Hopefully sooner. In the meantime, please keep using and promoting TB. We promise an exciting future for TB ahead. Thanks for all your support 👍

Oh yeah 😵 Actually how many merchants are still here and do care for this project? Please like my post, if you do. A few months ago, I asked in another forum topic, who would be willing, to invest 50$/month or more. Then the following poeple where in: @wakabayashi @Briljander @rubben1985 @Smile @vincentdenkspel @dynambee Are there any others right now? I am still evaluating the options for serious/established merchants...

Yes, I'm part of the group that would like to take over thirtybees. Currently we are trying to buy the rights -- not the thirty dev llc company, as we are not US based. Negotiations took a long time now. Every time we get close to the deal something else pop up. Important thing is that we are committed to this. Although we prefer continuation of thirtybees for various reasons, we are prepared to fork and proceed under the new brand if the deal is not reached soon.

The reason for the delay was caused only by me only, and I apologise for it. The plan was for me to start working on thirtybees full time at the beginning of February. I used to work as an independent contractor for a big client in a bank industry, and I was contractually bound to deliver a lot of work for them. Since the team didn't meet the delivery timeline I was forced to work for them until the end of February. I officially ended that contract last Friday. So, finally, I'm free and able to work on this project 100%. Right now I'm working on initial release, it will be done by the end of this week, probably Thursday or Friday. And then there is a very big backlog of things waiting to be done.

Hello everybody Tired of waiting? You're certainly not alone. We read about hold backs after hold backs for months now, without any substance backing anything up. Even this latest post yesterday asks for yet another two months of waiting. No new code, but new paid plans, apparently giving up free forum support. One could even read it as if they're playing with the idea of going closed source. Seeing this, I could no longer hold back myself and did what thirty bees should have done a year ago already: I made a release from what's there. That's more than 400 bug fixing commits since the last release, certainly not too shabby. So say hello to Merchant's Edition 1.9.0 Technically it's a thirty bees release with a renamed installer package. It'll install as thirty bees 1.1.1. Merchants with an existing shop simply upgrade to the latest Bleeding Edge 1.1.x, that's the same. And remember: 1.1.x as of half a year ago isn't the same as 1.1.x of today. What's the plan? Well, there is no shortage of ideas, including: Rebranding, own translations & update server (obviously). A Core Updater supporting both Merchant's Edition and thirty bees, allowing to switch easily between them. Committing the dozens of bug fixes I already have on my plate. Support for PHP 8.0. Speed improvements. Simplifying back office without giving up the feature richness. There are so many 'features' which barely make sense, just confusing merchants and slowing down operations. Tidying it up will improve the back office experience tremendously. A patch system for third party modules. We all know there are many modules out there which leave room for improvement. Their authors are too lazy to update them, Merchant's Edition is not. A usable version of the freaking freaky full page cache. Ever tried to configure it for best performance? It's currently a mess, and can be done much, much better. Regular releases, like once a month. Of course! About Merchant's Edition: there's a working business model in place already. No need to beg for money. Merchant's Edition may come up with things like Crowdfunding for larger improvements. From my own experience, merchants will happily pay if they get a substantial reward for their money, like fixed bugs and working code. Let me take this opportunity to thank those who did so far, it has been much appreciated!

I have hope that TB will Rise again, you can count on me for helping when you guys will be ready to work while having clear roadmap. My first contribution : ElasticSearch module finished at around 98% ( it just needs to be checked and fix small back office glitches, and translatations updates), works with last version of elasticsearch, and index products with multifeatures as well as colors attributes and show them ordered default by interest) My second contribution : I want to make a simple theme for TB and a module that can customize it easily, making the use of all different configuration/cutomisation modules not necessary anymore, all in one place should be less confusing and strait to the point. I already make a theme custom module for Niara but coulnd't finish it due to no time enough and TB internals managing problems as we know them, also I make a slider module that use vegas show script in full screen mode and/or background mode. My third contribution : Cleaning module should be up to date, including images clean, and products variations clean, as when you delete a variation many things are not deleted in the DB as it should.

We are happy to present to you the latest version of Thirty Bees - 1.4. The main advantage of this version is the full support of PHP 8.0 and 8.1 If you need help with upgrading your store, feel free to contact us. It saves you work and you will support Thirty Bees with it. Many merchants preceded you already! Please note that PHP 5.6 is not supported anymore, so please upgrade in time to avoid downtime of your store. Beside that we have done many bigger and small improvements. Some enhancements in the webservice as well as tracking packs sold (its parts), some enhancement in Features and some bug fixing. Please find them all in the change log or under this email. Furthermore I would like to tell you a bit about what we have also been busy with. We have been working on quite some modules what should make your work more efficient in the future. Those modules will be slowly released in the upcoming months. 1) Advanced error monitoring, which makes it easy to monitor in depth errors in your system. 2) A Full scale Warehouse Management System module, which will make picking and packing very easy. Fully integrated with all functions you need in an ecommerce warehouse. It will be perfect for anyone that has multiple people working in the warehouse. It will save you a lot of time, mistakes and will save you money from day one. If you are interested, please drop us an email to discuss your implementation. 3) Native Thirty Bees Mollie payment provider module 4) Advanced Support Ticketing system with optional communication channels like WhatsApp, telegram, email, etc. 5) FAQ Snippets: With this module you can easily add FAQ lists to product and category pages. Search engines can show this information in their result page as it has the snippets markup. By adding links to the text you can attract more people to you store and increase sales. Must have for every ecommerce site! 6) List flow module: Allows you to create dynamic lists of products. Products can be automatically added or removed from the lists when they meet some criteria. For example when text changes. This can be used to add provide list of products that require attention to your translator, photographer or marketeer. This is very powerful module, but the initial settings can be overwhelming. You might want some support for setting it up. Must have for every ecommerce store with lots of products, translations, domains, and employees! 7) History logging: This module logs most changes on product level and who did make the change. Some examples are price changes, text changes, meta data changes and much more. Must have for tracking changes on product level by different employees. And don’t forget thirty bees is an open source platform, maintained and kept alive by Merchants and enthusiastic developers. Any donation you make will be much appreciated and will 100% be used for the development of thirty bees. Buy us a beer or become a backer and show us thirty bees has a value for you. Added PHP8 compatibility Removed PHP5.6 support WebService enhancements · logging · error reporting · employee context Carrier enhancements · translatable carrier name · ability to disable some carrier ranges Enhanced error reporting · ability to attach custom loggers · replaced die statements with exception, so the root cause can be logged · don't hide SQL exception by default Packs enhancements · dynamic pack feature · do not show hidden pack items · track pack items sold Features enhancements · improved feature values editation directly from product page · product filtering by features in admin list Extendable back office notifications · it is now possible to have custom notifications icons in back office page, for example for new reviews Fixed a lot of bugs. Most important one: · Fixed image type resolving · Autoloader case sensitivity issue · updating product positions withing category · dashboard: date range automatic recalculation · delete category: orphaned products · product thumbnail name conflict · numbers input audit · mobile theme detection · uploading attachement filesize issue Other enhancements · some category fields like active were made multistore-aware · ability to edit specific prices · custom code - multistore support · combination generation: unique reference · import: introduced custom data sources · Smrty MySQL Cache encryption -- security must have · reviewed debug mode · product: enable shop association · products: simplified multistore editation · customer service: new settings controller · support search with spelling errors · file manager support for webp format · csv export customizable field delimiter

I think you guys deserve to have a better visibility into how thirty bees development is going forward. So I decided to write bi-weekly sprint overview. Let me start by explaining how we do development at thirty bees. We use scrum methodology, with 2 week sprints. In agile development, sprint is (usually) 2-week period of time when development team implements and delivers some functionality that has been agreed upon. Although we have a very small team (some naysayer would say it's not a team at all 🙂 ), we decided to practice this agile process for various reasons. One of them is to be more accountable and focused. Another is to have better understanding of how much work we can really deliver. Before every sprint, we have an internal scrum meeting where we decide on what will be implemented in the next 2 weeks. We have a huge backlog of items that can be done, with effort estimate. We also have a roadmap. We know when the next major version is going to be released, and what functionality it should/must contain (I will write a dedicated forum post about this soon for those interested). We use these information to select tasks for the sprint. We try to put tasks from different areas into to each sprint. The result contains tasks from these categories bug fixing -- we dedicate some time to fix bugs, maintain github, PR, etc enhancements that bring value to merchants -- these are standard enhancement requests, like multiple feature values or order editing platform enhancements -- these are enhancement that you guys don't know you need, but you will love them 🙂 Also tasks that will make platform more friendly and interesting to third party developers, theme developers, etc. chores -- everyone hates doing chores (I know I do). But they need to be done. Tasks like server updates, implementing testing pipelines, support for php8, and what not. The platform would implode without regular maintenance. enhancements that bring value mostly to thirtybees org (us) -- we are adding some functionality to the core / modules that will make us happy. For example, we plan to add usage tracking (how many people installed tb, what features are they using, what errors did they encounter, etc). I understand that merchants don't care much about these (and some will not want to share these info with us), but we need to know. Otherwise tb company will fail, and tb platform will go with it support and paid tasks - time dedicated for paid support. Merchants can contact us and ask for some custom development, server migration, updates, etc. Currently our only stream of revenue. OK, that's probably enough introduction. Let me present to you what we have done so far Sprint 1 01/3/2021 - 16/3/2021 The first development sprint started when I finally joined thirty bees org full time at the beginning of this month. The goal of the sprint was to start progress, and to release first version. What we did: Translation handling - release prerequisites temporarily remove php8-polyfill dependency -- tb failed on php 7.2 and newer because of it Tool to extract translations - automated script that extracts translatable strings from core, themes, and modules Tool to upload translations - script that uploads extracted translatable strings to crowdin, where you guys can translate them Tool to download translations - script that downloads translations from crowin and prepares translation packs Tasks associated with releasing new version Build and release all modules Build and release core Prepare translations Release notes Deploy to demo server Multiple php builds Extending thirty bees build machinery to support building thirty bees for different php versions. We still support php 5.6, but this makes it very hard (nearly impossible) to maintain. It's because many php libraries that tb depends on are not supported on this php version, there can be composer dependencies conflicts, etc. Extend core updater to request specific php version -- work in progress Bug fixing in first sprint we dedicated 1 day to github maintenance, fixing some bugs, merging some PR, and general backlog cleanup Support paid support requests Sprint 2 [current] 2021/03/17 - 2021/03/30 Plan: Core updater enhancements Make core updater user friendly -- core updater was made by developers for developers, that's not good support update to php version build refactoring code to make it less dependent on tb core -- we plan to use the same module as a migration tool from ps16 various enhancements, like tracking specific revision Carrier price semantics enhancement that allows merchant to enter shipping price with or without tax this also fixes AEUC proportional issues Scheduled tasks thirty bees will have build-in scheduler (cronjobs) to run scheduled tasks we need this as a stepping stone to implement additional features, like maintanance tasks, automatic backups, automatic index regeneration, updates, tracking, etc ElasticSearch this module was originally implemented using crowdfunding, it was a shame it didn't work. We fixed that review and extend existing PR requests for ES module, make it work with all supported elastic search versions fixed various bugs PHP8 support ongoing effort to make tb compatible with php8 in this sprint we renamed Attribute class, and all its usages in core. This is work in progress, not in main branch, not yet available for general audience Support paid support tasks in this case, the result will make it to the core, as feature custom Permissions for back office controllers -- you will have an option to hide some tabs in Product back office edit page. For example, you can restrict translators employees to see and edit only Information and Seo tabs. Then won't be able to break your pricing Work queue Work started on work queue feature This is a mechanism that allow us to run some tasks in parallel / in separation from main execution thread this will allow us to improve performance and to implement reliable long running tasks example use cases sending emails -- instead of sending email immediately/synchronously, we will create email task and push it to work queue. It will be send shortly by work queue worker. But it will not block main thread -- the server response will be much faster. Also, this allows for re-trying sending emails on error Bug fixing - Sprint 2 How is it going so far: We are little bit behind the plan -- to implement Core Updater enhancement took much more time than originally estimated. However, we are almost on track. For those of you interested in burndown chart: Sprint 2 will end today, and new Sprint 3 will start tomorrow morning. We have a sprint planning meeting today where we will finalise and agree on scope for the next sprint. I will create new forum thread containing plan for sprint 3 this evening, or tomorrow. If you guys have any questions, don't hesitate to ask 🙂 Have a nice day all

Hi guys, I'm a merchant from Poland, running TB from the first versions. I'm also an IT pro with an additional developer on board. I'm planning to use our experience into a small e-commerce business this year, and I'm thinking about supporting TB in some way, as it's been good for us :) We can help with some dev, infrastructure, maybe some marketing. Shoot me with a PM if there's any way I can be of an assistance. All the best! Daniel

Hi all We understand the frustration and uncertainty about the future of TB that is being felt here due to no news and constant delays. The delays are caused by having to resolve the issue with the partner and this is holding up the contract being finalised. If it was up to us it would have been sorted out long ago... However, we've decided that we and you cannot wait forever. We are committed to making Thirtybees succeed and evolve for the future. We have a great team and one of the Core developers, @datakick on board. And with you support, we know we can succeed. Because of this, we've decided that if the contract is not signed by end December we will fork. Either way, Thirtybees will succeed and continue in the future in one form or another. You will not be left hanging. We have you covered and backed by the Core developer on our team, you can be rest assured that we will deliver, whatever happens. Your and our stores will continue to be supported and TB will evolve for the future. We know it's a hard ask and we're impatient too. But if we can ask for just a little more patience please...

Perhaps you were waiting just as long as me, now it's done: thirty bees v1.1.0 (ZIP package) Packed with hundreds of bug fixes, awesome new default theme, two new modules. Release notes: Core Updater is now the tool to update thirty bees core. A lot faster, a substantially more reliable update strategy. It can update all versions beginning with thirty bees 1.0.1. And it can downgrade / roll back just as easily in case a new release doesn't work for your shop. Module tbupdater should be kept installed, it's needed for updating modules for the time being. Big refactoring of error reporting and exception handling by @getdatakick. A new exception page and more important for merchants: reports no longer go into the rendered shop page, but get reported in the JavaScript console. PHP errors messing up shop pages are a thing of the past. Another big audit of price rounding. Prices in the cart get now rounded properly according to the configured rounding strategy (by item / by line / by total). And invoices, credit slips, all now do as well. This audit also brought a lot of detail improvements in displayed prices. For details, see https://thirtybees.com/blog/prices-done-right/. In multishop environments, one no longer sees duplicate entries for currencies. Editing translations no longer requires to raise the max_vars PHP setting. Thanks to @ziyaindia. When checking for module updates, not only the module name, but also the module author has to match. This should solve a class of issues with thirty party modules named like official modules. It also means that one can exclude a (edited) module from updates by simply changing the module author, e.g. from $this->author = 'thirty bees' to $this->author = 'thirty bees tweaked'. Coupons/vouchers with taxes get now taken into account as well, thanks to @Zengraph. With multishop, lists of customer groups now list only groups available in the currently selected shop context, thanks to @chitmann. Also thank you to Emanuel Schiendorfer, David Gasperoni, Mark, Yaniv Mirel and Geo for their contributions. Much appreciated! There is a new section in the statistics module: Stats by Groups. Written and contributed by @Zengraph. Considerable chunks of theme installation were re-written. It should work now simpler and no longer mess with back office modules. This added support for different image sizes in distinct themes. Developers would call this a per-theme namespace for image types. Theme configuration XMLs in config/xml/themes/ disappeared. As they never got edited, they were always identical to config.xml in the theme folder. This also removed config/xml/themes/default.xml, which was used for community-theme-default, so no more surprises when installing a shop and re-installing the default theme. Initial theme settings in the installer were aligned with those of the actual default theme. Before, (re-)installing the default theme later had quite distinct results from what one had right after installation. Theme metas (where one turns left and right columns on and off on particular pages) now allow to configure not only pages known by the theme, but all pages available. CSV import now supports custom date formats in CSV data. This should allow e.g. U.S. merchants to import CSV data from a European manufacturer. Thanks to @ksimunovic! A new, awesome looking default theme, Niara. Previous theme is still there. Now one can switch back and forth between both themes coming with thirty bees. Support for the "back" step with third party themes is forthcoming, one can still install them, of course. Module beesblog is now a default module. Two new modules, thememanager and tbhtmlblock. Already in use by theme Niara, they get disabled when installing theme community-theme-default. Modules & Themes Catalog can now actually list modules and themes. Notes to developers: Price rounding audit contained the following steps: Get the cart into rounding properly. When creating an order, take these rounded prices from the cart unchanged. This ensures all downstream calculations use these rounded values rather than the current product price. This also allowed to remove duplicated rounding in classes like HTMLTemplateInvoice or HTMLTemplateOrderSlip. As a metaphor, consider rounding to be like a discount: price in the order is what the shop customer saw, not what the merchant started with. Reviewed all classes dealing with prices to always round to database precision. As if PHP couldn't do better. For strategies, see Dealing with Prices at Traumflug's. Replaced a whole lot of (hopefully all) hardcoded rounding precision values with constant _TB_PRICE_DATABASE_PRECISION_ or Configuration::get('PS_PRICE_DISPLAY_PRECISION') as appropriate. Controllers rendering option fields ($this->fields_options[]) containing prices should use field type 'price', validation 'isPrice' and, new, a cast 'priceval'. The latter converts to a float, then rounds to database precision. AdminController was changed to apply the cast for option fields ($this->fields_options[]) before validation, not after. This allows to implement a cast which shapes the value (like priceval() does). There is a new field type for a class' storage field, type TYPE_PRICE. It's a float like TYPE_FLOAT, but also rounds the value to database precision, to get precisely predictable price and tax calculations. Started to remove outdated code. Retrocompatibility code for PS 1.4 and before or PHP 5.5 and before. Removed AdminRangePriceController and AdminRangeWeightController. Introduced in 2011, they were never available in back office. Classes RangePrice and RangeWeight are kept, of course. Themes now support only one variation. Not sure whether multiple variations every worked before, code had quite a number of discrepancies. Attempting to install a theme with multiple variations now reports an error. To get the path of the config file of a theme before and after 1.1.0, use Theme::getConfigFilePath(). Image type names are now enforced to contain the theme name. Recommended standard is to let the system do this, it prefixes the theme name. For getting links to product images, use Link->getImageLink(), for getting product image sizes, use Smarty getWidthSize and getHeightSize, see e.g. in _productlist-item.tpl in both thirty bees themes. For getting just the appropriate type, use ImageType::getFormatedName(). Other variations are allowed as well, see ImageType::getFormatedName(). And yes, fallbacks for hardcoded image types were implemented. They come with a small performance penalty, though. To see how to fix a theme with hardcoded image types, see commits like https://github.com/thirtybees/niara/commit/1047053d4829ecaf7e5bbdbad891bba286863b07 or https://github.com/thirtybees/niara/commit/7f682df10940170593bbe6d21ea99dd74ebe77ae. There are a whole lot of new hooks, see New Hooks in 1.1.x in our forum. And yes, we're aware this has taken waaay to long. thirty bees should release more often. This release also appears in Core Updater in you back office.

Hello all, I am curently working on a Bootstrap 5 theme for Thirtybees and would like to share it with the community at least for the basic version. I need your help in order to finish it, while completing this task I'd like that you can report here the good and the bad things about the theme, so i can fix it or improve it and ask for new testing before I put it on github and manage it on that platform, as it's way more easy for me to do it here for start. And here is the admin back office that can let you use the ThemeMaster module, that will help you to customize your own design, it's very first version and don't hesitate to ask for things to manage from this module : https://cisero.zengraph.com/admin007/ user: [email protected] pass: demodemo So let's start it, I hope to finish it before january 2022, it also depends on your returns. Here is the ARCHIVE to download on a zip format, please report bugs and improvement ! Also here is the GITHUB link : https://github.com/Zengraph/cisero Cisero_theme_TB.zip

These recent irritations around the project currently named thirty bees accelerated my efforts to come up with a solid and reliable ground to connect developers with merchants and merchants with developers. Code written and features of the software were and are great, many merchants do their best to help others, just as many developers. This deserves a liberation from business and investor games. Say hello to Merchant's Edition Merchant's Edition has the goal to move the idea of open source into the business area. It's open to any developer working on the core software and basic modules. Their share grows not by the amount of money they provide, but by the work they put in. They can connect directly to merchants and vice versa. Merchant's Edition helps to connect them together. Next step: provide a chat for both. Those knowing me also know I prefer to do things right over rushing into something 80%. Look at how blazing fast the already provided site is. During development I learned a lot on how to make web pages faster, much of which can eventually be applied to shops running thirty bees as well. Published now already, to show that things around thirty bees are moving forward. Chat is then expected to be the same: fast and secure. Probably based on Matrix and Riot. You as a shop operator can get support right now. These nagging warnings all the time? We'll fix them. Need an extra feature? We'll write it. No time for technical maintenance and updates? We'll do it. Done by those who know the software best, from the ground up.

Today, we are thrilled to introduce the latest version of Thirty Bees: Version 1.6. This update wouldn’t have been possible without the support of our dedicated members. Thank you for being part of our journey! And to those who contributed code—your work is invaluable, and we extend our heartfelt thanks. If you’re not yet a member, consider joining us. Your support, whether through a small donation or by becoming a monthly member, makes a real difference. For just $15 a month with our Silver Membership, you gain access to an array of powerful modules designed to save you time and streamline your workflow. What’s New in Version 1.6? This release introduces numerous core updates and security improvements, some of which are highlighted below: ImageRewrite with AVIF Support: You can now use the AVIF format for images, optimizing quality and load speed. Enhanced Email Subject Control: Customize the email subjects sent during order status changes for better customer communication. Additional Category Description Field: We've added an extra text field in category descriptions for improved flexibility. New Modules: Two new modules are part of this release. One is free for everyone, allowing you to filter specific email domains in the contact form to reduce spam. The other, part of our Premium module pack, limits email-sending attempts from individual IPs, helping to prevent spam attacks. For just $15 a month, the premium pack includes this and other powerful tools to boost your efficiency. You can find all premium modules in the backoffice of your store! Love Thirty Bees, Please Support Us: For non-members, we have introduced a campaign to support Thirty Bees’ ongoing development. After a period, you’ll see a pop-up asking if you’d like to join us as a member or make a donation to support our work. Don’t worry; this pop-up won’t reappear for another two months, so it remains far from intrusive. Paying members, however, will not see this pop-up at all. How can you Support / Help Thirty Bees? We all love Thirty Bees and it has made many businesses thrive and be successful. The truth is that we’ve come a long way together, but there’s still so much more we can achieve. To continue growing, we need your help. We’re looking to expand our team, improve our platform, and spread the word about ThirtyBees to new users and developers. But we can’t do it alone. This is where our community comes in. How You Can Help: Leave a Review on TrustPilot: If ThirtyBees has helped your business, we’d love for you to share your experience. Positive reviews on TrustPilot not only help us reach more people but also build trust within the community. Support Us with a Donation or become a Supporter: Your contributions will directly help us bring more developers on board, enhance the platform, and support our growing user base. Every little bit counts, and it all goes back into making ThirtyBees even better. Spread the Word: Tell your friends, colleagues, and fellow entrepreneurs about ThirtyBees. Your endorsement is the most powerful tool we have to grow our community. Continue to Engage with Us and other Users in the Forum: Share your ideas and feedback, continue to help others like you always have. ThirtyBees thrives on the input and energy of our community. We love and appreciate that you are here! You are what makes ThirtyBees great! We believe in the potential of ThirtyBees and the strength of the community behind it. Together, we can continue to build something amazing—an eCommerce platform that truly serves its users and grows with them. Thank you for being a part of our journey. Your support means the world to us. Happy selling! Petr, Theo & Chiel Image rewrite generic mechanism to define and generate image types for any entity (categogry, products, blog posts,...) unified support for all image formats for all entities avif format chores updated librarires Remove dependency on Jaybizzle\CrawlerDetect, replaced by tbdetectcrawler module donate campaign small enhancements Product supplier: new columns name and comment Order Statuses: support for custom email subject Display calculated weight for pack products Category: new field Additional Description Hreflang: ability to override hreflang mappings Support shortcodes in order messages in backoffice Buttons to delete empty/old carts Automatic deletion of old css, js, and log files. Configurable retention Add button to close threads older than 30 days Expose CMS Categories to webservice New hook - displayAdminCartFooter hook Improve search indexation logic Contact form: support custom validation (two new premium modules - ban ip address, filter messages by content) Save maintainance IP addresses globally Import combination: mechanism to delete only combinations for products referenfed in CSV files Pass {invoice_number} placeholders to order status email templates Better Linux and Windows compatibility Information page: use asynchronous test to prevent page timout Cookie serialization: support saving all filter values privacy and security lot of security fixes Stop using google fonts in back office bugxies PHP compatibility fixes Better logging Fix Saving specific price without rules does not refresh specific prices on products Back office lists error handling Back office lists filter values serialization Category alternate url: check enabled flag Fix SpecificPriceRuleCore::getAffectedProducts Fix deleting default attribute Language deletion - fix directory cleaning Proportionate taxes: Fix shipping tax calculation Contact form: verify that order belongs to customer Fix error with cheapest product cart rules Clear op cache after zip extraction, fixing modules update Fixed translation extraction Fix download product link generation Use debug error page during installation Import: set out_of_stock only when provided KPI: fix refresh functionality Fix issue with incorrect tax breakdown Carrier selection issues Fix carrier weight restriction

There are two distinct things we do in thirty bees company. Firstly, we maintain open source project. This means: we are keeping the codebase afloat - we adjust code to run on newer versions of php, database, php extensions, new versions of dependency libraries. Without this, nobody in 2 years could run thirty bees project on any up-to-date server We fix bugs in core and more than 100 modules, as we assumed responsibility for this code We maintain github repositories for core and those 100 modules. We do code review for new pull requests. We scrub new issues, deciding if the report is bug or enhancement request, trying to reproduce the issue, etc We investigate and implement security patches that are reported by third party security advisors We play the gatekeeper card here, and decide what makes it to the codebase and what not. We hate to do that, because every line that makes it to the codebase becomes our responsibility, and we have to fix all bugs it might cause. So if the PR have tendency to cause a lot of grief, it will not make it to the codebase. We maintain set of api services that provides core updater functionality translations module updates and distribution We maintain forum, trying to help as much as possible We maintain store, web, demo, and other websites. and more If you look closely, you will notice I did not mention new code or features. We don't do that. At least not as part of thirty bees project maintenance. This maintenance is actually what you are paying for, if you are a backer. We do create and release new code under open source license, though. But that code is actually not part of open source project maintenance. Thirty bees company offers paid support and custom development services that anyone can purchase. Smile does exactly this. His private company purchases a lot of support time from thirty bees company, and invest it into the area he is interested in. It was warehousing feature are, packs, feature management, multistore, etc. Some of this new code development is done in core and released for everyone to benefit from. Some of it is implemented in new modules, that are either private, or ready to make available for everyone to buy. This custom development is a private initiative, not a public project by thirty bees. It is paid by third party company. Decision what features will be implemented or enhanced is entirely up to the company that purchased support time. Note that I play the codebase gatekeeper card here as well. I do not allow new code that could break the things for others. Some requests could be implemented very easily in a few minutes, but because they need to be reusable for everyone, it can actually take a few hours or even days to implement that in generic way. Smile is paying for that extra time, even though he does not benefit from it directly. Anyone can contact us, purchase some custom development time, and implement any feature they want. We will be happy to provide that service. Or they can hire third party developer to do that for them. We will do the code review, and merge any PR as long as it does not break things for others. Everyone can contribute to the open source project. And if they do not like the way we do the gatekeeping, they can fork it and maintain their own version. @Mark says that I'm playing the overlord and decide for everyone, and it's true. That what open source maintainers do. Somebody has to be the bad guy that rejects bad contributions. I'm comfortable being that asshole, I'm doing my worst for a good of thirty bees community, at least I believe I do so. Why are we maintaining this open source project? We don't really have to, now do we? I mean, Smile could fork and create his own version of thirty bees, hire me or other developer directly to maintain it for him. He would save a ton of money on development time, as there would be no backwards compatibility issue to solve. We could change anything and tweak everything directly in core. No modules, no overrides. No bugfixes for modules we don't use. No maintanance of code we don't use. We are maintaining the thirty bees project because we like the community, and we like to give back. We will continue to do so as long as we feel that there is a community to work with, and that the community cares. Being a backer means a lot in this context. It helps offset the expenses directly related with code maintenance, and it shows that there are people invested. It's a nice and tangible metric.

Notice: Upcoming version 1.4.0 will no longer support import of Excel files, at least not out of the box. Why? Thirty bees uses third party library to read excel files. Currently used library is no longer maintained, and does not run properly on all supported version of PHP (specifically on PHP8). There are alternative libraries that we could use, but those does not run on older supported php versions (php 7.0 and php 7.1). Because there is not a library that we could use that supports all php versions thirty bees support, we had to remove excel import functionality from the core (together with current library). But don't worry. Import functionality was extended, and we have introduced ability to register custom importer via module. And we will release new module 'Excel Import Datasource' shortly. You will be able to install this module if you run on on PHP 7.2 and newer. With this module installed, the Excel import will be allowed. This extension also allows for different data source implementation, for example import from XML files, or from API. If you are running on php 7.0 or 7.1 -- you should consider updating your PHP version.

Well Well Well.. I find it encouraging to see so many people trying to find a way into this mess !! I will tell you that I am still deeply involved in TB and will keep on doing my best to improve it like fixing bugs founded in core, I want to keep on doing it for free. Working for free for TB is good, I like it and it's not for free at all in fact, as I use it on many projects for my customers and this is not for free. Using TB instead of Presta 1.7 or OpenCart or WooCommerce or Magento is just the best option available for me specially for one point : All of the modifications I needed to do in CORE will be included in next version after adding a new pull request, but we need people taking car of that like trumbflug use to do and Datakick is still doing now. Just to resume : I'll be on the boat when TB sinks or not, hoping to keep it moving into the ocean of ecommerce CMS.

Even it’s probably not important at all, I will give now my view on things... Since months thirty bees is without a real lead. Since the health issue of Lesley, he has disappeared almost completely. But the problems began already earlier. Remember there was once co-initiator Michael, who suddenly left. As far as I know he gave up his company shares. See the source above. Technically he was replaced by Markus. But Markus never seem to got shares of the company. As far as I know he got some payments, but not near the market cost. Not too surprisingly Markus stopped to work too. Then there was only Petr left. Check out his posts, but in general he worked under even worse condition: a lot of support and commits/fixes for free. I see a pattern in this three cases. While thirty bees revenues were growing, the spendings for development were (probably) decreasing. Now we are all in a ship, that is just driving randomly on the sea. Lesley can’t lead the project anymore as he states himself, all major Devs are gone. No one is in sight. There are only three possible outcomes now: 1. Thirty bees is taken over Is the first scenario realistic? I have my doubts, especially when reading that the offered price for the company was 30 times, what Petr would have considered to invest. I am quite sure, that the valuation was not done properly. I would guess, that the income was used to calculate, but almost no costs. As it would be realistic that devs are always working for low or even no wages. As other already pointed out: the value of thirty bees can’t be very high right now. The code is open source. The value would be the brand, the amount of merchants and mainly the free cash flow. With such a solution I also wonder, who would even be the developper? Hard to imagine that Michael or Markus come back in this scenario. And Petr? Well this post is in his goodbye thread, so... 2. A new fork Some off you seem to think of forking this project again. Yeah it’s possible, but almost all off you, have no idea, what it means. It’s so much work, which again has to be done. Just creating a new fork doesn’t solve the problems. IMO a new fork would need multiple faces, that are ready to invest a lot of time, to maybe make money multiple years later. I read too many “I could do that” or even “this and that should be done”. Where have you been, when testers were needed for new tb versions/commits? Who of you has written documentations? Who of you has written concepts, how features should be redesigned and not only “the feature is bad/not working”? It’s not my goal to offend any off you, but it’s just hard to believe, that we suddenly have a dozen off guys, who will invest multiple hours a week for tb for free. I also see best chances in the proposed freemium system of @rubben1985. But are we enough merchants, which are willing to spend 50 (or more) dollars a month? And even more important: can we hire the right people with this money? Remember money is not the main problem of thirty bees... People who would be ready to pay 50$/month: @wakabayashi @Briljander @rubben1985 @Smile @vincentdenkspel @dynambee 3. The project dies and all merchants have to find their own way of handling it Option three is of course not very attractive. It’s the reason why this thread got hot so quickly 😉 Even if I share a lot of opinions with @toplakd. I am surprised how you can stay so relaxed. In my opinion every ecommerce company needs to get better daily. As I like to say: “You are either the shark of the ocean, or the fish of the ocean!”. We are probably all fishes. Ecommerce has become so hard last years. Some of you might remember @alwayspaws. Even if she was very active here and dedicated a lot of time to here online store, the business never really took off. I know some merchants who made good money by selling smartphone covers years ago. Now you can buy them for 2$ on wish. This niche is just dead. I could go on with with hundreds of such examples, but that wouldn’t help. Thinking “my shop is working now fine, I am safe” is in my opinion too risky. Even if I have to say a fish, at least I don’t want to get eaten by shark. For this I need to develop my shop further and further. Customer get used to the level/features that sharks like amazon offer. Your search/filters suck? Probably you will lose a lot of potential customers. Your mobile version suck? You are probably soon out of the game. Yeah this examples are not new, but new things will come again and we as a shop owner need to go on too. Most merchant’s here have no chance to technically handle that their own.

Hey guys, i created this theme based on community theme with clean design, some additional modules and second image on hover. You can see demo here: http://demo.worldtriangle.com/niara/ and download it here: https://gum.co/niara100/ Update 05.03.2019 Fixed missing option of some text translation in WtBlockBestsellers module Fixed invisible checkbox for terms and conditions if AEUC module is enabled Fixed customer registration from countries without states

I've just signed up with Patreon to support the thirtybees project. I don't know the developers, I am not a friend or a relative of them, I am just an e-commerce owner who was tired of Prestashop's continuous issues and troubles, and lack of attention in their forum when problems arose. I didn't want to update to PS1.7 because most of my modules would have stopped working. So more than a year ago I decided to try thirtybees. And I found it was lovely: no problems, fast response with the very few issues I had, even developers offering themselves to arrange things in my own server side, developers interacting with users in the forum. We all want everything for free, but if we have an e-commerce it's because we have a business, so we make profits thanks, also, to the work behind thirtybees. And we all want improvements and updates, and bugs fixed, and things working. The most honest thing we can do is to pay for the excellent service we receive. So, I encourage you to support thirtybees here, and it starts as low as $5/mo: https://www.patreon.com/thirtybees/posts?utm_medium=social&utm_source=twitter&utm_campaign=tyshare2 Think about this: changing your PS1.6 modules for PS1.7 ones would have cost you a fortune. Thirtybees has saved you a lot of money. Sharing this benefit with thirtybees is not just a good idea, but a profitable investment for we all: thirtybees will continue improving. And of course, it also a way to say "thank-you!".

Just in case anybody is interested, here's a preview of thirty bees 1.1.0. It still shows up as version 1.0.8 after installation. thirtybees-v1.1.0-preview.zip

Hi everyone, I needed a way to log into my frontend as one of customers. Because I couldn't find any module that would work correctly on thirtybees, I've build my own. I have decided to release it as an open source / free module. So, if anyone need this functionality, you can download it on my store. url: https://store.getdatakick.com/en/modules/login-as-customer github: https://github.com/getdatakick/loginas

Sorry I take over a bit of the post of @the.rampage.rado 😉 Today, we are thrilled to introduce the latest version of Thirty Bees: Version 1.5. This new release brings with it a lot of changes, including numerous core modifications and security fixes that are detailed in the list below. In addition, we are excited to announce the launch of our new Premium Module Offer! Instead of selling these modules at a high one-time price, we have opted to make them affordable for everyone! With only a small monthly fee, which is based on installation, not users. This will help support Thirty bees in maintaining the modules over time with the latest techniques and enhancing them based on your requests. Helping us to improve Thirty bees and make it grow! With the release of this version, we have also revised our Backer Plans, now referred to as Member Plans. Some of these plans include direct (paid) support from the team. This support time can be used to help explain how to use the system, custom development, or general support. Become a Member Now and Take Advantage of the Full Ecosystem! In the weeks ahead, we will release more modules designed to save you time and boost your revenue. We invite you to explore the new Member plans today, to save you time and make your store more productive! The modules can be found in your installation on the module page. And don’t forget, Thirty bees is an Open Source platform, maintained and kept alive by Merchants and enthusiastic developers. Any one time donation you make will be much appreciated and will 100% be used for the development and improvement of Thirty bees. Please buy us a beer or Become a Member and help Thirty bees to grow and trive! Happy selling! Petr, Theo & Chiel https://github.com/thirtybees/thirtybees/releases/tag/1.5.0 Changelog: Premium modules Extracted minification from core, introduced new module instead Extracted email sending functionality from core, introduced Mail Transport modules use Server Side Cache [redis/memcache] for smarty caching Attributes / Features list - drilldowns to products Support combinations for virtual products New carrier conditions - min order weight, min order value, max order value Cookies optimization - smaller, faster CSV import - support custom import entities Contact form: option to disable confirmation email Revamped File Manager - image handling, update library, security fixes Revamped modules zip files handling - unification, fixed problem with deleting assets Currency - ability to specify decimal places Cart rules: ability to set maximum discount value Support for custom notifications in toolbar System Notifications Webservice: Order Detail Pack informations Webserivce: expose Order Cart Rules Experimental features - stringify fetches Support tinymce editor customization Public names for features Bugs and Maintenance A lot of bug fixes in core and native modules Fixed lot of PHP 8.2 compatibility warnings Fixed redis/memcache/acpu cache Security fixes Removed support for PHP 7.3 and older Removed unused code (push notifications, configuration tests, rijndael) Fixed dashboard and stats reporting fixed ecotax calculation Fixes BO order edit - support free product, weight calc, restock... Fixed installation packs data - tax rates, zones,... Decreased dependency on third party library (google maps,...) Database schema changes tb_system_notification - new table tb_carrier.min_total tb_carrier.min_total_tax tb_carrier.max_total tb_carrier.max_total_tax tb_carrier.min_weight tb_cart_product.date_upd tb_cart_rule.reduction_max tb_cart_rule.reduction_max_tax tb_cart_rule.reduction_max_currency tb_contact.active tb_contact.send_confirm tb_currency.decimal_places tb_employee.last_connection_date tb_employee.signature tb_feature_lang.public_name tb_mail.recipient_type tb_mail.from tb_order_detail.product_reference - increased size tb_order_detail.product_supplier_reference - increased size tb_product.reference - increased size tb_product.supplier_reference - increased size tb_product_supplier.product_supplier_reference - increased size tb_search_index.word - increased size tb_stock.reference - increased size tb_supply_order_detail.reference - increased size tb_supply_order_detail.supplier_reference - increased size tb_search_engine - deleted tb_tab_module_preference - deleted Please, keep in mind: - module updates functionality was moved to core. After you update to 1.5 you'll have to remove tbupdater module (uninstall and delete it from your local install, it won't be needed anymore) - code minification and email sending functionalities were extracted from core so after you update to 1.5 you will have to choose one of two email modules and install the code minification module. Email modules configuration follows the same settings as they were in core up until now and the minification settings are kept in the same place. If you don't install those small modules you will not be able to send emails and your html will not be minified. - also please make sure that you update your DB after you update to 1.5 - as you can see there are plenty of changes there too. - if you use memcache, apcu, redis - use the new Server Side Cache setting = SUPER fast shop without full page caching!!! - introduction to system notifications - a place where you will be able to see future announcements regarding updates, etc. - it is strongly recommended to update to 1.5 - lots and lots of new features, BUGFIXES and SECURITY FIXES were introduced since 1.4 and this will make your shop smoother, faster and more secure. Regarding the premium modules, I believe that @datakick will describe them in the best possible light but they are a must of every serious merchant!

Due to some informal corona care tasks of one of the lead programmers, 1.3.0 has a little delay. It is our top priority, to get is quickly out. Will keep you posted!

Hi All! It has been a while since you received a newsletter form thirty bees! Well it was certainly time to send one out. I love looking forward to the future of TB but just a few words about the struggles we have encounter. Taking over TB is not an easy as expected task but all is on track to move forward as expected. Beside that I have to run my own stable ecommerce company which can be challenging with covid changes all things we took a year ago a granted. As a merchant I decided that for me it was worth taking over TB as I love the system and wanted to hire a full time programmer anyway. So we can extend the system for all of us and keep it cutting edge. This does cost a lot of money and at this moment is losing money. For all the people buying support and who back us this is great and keeps the system open, thank you 😊! Not a backer yet? Consider it, it would be great to get you on board so that we can work on more community requests. You can do this easily by going to the forum and choose support thirty bees! We recently launched the latest version 1.2.0. which has a lot of bug fixes and core improvements. Nothing fancy in the frontend or Backoffice though 😉 We like to keep it the most stable shop system out there and release stable regular updates. We will release more updates soon but expect after the catch up other updates can take a few months. We do expect version 1.3.0. very soon. It has quite some nice enhancements and improvements, like an new modern way of customer password recovery. scheduled tasks - sort of like build-in cron job work queue - mechanism to execute work jobs asynchronously in order to speed up request processing theme extensions - ability to extend themes, which allows us to introduce new front office features like new password reset work on php8 compatibility module installation overhall (1.6 still supported) product page tabs permissions What will the future bring? It expect TB to be a system that can work on a small scale but also on a bigger scale. For example with a advanced warehouse system which integrates smoothly but works as a separate system. Same for a product information system, and the fields needed for TB and all the different marketplaces. Also the frontend needs some updates as well as elastic search. We are also willing to discuss any enhancements big or small and if it is a good fit add it to the core or module. This can sometimes be free of cost or for a very affordable rate. Reach out to us and we can set up a meeting. Don’t forget to join as a backer! Stay tuned happy selling, all the best!

Let me preface this with stating the obvious, I am no longer with thirty bees and I don't speak for them in any official copacity. These are my own opinions. Now that is out of the way, Mark, you are a pain in the ass. You don't offer anything to the project, you donated $20 2 years ago. One thing I think is very complex for you to understand is that @Smile bought the company for a good / fair amount of money. Its no more of a democracy than if your company was a democracy. Over the years I have valued all of the constructive critism that has come down the pipe, whether I like it or not. When @wakabayashi stepped away to work on his own business and to see how thirty bees panned out, it mad me sad. But I read what he wrote, his thoughts, and they were fair and understandable. The same with other people that have come and gone over the years. Most everyone that has come and gone has been constructive, non combative, and have expressed themselves. You on the other hand, you talk like a child. You cannot form thoughts, so you just cut straight to insults. Like I said, I don't speak for thirty bees anymore. But here are my answers to your original post. 1. Its neither, its a private entity. If you want to influence the way the project and company are headed, you approach the owner with ideas. Maybe a joint co-operation. Not just cut straight to critisim and name calling. I cannot imagine that has gotten you anywhere in life. @Smile is a good guy and very open minded. He might not be who you pick to run thirty bees, but he is who I picked and he is running it. 2. As far as I know this is done. Notice the dev sprints on the forum, they state what is being worked on and it is set up as a proper company. 3. That is not how open source works. It would be really cool if it did work that way, but its not how any open source project works as far as I know. There are some with bounty programs, but those are also projects where they have users donating tens of thousands of dollars a month. Vue is one that comes to mind in that regard. Unfortunately thirty bees does not have that kind of traction. 4. No. This shows your limited understanding of software in general and as a whole. A long term plan has to be developed and followed. As much as the community of any project would like to vote on every task that is worked on, it is just not feasible. Things will end up too strung out, intensive tasks that provide seemingly little reward will be pushed to the wayside. A great example of this is how prestashop operated. They threw all of their resources into making 1.7, that is what people wanted, a new front end, symfony, ect. It wasn't out of beta yet and 1.6 stopped working. No one was doing the pain in the ass tasks like making sure browsers didn't deprecate the spaghetti code it relied on. A lot of the tasks that need to be done seemingly have no benefit to merchants, until they need it. That is why a roadmap is needed. 5. Where does this money that is paid out in your mind come from? The $20 you donated 2 years ago? You have just been an asshole to everyone here, you need to tone it down, act like a human being, act like there are human beings on the other side reading what you write.

Hi all We have some news to share with you: We've received the updated contract and after a few minor modifications, we felt comfortable enough to send it to our attorney. The contract is now at our attorney for verification and final approval. We should have more news soon. Will keep you posted.

In the upcoming days, a whole lot of releases of existing modules are planned. Sometimes just code maintenance, sometimes substantial improvements. I'll post release notes here, so you don't have to look up all of them on Github. Today it's Core Updater: Make the Ignore community themes switch aware of the new community theme, Niara. Substantial performance improvement when scanning large sets of (product) images. Some hosts simply timed out when searching 100,000 product images, making updates impossible. Code maintenance. coreupdater-v1.1.0.zip (also arriving in your back office)

Unfortunately there is no technical solution for this. Thirtybees just can't force any third party to support it. It's also not possible to build some sort of facade on top of the tb codebase in order to make ps17 modules work with it. I understand your fears, I really do. After all, it's your livelihood we are talking about. You need to decide what platform is best for you and your business, now and in the future. Let me just remind you that going with prestashop is risky as well. What will happen when they start working on ps18, dropping the compatibility once again? Maybe your theme will stop working, modules you bought will be useless, all the customization work lost. All because prestashop company doesn't care about compatibility, stability, or merchants themselves. You will be left high and dry. Trust me, they did this many times already, and they will do it again. Thirtybees, on the other hand, was based on a pledge of stability and compatibility. But of course, because the user base is much smaller, third parties don't have such incentive to support it. But I believe there is still great amount of ps16 merchants that appreciate the stability this platform offers and will migrate here. And with our user base increasing, there's a hope third parties will be more inclined to support it. Especially since they already have ps16 modules they invested great effort into. And thirtybees is a way for them to continue monetizing them. Now, it's up to you to decide what way is better for you.

Just a shout out really, for high quality, TB compatable modules with great support Some of us veterans may remember Vekia (Milos) from the prestashop forums. He was brilliant with help and support - but he did take a step back from those forums. I have recently purchased a couple of modules from him (pop-up manager and combinations table on the product page). Not only did he give excellent support but he added features to the modules for me also. Brilliant. If you do need any modules, his site is a good place to start. I did heavily suggest he joined us on this forum as he has fabulous insight to the workings of this ecommerce platform - let's hope he does https://mypresta.eu/

Hi everyone, I'm presenting you today a new module I always wanted to create: Consistency checks. Some of you probably know that I offer paid support services for thirtybees (and prestashop as well). In my line of work I have regularly encountered issues that were caused by inconsistencies between expected and actual environment. Thirtybees core, and modules as well, often expects that some preconditions are met. And if they are not, things can go awry pretty fast. Let me show some examples or issues I've seen: Extra file in /classes directory My customer accidentally copied php file /classes/Tools.php to /classes/db/Tools.php. That's not a big deal, right? Some extra file shouldn't have any affect on the system, right? Well, it does. When thirtybees generates class_index.php (index file for class autoloader) it includes all files from the /classes/* directory into it. In this case, the result was that thirtybees core used Tools class declared in file /classes/db/Tools.php instead of /classes/Tools.php. At the time this accidental copy happened, it wasn't a problem yet. Because both files were the same. But when my customer decided to upgrade to new version, it started to matter. And it bring down the entire server. That's because new version of thirtybees was used with old version of Tools class... It took me 4 hours (and my customer 200 EUR) to figure out the root cause of this problem. The fix was simple -- just delete the extra file. Module were deleted from filesystem without being properly uninstalled We all are guilty of doing this. Sometimes you install some module, and it crashes your shop. HTTP 500 error code. So you login via your ftp and delete the module. And the shop works ok again... But, there's a problem. There are remnants of the module in the system. Entry in modules table, registered hooks, possible overrides,... these all can cause weird stuff and bugs. For example, core updater will not allow you to perform update if it detects that some incompatible module is installed -- but what if you already deleted this module from /modules directory? Sorry, you can't upgrade. Not without going to your database and delete the module information from there... Also, these deleted modules slow down your system a bit. If there are hooks registered by delete module, thirtybees core have to evaluate this situation over and over again, every time the registered hook is executed. That's waste of resources. Images aren't displayed, because the image file is not on filesystem This is classic problem associated with migration. You copied your /img/p directory from old server, and then you import your data into database. It's very easy to make a mistake, and the data in tb_image tables can have different IDs. If that's a case, your images won't show... because the image ID does not correspond with id used to store file on filesystem... Consistency checks module All these issues can't be reproduced on vanilla installation. That's because the inconsistencies does not exists (yet). There are no extra files in classes directory, no modules were force-deleted, and all images are present,... But these inconsistencies will appear eventually, simply by using the system. So I decided to create a module that runs a bunch of tests against your system in order to find these problems. And, if possible, offers a fix. By using this module, you can get your system into the state that matches the vanilla installation as much as possible. And that can help you reduce the chance of bad things happening. At the moment, the module does not really contain a lot of tests, there are only 6 of them. But I plan to implement new along the way -- every time I will work on some problem that is caused by some inconsistency. So you can expect a lot of updates in the future. Also, if you have idea for some checks, let me know. Bug detection This module can also help detect bugs in the core or modules. If you fix some inconsistency, and it re-appears, it's likely there is some bug that wants to be fixed. Don't be shy and report this. Help thirtybees be better and more stable. Download I decided to release this module for free in order to help this project to grow. You can download the latest version of the module here: https://store.getdatakick.com/en/modules/consistency

Hi everyone, we have just released thirtybees 1.5.1. This is just bugfix release that addresses new bugs introduced in version 1.5.0. If you are running your store on stable 1.5.0 you are advised to update. If you are running your store on bleeding edge (1.6.0), no action is required. These bug fixes are already part of bleeding edge as well.

I am still working days (and nights) to push my theme forward. The progress is quite amazing. IMO there is no doubt, that we should go for FrontEnd component system. This in combination with fast ajax requests can lead to a damn good result. And the good: the core needs almost no adjustments. I have only a few very simple overrides... Here is a sneak preview of a fast customer journey: genzo_theme-preview.webm I work often with modals. This gives a much better user experience (especially on mobile devices). But in general it's all about the usage of predefined components: https://www.genzo.ch/tb-framework Here you can see the module "tb_framework". As you click through the Elements/Components you will see a lot of elements, that you saw in the video. Any theme/module can use these components as well. I won't publish my theme/components as they should be unique for my store. But I could open source the technique behind it. Especially the "tb_framework" module. Steps to get a similair result like mine: Somebody builds default components for "tb_framework". Best would be without any framework. Actually I did mine only with TailwindCSS, which means, that it's also possible without any at all. Only exception might be slider functionality. (Ofc I could support this task with my components). A new theme from scratch is created (or maybe existing cisero), that implements the components from "tb_framework". For the theme imo any framework can be used. Core modules are adjusted to use components from "tb_framework" module. (This is not too hard and actually quite fun) My opinion: As this is damn much work, I don't think we will find one guy, that makes this in his free time. A crowdfunding might be needed.

Quick update. We expect version 1.3 in the first or second week of september.

Regarding PHP compatibility: 1.3.0 will still be supported on PHP5.6 ... PHP7.4 There is an ongoing effort to make it work on PHP8. This is not a small feat because PHP8 introduced standard class 'Attribute' that clashes with thirty bees core class. To fix it we need to rename our class, respective move it to different namespace (in core and all native modules). While this is quite simple to do, it of course introduces compatibility issues with any third party modules. To overcome this issue, thirty bees will contain mechanism that will parse and 'patch' third party modules PHP files. When you install new module, it's php files will be processed anda all references to Attribute class will be adjusted. For this we will use third party library. Unfortunately that lib does not support PHP5.6, which is one of the reasons why we are deprecating PHP5.6 and will not support it in the future. At this moment there is still no need to actually remove support for PHP5.6, but once we integrate the support for PHP8 to mainline, we will be forced to do it.

This morning at 7am Sprint 3 has officially started. This sprint will be a little bit shorter because of the Easter holidays, we have only 8 days to finish following tasks: Finish Core Updater enhancements continuation of work from sprint 2. There are still some work left before we can release a new version of core update Automated testing pipeline in docker implement docker container that we can use to run automated test on any branch / revision submitted to github integrate this docker into CI pipeline Multiple feature values this is one of the most requested enhancement that existed for a long time, and we will finally implement it it will mean a potential, but very small, compatibility issue Tracking framework implement framework that will allow sending various information about your thirty bees installation to our tracking server (don't worry, it will be on opt-in basis) tracking framework will use scheduler that we implemented in sprint 2 Track environment information once the Tracking framework will be implemented, we will use it to obtain first set of data: php version installed php extensions mysql version memory limit timeout limit Bug fixing review and merge PR requests fix couple of high severity bugs Support requests work on paid support requests Please ask if you have any questions about anything

Sales are booming and my PS/TB is 11 years old... Worried my site could not keep up with the increase in sales, and not wanting to invest into a platform that looked like it was dying ie, TB. I spent the last two months flat out trying Shopify, BigCommerce, WooCommerce, Magento, Spree and every and other cart and template out there. I've landed back here with my old TB site because despite 11 years, changes in platforms and hosts TB just does everything it needs to do. I'm still on the same website I have always been on, so as long as TB is here looks like I will be here too. TB is the best!

Just for the record and for whoever is buying Thirty Bees, there are many users like my company that value Thirty Bees and are waiting patiently for the transfer of ownership to take place and for the resumption of development. So, don't be put off by the relative quietness or inactivity in the forum.

We consider thirtybees core to be very feature rich. There's no good reasons why another features should be added into the mix, as it works for 80% of the merchants out of the box. What we want to achieve is the stable, and easily extendable, system. That's the reason why most of the development was aimed into these areas. Fixing bugs, improving error reporting, overhauls of the most buggy code areas, adding more checks etc... With all this, we can finally have a system that can be deployed to production with confidence, and it will work even if left unattended. That's not something you can say about the competition (yeah, I'm looking at you 1.7) The problems with this kind of development is that, well,... there is not much you can say to the community. There is not big roadmap with flashy milestones. It's a boring, chore-like work. That's one of the reasons why nobody writes about that, here or in some blogposts.... I know it can be frustrating for you guys that don't understand code and don't look into the github... that's why this kind of thread flames every now and then

Core Updater is pretty advanced software updating technology and has shown to be quite helpful since it was released. Merchants lost fear to update their shop installation as they can roll back easily. Great! This way, developing the software actually makes sense, merchants can take advantage of all the new stuff. There was always a pimple in the picture, though: provided releases had to be added manually by a thirty bees developer. As so often, stuff to be done manually easily gets forgotten. No longer: over the recent weeks, Core Updater's background machinery has learned to build releases automatically. This is especially helpful for Bleeding Edge: the minute a change gets committed to the Github repository and passes validation, it appears in all the shop back offices. Can't get forgotten, always accurate (knock on wood). Another new thing appeared: issue branches. When tackling issues reported on Github, developers often want to show partial work or provide completed work for testing. Maybe they just add debug messages to find out what's going on in a shop installation. Now they can commit this work as issue branch, merchants will find it in the Bleeding Edge channel in Core Updater listed. Merchants update to this, test, report back their opinion in the issue tracker. Easily fast enough (~6 minutes after push) to allow timely discussions on how to implement this or that the best way. Note to developers: an issue branch is a branch named with exactly 'issue-' (including the dash), followed by a number consisting of digits only. This number should match the Github issue number. Enjoy! P.S.: this is available immediately, no upgrades or whatsoever needed 🙂

Hi everyone, I just wanted to raise your attention to the fact that cloudflare recently enabled Speculation Rules API for all plans. This functionality is designed to improve browsing speed by aggressively prefetching potential future assets/pages etc. However, these prefetch requests can be quite dangerous sometimes. Example: I'm in back office modules pages, and I click on 'Uninstall module' button. The confirmation dialog is displayed to ask if I'm sure. But the question is irrelevant - because of this new prefetch functionality, your browser already sent a request to your server to prefetch the response for the uninstall action url. The module is already uninstalled You can see the request in network tab. Even though claudflare responded with 503 error code (meaning the prefetch response will be ignored by browser), the request still made it to your server, and action was executed. If you click 'OK', thirty bees will send the actual request, and it will actually fails with error message "This module has already been uninstalled" That's nice, isn't it. The uninstall/install module buttons are not the only one that are impacted. For example, 'delete' or 'approve' or 'send' buttons in lists in back office, etc... It can also impact front office, most likely -- browser can automatically add product to a cart because it believes that user will click on the "Add to cart" button soon, so better be prepared for that... right. It's quite dangerous optimization. It's true that if thirty bees used POST instead of GET requests to implement these kind of actions, this situation could not happen. But we can't really change that. We will look into a way to prevent/mitigate this problem. Fortunately, browser is sending some HTTP headers that we can use to determine if request is a regular or prefetch, so we can use that to prevent this (hopefully) But until a fix is implemented, I advice you to disable this new prefetch optimization in your cloudflare dashboard. And to be sure, maybe even after that 🙂

Module implements mail functionality using PHPMailer library. Module compatible with thirty bees 1.5.0 bleeding edge and already available in list of native modules. PHPMailer library is compatible with PHP 8.2, also it is worth replacing "Mail via swiftmailer" module with this module.

@Smile / @datakick good luck! I'm a developer who runs a TB shop for my wife. Happy to help shoot down some bugs.

This is a bit unfair. You shot yourself in the foot back in the day when you decided to modify *core* files. Now you are stuck to the version you 'forked from', and you blame core updater for things going bad during upgrade. Core is named core for a reason. It should not be touched, ever, by merchants. Or by anyone, really. That's why thirtybees have override system in the place, and a hook system as well. Unfortunately, this kind of core modification is very widespread. There are many tutorials on the internet describing how to do things this way. Many third party developers / agencies do this as well, mainly because it's the easy way to do things. The result are shops running on outdated system, scared of upgrading, stuck in the past. It's a bad situation, but it could be fixed, actually. Thirtybees could bail out these shops. We could have automatic tools that would convert these core modifications - extract them to custom modules using overrides. We could also have the system that could learn and understand what has been modified, and notify merchants during upgrade that some of the overrides are no longer valid, for example.

I uploaded a new Prestools version: 1.24n. It contains a new version of the image plugin too. The new version fixes a few issues with image edit: - you could not add an image to a product that didn't have any images. - when you marked a newly added image as cover it wasn't registered as such. As a consequence the product ended with no cover and you didn't see an image in the backoffice product list. - when you made the image field editable and the cover image was not the first one it displayed on the first position the cover image too. The editing is now more wysiwig as it makes that you to always have an active cover product. If you find any more problems please let me know.

It was Thanksgiving here in the U.S. thursday. As I'm getting back to work, I just wanted to let you all know know how thankful I am for this community in helping to keep TB a top notch store front tool. Especially to all they folks writing code on the backend and responding to all of us business level admins to assist. I and my business really appreciate it.

Hi, I'm the original creator of the module, and I'd be happy to donate it. Just tell me what you need.