datakick

This will be caused by some CSS in your theme, they probably interfere with the module layout. It looks fine on my theme:

Should the checkout process be really concerned about cross-selling, though? You can already recommend related products directly on your product page, or on the added-to-cart popup. Isn't it enough?

Could you share screenshot, or have you already fixed those issues?

Thank you for the contribution. Unfortunately, the module can't be installed, as there is some syntax error: syntax error, unexpected ')' in file modules/vegasslider/vegasslider.php at line 292 When I fixed that, I got another errors when I tried to save the module settings: Call to undefined method VegasSlider::clearCache() in file modules/vegasslider/vegasslider.php at line 411

What is your reason not to upgrade the module? I do think it's important to update before the deadline. The fact that it's not yet required by law doesn't mean that some of the banks and other institutions won't be using these new security features. After all, this does bring benefits to both card holders and card issuers. And they have invested significant resources to implement them. By using checkout flows that does not support SCA you are opening yourself to the risk that some payments will be declined.

Not at the moment. In fact, most people don't even see this tab. Markus doesn't want this new feature to be available to general audience yet. Core updater version with this feature is no longer available for update. And those who updated during the brief time that was available (as you did) can't use this new feature as well. That's because core code was updated to not support database changes detection. Anyway, if you want to test it, I'd be glad. All you need to do is forward your code to bleeding edge add this line to /config/config.inc.php -- as shown in this commit define('TB_OBJECT_MODELS_AUTHORITATIVE', true); With this constant, your version of core updater will enable the database schema comparison tool. If you migrated from prestashop, or even if you come from older version of tb, you should see plenty of database differences. Most of them should be benign, though

You don't need to change your theme. You just need to fix few lines in your current theme.

Yes, it works in multistore. You can assign different cloudflare zone to each store. When you clean cache in store context, it will pick up the right zone to purge.

No. This is really just a simple tool to purge *all* cloudflare assets together with prestashop cache. I agree that it would be much more useful to continuously watch files on server and invalidate modified ones, but that would be too much work. This is good enough for me (and I implemented this module primarily for myself and my clients, as it drives me crazy to constantly flush the cache 🙂)

I have released new simple module to purge CloudFlare cache every time you clean cache in your back office. If you are using CloudFlare, I'm sure you know how annoying it is to login into your CloudFlare account to purge cache whenever you change something in your store. This module can help with that https://store.getdatakick.com/en/modules/cloudflare-cache-purger

If you use template that correctly implements product metadata (almost all of them do), then review stars will be eventually displayed on google. Note that it takes some time for google to crawl your site and index new content. It can even take few weeks, or months. Even if you submit sitemap file highlighting recent changes on your site, it's ultimately google's decision how often they visit your site... they have a big queue 🙂 For example, if you google "datakick site:store.getdatakick.com" then you'll see Which says this module has 5 reviews. In fact, this module has 9 reviews right now. So, google hasn't indexed this page since 2019-08-05 (date when the 6th review was added). So, my advice is to be patient

New version 0.6.0 has just been released with following new actions you can use to create your rules: Remove customer from group Associate product with category Remove product from category You can now create rules like add product to Featured category when its price is > $100 remove product from category Featured when it is sold out When customer purchase product Club membership then add customer into group Premium,and remove customer from group Customer

As I wrote before, there's no plan for this. I have added this to my backlog, but it doesn't have the priority at the moment. I don't follow

Should be easy I don't plan to implement this.

Fast forward two months. Number of patrons dropped down to 22, and total amount pledged dropped from $670 to $195. That is encouraging.

There are still many bugs. Some old bugs were fixed, some new were unfortunately introduced (had the community tested the release preview versions, we could have avoided lot of them...)

Tracked here: https://github.com/thirtybees/thirtybees/issues/1040

