WebsiteBaker Community Forum
WebsiteBaker Support (2.13.x) => Modules => Topic started by: svsanchez on June 15, 2023, 08:52:06 PM
-
Hello, I just noticed that the Bakery module is no longer supported :-(
Does anyone know if it works with Baker 2.13.3 and where can I download the latest version?
-
latest free version is here -> https://addon.WebsiteBaker.org/pages/en/browse-add-ons.php?id=0648E8
but be carefull with this, no guaranty, that its work with PHP 8 and higher
-
Hello Sternchen, thank you, that is where I tried to download it before asking but it says that the download is NOT available :-(
-
Try it here -> https://www.bakery-shop.ch/en/bakery/
-
Yes, had already tried that one too, but unfortunately the download link points to the same URL (https://addon.WebsiteBaker.org/pages/en/browse-add-ons.php?id=0648E8) where it is not available anymore.
-
Bakery - Support from the Developer freesbee stop's in 2017. Now its supported by Florian and he is the boss from WBCE. You can try the latest free version 1.89, see my link and there under Downloads, bot no Guaranty, that this module works with WB and the latest PHP-Version
-
Thank you so much for your help Sternchen. After about 11 years my client has decided to abandon WB and move to WP. He had been hesitant because he has about 3000 products on his site, but I guess without Bakery it's a painful but right move.
-
i cannot be happy, when i lost a WB-User, but in the case of this shop, i think, this is a good solution. i remember the whole problems with utf8 and with upgrades. Now, with a new system, all this problems are gone.
All the best my friend
regards Uwe (aka jacobi22 / sternchen8875)
-
Bakery was a great 'little' shop module, so easy to use and implement. I would give my vote for it to come back again.
:-)
Seanie.
-
Bakery was a great 'little' shop module, so easy to use and implement. I would give my vote for it to come back again.
:-)
Seanie.
Sorry to bring up an old post about Bakery again (the Bakery Shop forum is read-only), but 2 questions I'd like to ask:
1) Why was Bakery stopped as a shop module? and
2) Would it be worth developing Bakery again for the latest WB, now that it is more stable than ever?
I like WebsiteBaker, I have used it for a handful of websites for many years and the only thing that's missing in its latest version is a shop module. As an open-source CMS in competition with the best of them out there on the world wide web, WB is so much easier to use than Wordpress and other CMS engines in my opinion, but the lack of a shop module is a sore point! :wink:
Seanie.
-
to #1: Christoph Marti (FreeSbee) was the developer of this (in the first version) very small shop, but it came from a different time with a different idea. This idea was to present products in an organised picture show so that they could later be bought in the live-shop. At that time, there were no rules such as GDPR or "Trusted Shops". There was no need for customer management because you bought locally in the shop. In the first module versions, a single image was sufficient and there were no invoices. All this came over the years, but it was never a professional shop system, it was only intended to advertise things you wanted to sell.
That was in 2007! - The basis for the Bakery module was the well-known News from WB. Even today, more than half of the code is still from the News module.
Over the years, the module has become bigger and bigger, with its own image gallery, various payment methods, stock management and invoices. However, this also meant more trouble, because the tax office, for example, only accepts clean accounting, because payment methods suddenly stopped working and because PHP and WB were constantly changing. All this meant more and more work. A user only sees a new module version, but not the time required for research and programming. In the end, the effort became so great that Christoph decided to give up the project in 2015.
Florian from WBCE then took over this project, including the domain in Switzerland, and continued it in this form until 2018. However, since WB and the fork had diverged in terms of code over the years, there was also a version adapted to WB, and then came the GDPR and it would have required major changes. Plus the constant major updates of PHP and MySQL. As a result, the Bakery module (in all versions!) is now at high risk of a warning and therefore had to be blocked in the WB downloads. As a provider of such downloads, you are also obliged to comply with current laws. This mainly relates to EU regulations and the author's country of origin. Whether the subsequent user then deactivates such functions because they are not required in their country or on their website is irrelevant.
And that means in detail: for the EU area, you need customer management, the GDPR options, a revocation function, your own data protection page if necessary, etc.
There are also things that you simply expect from an online shop: a notepad, a functioning shopping basket, separate fields for weight information, other details e.g. ingredients for dishes, a rating system (star rating). And in this day and age, you also need different shipping options for certain items, e.g. by quantity or weight with automatic price calculation after changing the number of orders. These are just a few small things that come to mind spontaneously, but there are still the basic things such as: an output that works on both mobile devices and in 4K resolution on the TV at Home
to #2: WB is a free CMS and anyone who makes a module available for free use here also does so for free. I estimate that a good bakery successor with all the trimmings and certainly under EU law would take at least 6 - 12 months full-time from Monday - Friday if you program alone. But you're already at least a semi-professional and you know what you want. What time you could gain with a second programmer is probably wasted on arrangements. The rest is simple math.
A programmer's personal aim is always to be better than other, similar things. Now I know e.g. only WooCommerce (for Wordpress). I think this is a good solution in the area of “do-it-yourself” people: read a lot, click a lot. It's not a professional shop, but it doesn't need one. All it takes is something compliant with the law.
As a programmer, you will still have to research and learn one way or another, so another 2 - 3 months.
Now the simple question: If you work on this module for a whole year, how much money do you need to be satisfied?
If you work full-time in the factory, in the office, no matter where, how much time do you have after work for such a module? And if you have a partner and children too, what time is left?
Now we are perhaps two years later and we say: the shop is finished. But at least once a year you have to invest time again because PHP and WB will change.
Another thing: the number of support requests for Bakery has decreased significantly since 2018 (the introduction of the GDPR). One can assume that many have closed their shops because they were insecure. I looked after a few myself and they were all closed. I converted one of them to WooCommerce / Wordpress. The question must be asked whether the effort is even worth it. Nobody is going to program a free shop for one single user over one or two years and nobody knows what will happen to WB or its forks in this two years.
-
Are there any exact guidelines how to make shop GDPR compliant , like a final list with rules 1,2,3 etc.. ?
For some time I am working on a bakery fork, but currently it is only working for listing. Examples can be found here (https://www.promomaterijal.me/promobox/olovke/) and here (https://www.multitasknekretnine.me/prodaja/) and current code has significantly improved since then but it is not ready for public release yet.
But to make this a shopping cart, as sternchen8875 said, it takes a lot of work first to research, then to code and test.
-
Are there any exact guidelines how to make shop GDPR compliant , like a final list with rules 1,2,3 etc.. ?
difficult to answer in a foreign language...
Checklist: The most important points for GDPR compliance at a glance (source (https://www.p2media.de/news/datenschutz-im-e-commerce-worauf-sie-bei-der-dsgvo-und-onlineshops-achten-sollten/))
- #1: Draw up a privacy policy or adapt it if necessary
- #2: Adapt forms so that customers are adequately informed about data processing and only data that is actually required is requested
- #3: Ensure sufficient encryption - in some contexts, a more specialised SSL certificate or deeper encryption may be appropriate.
- #4: Scrutinise analysis tools and adapt the way they are used if necessary - clear information about the use of data, consent options and anonymised IP addresses should be guaranteed.
- #5: Customise cookie banners so that users can specifically consent to the use of relevant information or not, depending on the purpose.
- #6: Adapt newsletters or correctly organise address data used for email marketing - consent by recipient, documentation of sources, data protection notice, etc.
- #7: Create or adapt general data protection documentation - according to the GDPR, e-commerce companies are obliged to be able to prove compliance with all legal regulations.
- #8: Create or adapt protection for minors if data of underage visitors is processed - i.e. provide an explicit consent option for legal guardians
- to #1: best solution for WB and a new shop module in my eyes: a own part for a special shop privacy police in the shop administration and add this via droplet or section picker to the general privacy police of this website. What ever you do, it is (in my eyes) not possible, to build a shop system, working without cookies or session datas from the customer. it is important, that a customer say YES to cookies and you have to check this every time in every form, especially before the purchase is finalised. WB has some good helper-functions to include the data protection pages, see form and news-module
- to #2: means: a good text in your privacy police to give a description, what are you doing with the customer datas
- to #3 && #4: in my eyes, SSL is absolutely essential, never use a real ip-adress from a customer somewhere in the shop administration or database
if you work on your website with customer datas and you've a bigger company or shop (more the 9 People) or if you send's customer datas to another company (outsourcing), maybe for newsletter or invoice- && shipping-service, you need a special "data protection officer", declared in your privacy police.
some other important things:
there are also some other rule: every customer has the right, to see a order status and a order history and he can say everytime: pls delete my personal datas and delete my account, but you cannot delete the datas, if the tax office requires a complete presentation. The same for canceled orders. the old bakery works with the payment status: if the status say "cancelled", the script delete all datas from this invoice, but the (german) tax office dont accept this, you have to anonymised this datas)
The old bakery save the complete invoice with text, adress, prices etc. split this datas and use a separat customer adress database table and the order datas in another database table, seperated by customer-id. if now a customer say's delete my personal datas, change this datas, but dont delete it. All this is part of the customer account administration in the module
the old bakery add at first, if you add something to the basket, a data sheet with a invoice-id. if another customer come's in the same minute, he get the next id-number, but if somebody cancel his order, you've no order for this invoice-id and the script delete a empty order in the next 24 hours. Here you need a new method for identification, set the invoice-id as the last step in the order.
and some private words...
if you ask me, dont use the old code or parts from old bakery, separate code and output. it works fine with twig and templates. i add in my modules a template editor (edit area) and store the results in the database. i know, it is difficult, to change something in the module, if you use it also in a online store. i'm working since 2018 on a rebuild of the OneForAll-Module. OFA is a (code-)Mix between Bakery and News with some additional functions. I use the idea of OFA, but no part from the old code, i used this module online since 2018 to build lists with Time-controlled output in some projects, but it is not complete finish yet, maybe to 90%, there are only some small functions in the field type definition left, but it works for my projects and you've no pressure, to work on it :|
The same for a Bakery-Rebuild: there is no request for a minimized shop, everybody wants a "real shop system". So i use Wordpress && WooCommerce. Its a good working system and a good example for a own shop, but you spend a lot of time in this kind of module. I like to build something like this and i'm happy, to see, that its work and get bigger and bigger, but then, after a couple of mounths, i lost the interest. In the past I had a lot of health problems with numerous operations after an accident and every time afterwards you are out of the matter and lack the drive to carry on.
I hope you have more patience