Leaderboard

Hey everyone! I wanted to share my experience with thirty bees. If you’ve been searching for a robust, feature-rich solution for your online store, I think you’ll be pleasantly surprised by what thirty bees has to offer. Here are some of the reasons I’m running it on all my shops since it's fork : Focus on Stability and Performance One of the biggest headaches in e-commerce can be platform instability - nobody wants a store that crashes or slows to a crawl. thirty bees is built with performance in mind, ensuring that page loads remain snappy and your store stays responsive. This means a better experience for your customers and less downtime for you. It supports most modern caching solutions and runs on apache, litespeed and nginx servers. Easy Migration If you’re already running an online shop on PS or a similar platform, moving to thirty bees can be straightforward. The developers have put a lot of effort into making the migration process smooth. That means you don’t have to reinvent your store from scratch or lose your hard-earned data and customizations. Some troubleshooting will be required if you have to migrate from very old php versions (v5) but there are plenty of help here in the forum and people that can do the job if you're not confident with it. Open-Source Community thirty bees is an open-source project, which means you get the benefit of a community of developers, merchants, and enthusiasts who actively contribute to improvements, security patches, and new features. You’re not tied to a single vendor for updates or support—you can tap into a global network of experts. If you need support or you need some of the quality premium modules you can subscribe for a tiny sum per month, but it's strictly your choice. Rich Feature Set Whether you need advanced product attributes, multiple languages, detailed analytics, or a robust checkout process, thirty bees has you covered. It provides a wide range of native modules and integrations, making it easy to tailor the platform to your store’s needs without having to rely on countless add-ons. New features are added on regular basis while trying to keep compatibility with themes and modules from established developers - packs with attributes, list filters for BO and many more! User-Friendly Back Office The admin panel is designed to be accessible and intuitive, so you can spend more time focusing on growing your business rather than wrestling with confusing settings. Tasks like adding products, managing inventory, and processing orders feel straightforward. If you are bored with just one shop, switch Multistore ON and make your second shop in the same installation - save on development time and running expenses. Strong Compatibility Because it’s based on a well-known e-commerce framework, thirty bees supports a lot of existing modules and themes. You can often bring your favorite PS modules over, or tap into the thirty bees - specific extensions developed by the community. Active Development The team behind thirty bees is committed to ongoing improvements and enhancements. That means bugs get fixed quickly, and you can expect new features to roll out regularly. Staying current helps keep your store secure and competitive. If you find any bugs or request new feature you can post here: https://github.com/thirtybees In Conclusion If you’re looking for an e-commerce solution that combines reliability, performance, and an active, helpful community, I highly recommend giving thirty bees a try. It’s been a breath of fresh air for my online stores, and I’m confident it could be the same for you. If you have any questions about migrating or just want to talk shop, let’s discuss it on the forum! And now a personal appeal to the fellow forum members: thirty bees thrives on community support. Whether you subscribe, donate, or contribute your development skills, your help drives innovation and secures the future of our platform. Our because it is made and maintained by fellow dedicated merchants and developers.

I did some testing, and... released a new version of paypal module, and I strongly recommend everybody to update 🙂 There was a serious bug in module. When creating an order, paypal module provided current cart value instead of amount that was actually paid. This should be always the same, unless it isn't. For example, if you can do this: clicks on payment button that opens paypal checkout page open your store in different tab, and amend the cart (add/remove products, change carrier,...) switch back to paypal tab, and conclude the payment Normally, the order would be created with Payment Error state. But because of the bug in paypal module, the order would be created in Payment validated state, everything marked as fully paid. Neat.

I appologise for the late reply, I missed this request. There's no need for any postprocessing as @Adik suggested in his reply. Datakick module supports building this out of the box. Let me explain how xml builder works. When you create xml node, you can assign it Data property. When you do that, that node will be repeated for every record in your database. Example: node <category> assigned data = Categories. Result: category node is repeated for every category in your sotre. Now, inside this <category> node, you can create a new node, and once again assign it Data property. For example, product: Result - inside every category, all products are displayed That is probably not what you want, though. You probably want to filter out products that are somehow relevant to the parent category. For that, there is a Restriction property. You can say how to restrict product based on their relationships with parent node (category). For example, we can have 'Products in category' restriction which means that product is assigned that category. Or you can use 'Product use category as default' restriction. Result : we have list of all categories containing only products associated with that category Back to the question. In the same way, we can modify xml feed for google, and add new element <g:additional_image_link>, assign it with Image data, and set restriction = Product images. We can also add additional condition to get rid of remove default image that is inside <g:image_link> Result is what we want:

We use Datakick's module to submit data feeds. The ads themselves seem best managed within the meta ad tool. We've never connected the API for tracking yet, as we haven't found a good tool that will connect to TB yet.

@the.rampage.rado your post reminded me, to renew my supscription 👍

Very nice summary 🤩!