New version 0.5.0 - FIELDS MANAGEMENT I've just released new version of chex module. This new version allows you to manage entry fields: you can now hide fields you don't need in checkout form (for example company name or vat number) you can create your very own custom fields. For example custom GDPR checkbox There is a plan to further extend this area. In future version(s) I plan to add ability to define custom layouts (move fields around) edit build-in fields (rename label, placeholder, required state, etc) actually save custom field values. Although you can now create your own custom fields, entered values are NOT stored anywhere. So, apart from required checkbox that can be used to prevent form from being submitted, it's pretty useless at the moment. Also, this new version of implements better persistence for entry fields -- for example, selected country/state is now remembered and survive page reload. You can test on my demo account, or download from my store

check that database table <PREFIX>_stripe_review exists and contains all required columns CREATE TABLE `tb_stripe_review` ( `id_stripe_review` int(11) NOT NULL AUTO_INCREMENT, `id_order` int(11) unsigned NOT NULL, `status` int(11) unsigned NOT NULL DEFAULT '0', `id_review` varchar(255) DEFAULT NULL, `id_payment_intent` varchar(255) DEFAULT NULL, `id_charge` varchar(255) DEFAULT NULL, `captured` tinyint(1) DEFAULT NULL, `test` tinyint(1) DEFAULT NULL, PRIMARY KEY (`id_stripe_review`) )

I'm not saying it's not caused by tb. I'm saying that, since it is an intermittent issue, it can also be caused by something else. And until there exists repro-steps one can follow to reproduce the bug, I will continue to think so 🙂 This was never an issue, this was just unnecessary log line that caused panic. This line was added to system log whenever user loaded *any page* immediately after cart was converted to order. At that moment, cookie still contained id of old cart. Thirtybees (prestashop) reacted on this situation by creating new empty cart, and by displaying this *error message*. But it's not an error, it is an expected workflow. This was *fixed* by deleting the code that logged this line. Nothing else 🙂

Note that it's not necessarily tb fault. Since it is intermittent issue with no repro-steps, the root case can be somewhere else. For example misconfiguration of server. Say, during peak hours HTTP requests can be dropped by apache/nginx, php server might not be able to create connection to database, etc... these would result in http requests returning 500 error code (and thus ignoring paypal callback) Of course, this could be mitigated, or even completely fixed, by rewriting paypal module. For example, the module could proactively fetch all completed transaction via paypal API, and check that all of them has been processed. But that's a big refactoring, and I'm afraid that tb guys don't have enough manpower to achieve that

that's not fix. You just made your site harder to upgrade. Use override. Optionally you can install my conseqs module and create rule to block this kind of email.

That's because this commit was to master branch, which corresponds to version 6.0.0. That version was released for a brief period of time only, as many people had issues with it. Since that time there was some development on 5.x.x branch, and couple of 5.x.x version releases. Unfortunately this branch still has the issue mentioned in this thread. I don't know if there are any plans to revive 6.0.0 work and fix it, or if the plan is to continue development in 5.x.x branch. That's up to thirtybees developers to decide.

I also think that it's not really necessary to have separate checkbox for GDPR (in checkout). I have even wrote an email to the bureau that oversees GDPR implementation in my country, and they confirmed this. Data provided during checkout are considered either - required by law -- business entities are required to collect some personal data for tax and accounting purposes. These are the data displayed on invoice - name, address, etc - legitimate interest -- businesses have legitimate interest to collect additional personal data, such as email or telephone number. These are to protect against fraud, to ensure product deliverability, etc... for example, you need phone or email to contact your customer if you discover later that you are unable to fulfil the order. As long as all the personal information you are collecting during checkout can be in one of these two categories, you don't need any consent. You just need to inform your customer about it, for example in your terms or privacy page. Of course, if you collect some PI that doesn't match these brackets, then you need consent. Example is age / date of birth. Unless you are selling alcohol or tabacco, you don't have any legitimate of legal interest to collect this info - you need consent. Anyway, I'm not here to discuss about GDPR. And I don't want to force my ideas on anyone. I decided to add new feature to the module -- custom consent checkboxes. You will be able to create as many checkboxes from back office as you want. That should fix it