Yes, you read that right! Another version of thirty bees coming up. It has been weeks of hard work, scanning through old pieces of spaghetti code and refactoring large pieces of the software (don’t be afraid to change the code once in a while to make it better!). The goal of these changes is to make the core more stable and/or make it easier in the future to remove bugs and to test it. This also explains why it took a while to reach the beta stage of the next version as we had to fix lots and lots of errors we saw in our production environments as a direct consequence of these heavy changes [we are testing it live, so you don’t have to 🙂 ].

Release candidate?

We have kept the first alpha versions and the first beta private as we found a lot of problems with those packages and while we were at it, decided to release a beta which we think might even be release candidate-worthy. As our regular visitors of our GitHub repository might have noticed, the issues for 1.0.1 have now been exhausted. This means that it is up to you and let us know via our forum or GitHub what problems you come across and might need to be fixed before releasing 1.0.1 stable.

Another reason for us to wait such a long time before making the newer version public, is that we also extensively have been testing the PS 1.6 => thirty bees migration tool. It will allow any version between and to be migrated to thirty bees. To make it easier to find the bugs this release candidate-ey package was also very helpful. After the files have been successfully copied by the migration tool and the database has been perfectly changed (just a few extra tables!), you’re suddenly left with a rock-solid thirty bees engine in your store. We are not sure if the default community theme should be included in the migration tool as well (most of you already have a nice theme and no need to change), but if you think we should, let us know in the comments! We definitely listen, that’s the whole reason for this project.


Thank you very much for the feedback you have given us through all the channels possible: Gitter, GitHub, the forum, you name it! As a result we have processed a lot of your feedback and included it in 1.0.1 [sometimes we even were a bit too greedy with merging your pull requests – thanks Markus, but we found out the hard way that have to postpone your contribution till 1.1.0 😉 ].

Here are a few highlights:

  • The top menu has been reverted to a forked version of the PS top menu.
  • Fixed a lot of problems on the Supplier/Manufacture BO pages.
  • Fixed the Friendly URLs and wrote a workaround module for those affected!
  • Made a security patch for those who host back office demos with thirty bees.
  • Fixed exchange rate modules.
  • Fixed the module list.
  • A build script to ensure solid packed release packages (thank you very much, Markus Hitter!)
  • Improved PrestaShop 1.6 compatibility by restoring the tools folder and a few more tricks.
  • Restored translations and localization packs. Thank you for contributing on Crowdin!
  • Fixed the CSV importer. Thank you very much for sharing your CSVs. If you think some things are still broken, feel free to contact me directly via the forum, Gitter or whatever channel you can find. This item is very important!
  • Despite it being a patch version we felt the need to add a few features:
    • Error reporting. The back office page Advanced Parameters > Logs allows you to decrypt error messages that are shown on the Front Office. Instead of a blank page thirty bees now tries to catch the error and encrypt it via a friendly public message. In case one of your store’s visitors comes across a problem s/he can quickly share the generated code with you as a merchant and it will allow you (and only you) to decrypt the message and see the exact error message (plus more information for developers). We felt this was badly needed and expect that it will make the problem solving process much much easier and quicker!
    • Omnipay library. This library will allow us to quickly write integrations for about 50-70 payment gateways. We will cover this in a future blog post (and on the forum, stay tuned!), but as we are going to run a few tests soon, feel free to let us know in the comment section with which gateways we should start.

How do I update 1.0.0?

For the moment you can not. This list of dependencies will show you what needs to be done before we can provide a solid patch system for thirty bees:

  1. Release 1.0.1 stable
  2. Finish the migration module
  3. Finish the thirty bees updater

Note that we do not give deadlines as we really want to take all the time that is necessary for a rock-solid system, but we expect that the migration module might hit beta by next week. And, yeah, the 1.0.1 is a biggy, but if we all can not find any heavy bugs in it, that one might hit stable by next week. After that we will further develop the thirty bees updater (of which the module updates are already working!) and things might go really really fast.


Because MailChimp will then be the next module on the agenda. We have been working extensively with MailChimp and a few stores to make sure the e-commerce integration rocks! There are just three items left to make it the best integration ever (especially to make it suitable for Europe). If you have some spare time and want to help us speed things up, we gladly accept pull requests! And who knows, this might get you a partnership for free, because we have plans for contributor partnerships, since we feel such a program belongs to our open-source nature and what could be a better test than seeing your great developer skills in action?

The MailChimp module will be provided for free and become a native module, always one click away from your back office, so whenever you need to launch a store, you can get your email marketing (automation) started right away, so you have more time to focus on e-commerce.

Blog module

That freed up time could be used to add more content to your site. Besides having cleaner URLs in thirty bees, you can easily improve your SEO via several blog posts (well, the more the better). This module will be released after MailChimp and made available via the thirty bees updater, so it should show up in your back office as soon as it is ready. Have a look at the roadmap for the features:


Well, here it goes. The package!


And in case you haven’t understood from this blog post: we NEED your feedback, so post it wherever we can find it! Oh, and let us know which payment gateway you use. We love that kind of info, you know, to complete our roadmap.