datakick

This is not build in functionality.
You can use my conseqs module to create a rule to send email when new recort 'Order Return' is created.

This is unnecessary strict server settings. You should reconfigure your server to allow SAMEORIGIN for x-frame-options header. Your server currently returns 
X-Frame-Options => DENY 
 
 
 
 
 
 

No, this is not supported. You can disable ordering out-of-stock items, but they are still displayed in categories.
You can either
edit your theme, and simply omit out-of-stock items from listing periodically run SQL update query to hide products that are out of stock. Something like this might work (please test) UPDATE tb_product_shop SET visibility = 'none' WHERE (SELECT SUM(quantity) FROM tb_stock_available sa WHERE sa.id_product = tb_product_shop.id_product) <= 0;  

There you go.
There you go. Looks like you have copied AdminProductsController.php to override/controllers/admin directory sometimes in the past, modified it slightly, and forgot about it.
I suggest you delete this file.
You should also investigate what it was that you modified, but I don't see many changes in the file.

One of the reasons the pdf can be so huge is the used font. You can tweak used fonts in file classes/pdf/PDFGenerator.php, property $font_by_lang.
For example, deleting line 
'en' => 'dejavusans' Can reduce pdf size from 461K to 15k.
Of course, the resulting pdf might look different. Or completely broken, if your language contains weird characters such as 'příliš žluťoučký kůň'

Not possible. Just... no.
The only way this could happen is if your browser sent two ajax requests to install theme. That's very unlikely. Very, very unlikely. 
Unfortunately it's possible, but only if you have some very weird caching browser extension, adblocker, etc. Or maybe some server redirection.... who knows. 
Look into browser console, Network tab, and see what requests are send during installation. There should be only one request with installTheme=true

I've installed it on my test thirty bees, configured, and it works properly. What does not work for your?

Hi @SeaSky, 
unfortunately this is not possible with the current module. This kind of data are not exposed
Petr

This is already fixed bug. You can either update to bleeding edge, or apply this fix:
https://github.com/thirtybees/thirtybees/commit/a7cd6399183897306cbbd77cac13a4f525344bb8
 
 

Yeah, import works for me just fine:

There must be some bug, modification, override, or whatnot in your system. Once again, I strongly recommend update to 1.1.x

The code is perfectly fine, there's nothing wrong here. It just adds additional table to the query that fetches orders. 
The problem is that your database select bad plan to execute this query. The solution is to help the database -- create index that it can use to optimally retrieve data. Something like this:
CREATE INDEX mp_order_reference ON tb_mollie_payments(order_reference); With such index the query will run much faster, probably

Please don't do that, this is one of the most important part of the code. It's like replacing car engine because your 'Check engine' light is on.

data inconsistency in database. You can download my consistency check module, that might help you fix it

Thirtybees require address to determine final price, tax, discounts, etc. 

Go to 'Customer groups', and check enabled modules for each group

This is a bug in the core, thanks for bringing this up
https://github.com/thirtybees/thirtybees/issues/1242

You didn't get the idea of a multistore at all.
Multistore means that you have only one installation that handles all your stores. These stores can have different domains associated, you just need them to point to the same IP address you thirtybees is running on. When visitors visits any one of these stores, thirtybees will determine the correct shop context from the url, and will serve content from that shop only.
Of course, you can decide if your mutli-stores will share products, customers, orders, etc. You can set it as you wish. 
The main benefit of multistore is that you can manage everything from one back office

Not a bug. You just need to fix your installation.
In this post thread:
you wrote that consistency check found extra file: /classes/db/DbMySQLi.php. Now look what file is this exception complaining about. If you have removed this file as suggested, you wouldn't have this issue.
A little explanation: translation tools load all php files in /classes directory in order to find translatable strings. They load even extra files that are not part of official thirtybees release. In your case, it loads ancient remnant from ps16 - DbMySQLi.php was part of prestashop 16, but is no longer supported by thirtybees. You should delete it.

Well, the problem was that you enabled Advanced stock management, but didn't associate your products with warehouses.
After I disabled this feature checkout works just fine.

If you want to use this feature, you need to
create warehouses associate warehouses with carriers associate products with warehouses (and locations)

Try to restore original IP address, as described here:
https://support.cloudflare.com/hc/en-us/articles/200170786-Restoring-original-visitor-IPs-Logging-visitor-IP-addresses-with-mod-cloudflare-

Clear all caches. Browser, server, and cdn (cloudflare??)
 

Delete cache/class_index.php
 

The problem is that there is some module with long controller name. Controller name is used to compose page key in form:
module-<module_name>-<controller_name> for example
module-paypal-plussubmit Thirtybees has limit 64 characters for these meta page entries. If (( module name lenth + controller name length + 8 ) > 64) then this error is thrown, because the resulting page key can't fit database column.
This limit is obviously too small, we should increase it for the next version of tb. I've created github issue to increase this limit.
Meanwhile, you can do this to fix the situation:
Edit file classes/Meta.php and change size of the page property to 128:
'page' => ['type' => self::TYPE_STRING, 'validate' => 'isFileName', 'required' => true, 'size' => 64], to
'page' => ['type' => self::TYPE_STRING, 'validate' => 'isFileName', 'required' => true, 'size' => 128], You will also have to connect to your phpadmin and modify table schema (you might need to change table name tb_meta according to your database prefix):
ALTER TABLE `tb_meta` MODIFY `page` varchar(128) NOT NULL;  

You will have to modify the module code. Simply change this line to 
$category_products = $category->getProducts($this->context->language->id, 1, 100, 'price', 'DESC'); That should do the trick. If you do this modification, you can't update the module to newer version. The easiest way to ensure this is to change module version to some very high number, ie 100.0.0. That's a hack, though. It would be very nice to have an option to *lock modules* in tb core

Disable debug mode, or upgrade thirtybees to 1.1.0.
I've also filed an issue for this to be fixed within the module:
https://github.com/thirtybees/advancedeucompliance/issues/10