datakick

You have to set permissions for this webservice key in Advanced Parameters > Webservice 

Ha, this works for bankwire, but not for stripe module. Probably bug, will look into that.
Edit: bug in stripe module fixed by commit https://github.com/thirtybees/stripe/commit/a4dfcf933e5acab79a7ace3a416f65a898998bae. Will be part of the next module release. 

That's true, chex does not have such functionality.
Newest version of stripe let you sort stripe payment methods, so that can help.

This is google being stupid, that's all.
This warning is displayed when product doesn't have any reviews yet.
We obviously can't write any metadata about review (author, content, rating) because none is written yet.
We also can't write any metadata about aggregateRating - because what is the average of nothing? Allowed value for this field is in range of 1 to 5.
If we used 0, then google would complain that this not a valid value we could put some value from the allowed range, but which? 1 -- that's not good, because then the page would be displayed with 1 star in search 5 -- that's better, but we would be lying -- nobody gave us 5 stars yet. And google could, and would penalize your site for that. The only solution here, in my opinion, is omit the information completely.  

What you mean by "maybe by email address" ?
If the importer order has some sort of 'amazon' email address, you could use my conseqs module to block sending emails. You can use Before email is sent trigger + conditions + Prevent sending email action. Condition can be based on email type + recipient email address

Yes, that is the problem.
You have (for some reason) set your store to use PHP Encryption, but no encryption key is generated. No idea how this happened. 
Because no encryption key exists, thirty bees will raise the first warning: "PHP Encryption can't be used because _PHP_ENCRYPTION_KEY_ constant is not defined."
And fallback to Blowfish encryption. Blowfish encryption is deprecated, and raises the second warning.
The fix is very simple.
Go to Performance tab switch encryption to Blowfish. Save switch encryption to PHP Encryption Save That's it. When you change encryption from Blowfish to PHP Encryption, system will generate new encryption key if none exists.

I've just pushed this to bleeding edge.
Your body tag will now have class depending on selected context, for example mulstistore-context-all, multistore-context-group-1 or multistore-context-shop-2
You can add custom css into <admin_dir>/themes/default/css/overrides.css
body.multistore-context-shop-3 .bootstrap #header_infos { background-color: lightgreen; }  

This controller is available only after you enable Multistore feature in Preferences > General

Your thirty bees store has "trust store" file that contains root certificates of all trusted certification authorities. This file is outdated in 1.3.0, and does not contain new root certificate that Lets Encrypt uses nowadays. Which causes your store to not trust any servers that are using certificates issued by Let's Encrypt. Including thirty bees api server.
To fix this, all you need to do is update to latest thirty bees 1.4.0.
If you can't do that, then you will have to manually download the truststore file: https://raw.githubusercontent.com/thirtybees/thirtybees/main/tools/cacert.pem
and save it as /tools/cacert.pem inside your thirty bees installation. There should already be this file, you have to overwrite it.

Columns New client in order list is not stored anywhere. It just shows if the order is the first order created by this customer id. Every guest account has its own customer id, so it will indeed show true.
You can merge customer accounts with the same email addresses if you wish.

Module version 1.0.4 was not php8 compatible. Try new version 1.0.5

This module is not PHP8 ready. 
https://github.com/thirtybees/nocaptcharecaptcha/issues/12

niara theme (and probably others) has its own override for homeslider template that tries to pick images from /modules/homeslider/images/ directory.
You need to update this override template in niara theme:
/themes/niara/modules/homeslider/homeslider.tpl
changes are described here:
https://github.com/thirtybees/niara/commit/15e5338e628fca184a339d6cde66c961bfeb8169
or simply download this version and use it to replace the one in your theme: https://raw.githubusercontent.com/thirtybees/niara/15e5338e628fca184a339d6cde66c961bfeb8169/modules/homeslider/homeslider.tpl
 
 

Yep, this is a bug. Fixed in bleeding edge

What tb version? I believe this was fixed already https://github.com/thirtybees/niara/commit/f56c79cd8566f349dec81c40ce9c8cd2f5a41864

