30knees

@PedalmanGenau, das Gesetz fordert, dass du eben keinen normalen Link hast. Der Widerruf muss sich deutlich von anderen Links abheben. Daher die Entscheidung als Button. Deine Idee wäre widerrechtlich. Aber technisch möglich, ja.

Just in case there's even more of a delay with the release: https://github.com/30knees/tbsimplewithdrawal

Das Modul hat Codex gebaut. Hier die Antwort:

So sieht der Footer aus: So das Formular: Und so die Bestätigungsemail:

Werde doch nicht vor dem Stichtag wechseln, daher: https://github.com/30knees/tbsimplewithdrawal

A connector to a newsletter service, a modified connector to LexOffice to send Amazon invoices to LexOffice, and a connector to the ShopVote API. But these are already for PS 8.2.

@vincentdenkspelI said not just ... not just not. :) I have also created some modules that work. It's amazing!

Agree. But not just for development. I think it will also change shop systems. It might be that systems like Shopify will benefit more than standalone systems because of their data advantage.

I wonder how our paying shop customers would react to the excuse of: Hey, I work part-time on this shop and I am alone. Sorry for all that didn't go well. I don't think that's the right attitude. And I want you to succeed. I'm not being critical to be mean.

Ich wechsele das Shop-System und wohl vor dem Stichtag. Daher vorerst keine Beiträge von mir. Sorry!

Then the proper message you should communicate is: We need X amount of paying members to do Y. We have Z members. Or: We need X monthly income to do Y. We have Z monthly income. Don't just say: Become a member. Give people data, a funding goal, etc. You see that the calls to donate haven't been working amazingly. Try something new. And yes, it's hard work.

No. It is not that simple. I supported for a long time. I wasn't even able to get a simple approximate answer on when the promised updated Mollie module would be made available. Often, I didn't get even get an answer to questions. This included questions about me wanting to make some privately developed modules public in the hope that they might attract users to thirtybees.

I think @Kashir2000makes some good points. I am no longer a paying member and am moving away from thirtybees to Prestashop 8.2. I'm about half-way through the migration and I can tell that Prestashop is much less responsive and I am already annoyed by it. I would prefer to stay with thirtybees but the lack of modules for thirtybees (and PS 1.6 modules no longer being supported) is what drove me away. I can find the modules I need for PS 8. Of course, I could have the modules I need developed. I did that, in part. However, the only decent developer I found for thirtybees was datakick. He is just one person and mostly too busy to help in a reasonable amount of time with what I needed. I understand and don't have any hard feelings. It is how it is. I would love to stick with thirtybees. I want it to succeed. But, for me, unfortunately, it is a platform for people like @wakabayashiwho are developers and not for people like me.

Update: I turned off the datakick Bad Bot module and Varnish. Both shouldn't impact Googlebot but it looks like one of the two measures fixed the problem.

I see, thank you. I wonder what then is causing the Google issues of: 1) redirects with a 403 and 2) no desktop page available. These problems are inconsistent amongst all products.