Comments on: ThirtyBees, a PrestaShop Fork project

By: oliiix

oliiix — Wed, 17 Jun 2020 12:52:00 +0000

you seriously wanna join forces with the people who don’t care at all? I mean you have to give an additional piece of nothing if you do not even care about hundreds of price calculation and display bugs in a product that HAS to do at least this correctly. Besides I never heard from them on any of my requests and questions even when payed modules were not working and I didn’t hear anything from the module creator, money just lost. Yes that product definitely deserves to be forked… And forking is actually a very good thing but I’m not going to get into right now. It’s a good think especially if you create something wonderful with it. There’s no backside to it except human ego

By: NemoPS

NemoPS — Mon, 06 Mar 2017 04:42:00 +0000

Myles,
Well there is no way to keep up with that if you need to use it on a live environment. It’s not ready for production yet, so I would try to wait a couple of subversions and just download them from the site.
If you need to stay updated, the only way (that’s what we do) is to erase the local version and pull down again from github, then reinstall

By: Myles Cirillo

Myles Cirillo — Mon, 06 Mar 2017 02:48:00 +0000

Nemo
Im new to Presta Shop and what sold me was that I could easily manage my own store. In an effort to learn more I stumbled onto your video tutorials and now I’m here. I have BlueHost as my service is this a problem? How can I keep up with the fork revisions and not get burned? Thanks for your insight and videos.
Myles
Owner

By: Casper Olsen

Casper Olsen — Sat, 11 Feb 2017 20:03:00 +0000

I will keep an eye out for this project. After they announced 1.7 it has been a fight to address even small issues in 1.6 and after the release of 1.7 it did not got any better, really.

By: smartdatasoft

smartdatasoft — Mon, 16 Jan 2017 06:08:00 +0000

thirtybees, Will be the best ecommerce , For the last 4 years of contribution and hard work for Prestashop , Prestashop give nothing to us. They just kick all of us

By: NickN

NickN — Sat, 14 Jan 2017 18:21:00 +0000

I for one will be keeping an eye on this as I find it very interesting. It’s a good thing that there are agencies and profesionals that make a living out of this, beacause at the end of the day we all need the money :-). Although I love prestashop it always seems fragile. I will continue to work with 1.6 as long as I can and will consider my options then. For me opc / upgrading are the biggest problems with prestashop. I read on the net some very interesting ideas about the project.

Best of luck and see you there

By: NemoPS

NemoPS — Sat, 14 Jan 2017 18:08:00 +0000

Hi Nick, and thanks for joining.
The fork has been created because it’s not actually possible to “join forces”.
We tried, we tried helping and improving the code, suggesting features and so on, but have seen our efforts constantly being frustrated by the company and its suicidal choices.
The fork doesn’t want to hold back, but rather, as you say, improve. It will indeed fix bugs and add just a couple of features at the beginning, but will also take its own course later on.
There is no reason to adopt symphony and twig, why should it? It only adds another level of complexity, which is not needed. Prestashop already shifted from pure php to having its own adapters and classes recently, and this doesn’t help newcomers. It just raises the requirements bar a little higher, and the fork wants to avoid it.
It simply wants to continue to develop prestashop with the spirit it was born with: simple, fast, efficient, the software every merchant could use, even with little to no financial resource.

By: NickN

NickN — Sat, 14 Jan 2017 17:04:00 +0000

Strange that nobody commented on this. I know that prestashop ppl are watching this.
I can fully understand why a fork is beeing created. Although I hate forks reason beeing that I believe that’s its better to join forces instead of splitting.
IMO this fork is “holding back”. Let me explane: You say that it will be based on 1.6 and fix the bugs for this. By the time you get your project together and try to fix the problems in 1.6, prestashop 1.8 will be released. This fork may be a wakeup call for the prestashop team and maybe they step up their game and address the probems you are saying about 1.7.
IMO this project should be more bold and focus on “fixing” issues by upgrading the code all together. Sympony3 and twig would be a nice example. At the same time adding the features nemo is saying prestashop is missing (what does nemo realy think prestahop is missing?). For me this with a “compatability mode” for 1.6 themes and modules would be the ideal deal. Because let’s face it at some point backwards compatability will be broken.
I hope the best on your effords and beeing a 1.6 store owner I will keep my eye on you.
Best of luck
Nick