yaniv14

try to change: $valuesQuery->select('id_feature, IFNULL(fv.custom, 0) as is_custom, COUNT(fv.id_feature_value) as count_values'); to: $valuesQuery->select('fv.id_feature, IFNULL(fv.custom, 0) as is_custom, COUNT(fv.id_feature_value) as count_values');

id_product_attribute is the default attribute id of the product, if the product has any attributes/combinations. if no attributes/combinations exists for the product it will return 0. when you do conditional check 0 counts as false. to be more accurate in the case will be better to check that the integer value of the id_product_attribute is greater than 0. the reason you cannot call same "object properties/array keys" like "combinations" is because those variables are in most cases injected to the templates as smarty variables by php code in specific parts. for exmaple: in product.tpl most of the variables that available in the template comes from ProductController (FrontController)

I believe you purchased a module for Prestashop 1.7 which is not compatible with ThirtyBees because ThirtyBees is based on Prestashop 1.6

if you are using webp than disable it.

try disabling friendly url

regarding image uploads you can check also php configuration "upload_max_filesize". in order for friendly urls to work you will need to have your webserver support it. in your case you are using Lightspeed so i believe it should be similar to apache and allow usage of htaccess file. but if I remember i was in discussion in a similar topic few years ago and it was not working because the shop was not on the root folder but instead was inside a folder, like in your case "/store/. regarding the core update not working, i can't help much. maybe @datakick can help... but I guess upgrading to latest stable version or even bleeding edge can help.

based on the error log you need to increase you php memory limit

It's depend on the webserver your hosting company is using. If its apache webserver than recreating your htaccess should do the trick, because apche setting can be overrided by htaccess file. if you are using nginx webserver than htaccess wont help because nginx dont allow external overrides and all rewrites rules should be in nginx conf file.

If its only category page you are looking for than you can probably do some hack in header.tpl something like. {if $page_name === "category"} <div class="col-xs-12">..... whatever you need from category.tpl file...</div> {/if}

check if you have any database upgrades you need to apply. also try to do hard refresh (ctrl+f5), maybe some javascript file has been updated.

maybe you need to run some database fixes/upgrades from the core updater module?

col-xs-6

can you paste the content of that file

Bootstrap 4/5 use flexbox compare to Bootstrap 3. Bootstrap 5 use pure javascript instead of jquery, have RTL support by using start/end instead of right/left... and also more scss utilities. in general Bootstrap 3 is too old for today web standards.

1.6.1.17 should be compatible.

If using apache web server try disabling mod_security

https://github.com/thirtybees/thirtybees#requirements

installing the module is not enough, you will need to install and run elastic search on your server. I dont have any experience with elastic search module, but if I remember correctly this module was never really fully production ready.

try to disable elastic search module

link?

Check that you have proper write permission for folders

There is no override to a theme template file (tpl). I dont think Niara theme will be update with the core update module. if you have future concerns just make a copy of the modified file and keep it aside

It looks like DHL has switched to a new API and maybe dropped support for older WSDL if you look in there main wsdl page you will see: <wsdl:documentation> NOTICE: This WSDL is valid for implementations that are in production prior to 14th March 2021. Please note that there is a new WSDL as part of the latest MyDHL API Developer guide. Please contact your local DHL IT Contact. </wsdl:documentation> i am not using dhl so I can't tell much. Good luck

xx_shop_url table

The reason that your migration fail was not related to thirtybees or prestashop, it was because you add an override with code that not supported by PHP 7.2+. I am not familiar with the migration process but I recommend doing it without your overrides (for start), and also after migrate you should continue updating to latest thirtybees version. regarding this error, I think you have something like: "private function getLangLink(.....)" when should have: "public function getLangLink(.....)"