datakick

As this is not a bug, I will not be releasing a new version to fix it. It is common that module template sometimes needs to be adjusted in order to work properly with your theme (or in this case with other module). You can simply edit file /modules/revws/views/templates/hook/home.tpl and change col-sm-12 to col-xs-12. Or, you could modify the template of the other module in a similar way.

The problem is that two templates, from different modules, use different bootstrap class. Bootstrap does not like this You need to choose which class you want (col-xs-12 or col-sm-12) and then edit and change one of the template

No, "Block Facebook Share" works only on product page. It should be simple enough to modify the module to work with cms hooks (displayCMSTop or displayCMSBelow), as the module does almost nothing. You should register selected hook in install section implement hook handler hookDisplayCMSTop -- almost copy of existing hook, only different way to resolve url for cms page

That's hard to tell, it depends on what modules you are using. For example, I've seen module thats send abandoned carts emails to raise 500 errors after the old carts were deleted. Some modules (for example my revws) uses guest table as a.persistent identifier to identify anonymous visitors (revws is using that to allow anonymous visitors to edit / delete their reviews. Pruning data from guests table will break this functionality). And there are more. To improve performance, on a clean installation without additional modules, it's safe to delete old carts (tb _cart, tb_cart_products, tb_cart_cart_rule,...) delete old entries from (tb_log) delete old visitor-related entires (tb_guests, tb_connections, tb_connections_source) prune tb_mail entries It can be hard to do that manually. There are modules that do that in a safe way on a regular basis.

Yes, it's safe

Indeed, the composer dependency of this module do not work properly with the composer dependencies inside core. We really need some way to have composer dependency isolated (to support different versions in every module). But that will be very hard task to implement. Meanwhile, I've released a new version of tbspreadsheetdatasource for thirty bees 1.6.0. Please update the module, and it should work again

The autoload directory is to add your custom css files, not for overriding existing css. But for css, that's usually what you want. Add your css rules that have higher priority, so browser will use it. For example, if the css rule you want to change look like this: .sf-menu { float: left; margin-bottom: 1em; } and you want to change margin-bottom, you can create css file that contains only change: .sf-menu { margin-bottom: 2em !important; } Browser will use all rules and merge them together. Because of !important keyword, the your custom value for margin will be used. So -- do not copy the original file, but only copy rules you want to change.

Your theme contains directories /css/autoload and /js/autoload. You can put your custom css / js files into these directories, and they will be automagically included.

Fixed in bleeding edge

It probably depends on mail transport module you are using. Old tbswiftmailer module delegates placeholder replacement to swiftmailer library (Swift_Plugins_DecoratorPlugin class), and this probably applies the replacement to subject as well. New tbphpmailer module does the replacement manually, and only for email body. I'm not sure if this is a bug in the module, or in core Tracked here: https://github.com/thirtybees/thirtybees/issues/1923

Names of front controller files should be lowercase, I believe. There was recently a fix for this https://github.com/thirtybees/thirtybees/commit/73bd67f18a143bf06fdc014302495ec7c77986f8 but for BC compatibility reasons (if you want module to run on older tb versions) you should use vouchercheck.php

I don't think so. Core controller still provide list of category pages to template, and niara/community theme displays them correctly.

Until thirty bees 1.5.0, CMS category description did not allow HTML content. We enhanced this in 1.5.0. However, old themes do not support this. You have to edit your theme cms.tpl file, and remove escaping. See this commit, how it was done in niara theme: https://github.com/thirtybees/niara/commit/402af237ecf99c5b9cb49e9316c54b88dd5b5c28 https://github.com/thirtybees/thirtybees/commit/09fcb66221a3ed14008c3476e1cfed1ff3d531d7 So this is not a bug. However, thanks to you I found different / related bug -- description displayed in the back office CMS category list needs to be striped from tags. I've fixed this, it's in bleeding edge now.

If you find any errors, please file github issues. The worst that can happen is that we will close it as a not-a-bug. Related to custompayment module - we have just released new version of module that fully supports image rewrite functionality. Mostly, buggy custom code for handling image upload/deletion was deleted, and everything is handled by the core in a generic way.

That's because you have enabled high dpi images - 2x dpi. Source image should be at least 2 times the size.

I've also updated core code in bleeding edge, to have better backwards compatibility with legacy overrides.

Replace this line with if (! is_array($error)) { $error = []; } $error = array_merge($error, $carrier_error); Core method variant allows $error parameter to have null value, and it properly handles that situation. Your override version does not - it's probably from very old ps16. Note: This override completely replaces the core version of getAvailableCarrierList method. There has been a lot of changes in that method (for example added support for min package weight), which will not work for you now. You should update the override code -- copy the current version from tb core, and apply the needed changes. Otherwise system will not work properly in all cases. This is not related to 1.6.0, though -- it's the same with 1.5.1 as well.

paste content of override/classes/Carrier.php

Nothing special, just update

What's the severity of that message? I doubt it's exception or error, it looks like notice or warnings. If so, than it probably won't be the root cause

Anything can cause that. Install collectlogs module, update back to 1.6, and then look what errors are collected.

Well, it must be placed somewhere, and everywhere it will block something. If you can't close it, it means that you have some javascript error in your back office, most likely caused by some module. That error is probably blocking execution of other javascript, and is therefore most likely causing problems elsewhere as well. This just made it more prominent. Fix your store.

id_cart in your cookie is set to null instead of an actual cart it. All places in core that writes id_cart into cat are putting integer value (not null), so there must be some module that did this.

The code works for me. Browser doesn't like it much, though. When you select multiple orders with invoices, and then click on multi-download, browser opens multiple tabs for every invoice. This is not a normal behaviour, and browser quite correctly treat this as unwanted popups. I had to click on 'always allow popup on this site' to make this functionaltiy work. Note: please remove this code from admin.js -- that is a core file, and should not be modified. The best way to implement these changes is using custom module. I've quickly prepared a very simple module that adds custom js file to all admin pages: backofficejs-v1.0.0.zip Just install it, and then modify file /modules/backofficejs/views/js/backoffice.js in order to add your code.

It depends on what type of voucher it is. It can be either: Single-Purpose Vouchers (SPVs) --- can be used only if the tax rate and the place of supply is known. So, if the voucher can be used only for products with standard VAT rate, and only in Bulgaria, than such voucher meet the SPV criteria. You can then collect VAT at the sale of such voucher, and voucher can be used as a standard discount. or Multi-Purpose Vouchers (MPVs) -- voucher can be used for any product, or EU-wide -- an actual VAT rate is not known at the time of voucher sale. Voucher must be sold without tax, and tax must be collected when the voucher is applied. Voucher shouldn't be used as a discount, but as a method of payment.