Thanks for reporting this. Actually, this particular issue is already fixed, and will be part of the next version of paypal module, when released

We have investigated together with @Coachonko, and there indeed was a bug in PayPalPlus submit controller. Fixed by commit https://github.com/thirtybees/paypal/commit/cd4f8a5ff3062539d5ca013abf0158ffe467e5eb. Will be part of next module release

it can be... a lot if things. I dont think this is application issue, looks like env misconfiguration problem. For example:
https://hpduy17.wordpress.com/2019/01/29/deal-with-swift-transportexception-when-sending-gmail-from-laravel-application/

There must be some error / exception during order validation process. Look into server error logs and inside /logs directory in thirty bees itself.

Advanced Parameters > Logs

Fixed in latest bleeding edge, thanks for reporting this issue.
https://github.com/thirtybees/thirtybees/commit/c024695e15c5a7f0f8c3b6fdf7859d150a577154
 

It's doable, but not very friendly. Look what static methods are available in Meta class. You could you getMetaByPage, or getCategoryMetas or getCmsMetas
{assign var='contactMeta' value=Meta::getMetaByPage('contact', $lang_id)} {assign var='categoryMeta' value=Meta::getCategoryMetas(4, $lang_id, 'category')} {assign var='cmsMeta' value=Meta::getCmsMetas(9, $lang_id, 'cms')} <pre> contact title = {$contactMeta.title} category title = {$categoryMeta.meta_title} cms title = {$cmsMeta.meta_title} </pre>  

Something like this:
<?php class Address extends AddressCore { // New function to get the postcode from the given address public static function getPostcodeByAddress($idAddress) { $idAddress = (int)$idAddress; if (!$idAddress) { return null; } return Db::getInstance(_PS_USE_SQL_SLAVE_)->getValue( (new DbQuery()) ->select('postcode') ->from('address', 'a') ->where('a.`id_address` = ' . $idAddress) ); } public static function getZoneById($idAddress) { // CUSTOMIZATION // Use the new function $postcode = static::getPostcodeByAddress($idAddress); // Minor islands and Venice if (in_array($postcode, array( "04027", // Ponza "80073", // Capri "09014", // Carloforte "98000", // Eolie, Salina "91023", // Favignana "58012", // Giglio "80070", // Ischia "07024", // La Maddalena "92010", // Lampedusa, Linosa "98055", // Lipari "91017", // Pantelleria "80079", // Procida "71040", // Tremiti "90010", // Ustica // Venezia begin "30121", "30122", "30123", "30124", "30125", "30126", "30127", "30128", "30129", "30130", "30131", "30132", "30133", "30134", "30135", "30136", "30137", "30138", "30139", "30140", "30141", "30142", "30143", "30144", "30145", "30146", "30147", "30148", "30149", "30150", "30151", "30152", "30153", "30154", "30155", "30156", "30157", "30158", "30159", "30160", "30161", "30162", "30163", "30164", "30165", "30166", "30167", "30168", "30169", "30170", "30171", "30172", "30173", "30174", "30175", "30176", // Venezia end "57031", "57032", "57033", "57036", "57037", "57038", "57039" // Elba ))) { return 10; // ID of the zone for these zip codes } // Livigno is even more expensive if (in_array($postcode, array("23030"))) { // Array because maybe more zip codes will be added in the future return 11; // ID of the zone for these zip codes } // fallback to original implementation return parent::getZoneById($idAddress); } }  

Thankfully, this being open source, you can easily edit htmlpurifier configuration and adjust it to your needs. See Tools::purifyHTML

This problem is caused by new column active in table 'tb_category_shop'. This column exits in bleeding edge only, so if you are back on 1.3.0 all you need to do is drop it:
ALTER TABLE tbp5_category_shop DROP active; But obviously, this module will no longer work on bleeding edge (or future versions of thirty bees). As @wakabayashi wrote, the module author did not specify from which table active column should come -- that's not really their fault, as at the time they wrote the module only one active column existed in context of this query. 
If you want to keep using this module, you will have to modify it, and fully specify table name / alias.