30knees

@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.

Thank you for the explanation. That means the feed is providing the correct URL, i.e. https://www.example.com/en/products/84/sample-product?combination=143 However, Google complains (at least, this is what the ad agency is saying) about the redirect that then happens to the URL with the # and is unable to index the page. I get a lot of errors saying that the page is not accessible to Googlebot. If this behaviour is standard, I don't understand how Google can be having problems because of the redirect from the URL with the ? to the one with the #. This would mean that all thirtybees/Prestashop users are having problems. Which would mean the ad agency is wrong in thinking that's the reason why Google can't index.

A different question: What URL do you provide to Google, the first (like it is for me) or the second: The feed outputs variant URLs such as: https://www.example.com/en/products/84/sample-product?combination=143 When this link is opened, the shop performs a 301 redirect to: https://www.example.com/en/products/84/sample-product#/72-size-large

Same as wakabayashi for us.

Is anybody else also suffering from this unable to view store on desktop issue? https://support.google.com/merchants/answer/12158123?hl=en I’m using a module to send product URLs to Google Merchant Center (Datakick). The feed outputs variant URLs such as: https://www.example.com/en/products/84/sample-product?combination=143 When this link is opened, the shop performs a 301 redirect to: https://www.example.com/en/products/84/sample-product#/72-size-large This means the query parameter ?combination=143 is replaced by a hash fragment. I don't know whether this is the problem or whether it's something else.

Ich würde über einen Drittdienst gehen, d.h. Shop irgendwo anbinden und die leiten dann alles an DHL weiter.

I am forgetful. See here: It does indeed only affect products without reviews.