datakick

@x97wehner that's actually much more complicated than I thought. Review average is rendered using either displayRightColumnProduct or displayProductButton hooks -- what hook will be used can be selected in module settings page. It's possible to edit your product.tpl template and move one of these hooks to the appropriate place. For example, move this line. The problem with this approach is that these hooks are shared -- many modules can, and usually do, use them to display additional information on product page. So, if you move placement of this hook within template, you will be moving content generated by other modules as well. In other words - you can use this approach only if no other module is using this hook -- you can check in Modules > Positions. For example, in my case, if I move displayProductButtons hook it will affect Block Product Payment Logos module as well. I will add a new dedicated hook to the module for this particular use case. That way, you will be able to call this hook anywhere in the product template, and it will not impact other modules.

I've just attached one small module named revwsrecent to the first post. This module works together with revws module and displays recent reviews on your home page (in tab). It's really very simple module without any configuration or whatnot, but I thought someone might find it useful. You can actually see this module at work on my demo server

You don't need Google Analytics API module -- that one is used to fetch data from google analytics back to your store. It's not really that useful. Just install Google Analytics module, configure it, and you should immediately see visitors in your google analytics account

This is the hook code that renders the subscription form: ``` if (!$this->customerqty || !Configuration::get('PSSTOCKMANAGEMENT') || Product::isAvailableWhenOutOfStock($params['product']->outof_stock) ) { return ''; } $context = Context::getContext(); $idProduct = (int) $params['product']->id; $idProductAttribute = 0; $idCustomer = (int) $context->customer->id; if ((int) $context->customer->id <= 0) { $this->context->smarty->assign('email', 1); } elseif (MailAlert::customerHasNotification($idCustomer, $idProduct, $idProductAttribute, (int) $context->shop->id)) { return ''; } ``` If nothing is rendered, then the only explanations are: 1) hooks is actually not triggered -- please ensure that the module is enabled 2) Product Availability option is disabled in mailalerts module configuration 3) Enable stock management is disabled in Preferences > Products 4) product can be ordered even when out of stock (although this should be bypassed by your modification) 5) user is logged in, and has already submitted mail alert

@Pilou it is syntax error, and that has nothing to do with thirtybees or prestashop. It means that the code could not be parsed by php server There are two possible explanations: - you have made a typo when you copied the code - you run the code on different server with different version of PHP

Yet another version of this module is out. From outsider perspective not much has changed - some ui was moved around, and few bugs were fixed. But under the hood there were many more changes related to review types. Basically, this version brings support to review different types of entities, not only products. I will use this as a foundation to implement store reviews in the future (although that's probably going to be premium feature)

@30knees this error message is not really helpful :) But it seems that Mollie module should have a switch to display real error. Enable this option is module's configuration page and try again

@30knees the problem is in psograph.tpl template, and that's not part of the mollie module. First find out what module uses this template. The problem can be that these two modules can't work together - they both probably set the same smarty variable, thus creating conflict.

It's strange that ps16 module won't run on thirtybees. If there's some compatibility issue, it should be fairy easy to iron out, either in tb core or in module itself. I'd be happy to check your module compatibility for you. On related note - have you tried elasticsearch module? It might be good replacement, and it would speed up your shop as well

Sure, the module itself contains installation procedure

Good. I've created pull requests with the changes to master repository. It seems to be abandoned, though

Note: I've moved this to separate topic

@x97wehner edit this line and change it to look like this: php 'total_to_pay' => Tools::displayPrice($params['total_to_pay'], $params['currencyObj']),

@x97wehner I meant logs stored in file inside log directory: /log/20181120_exception.log

@x97wehner look into /log directory inside your thirtybees installation, there you should see the 'real' error message

Look into your webserver's error log, there should be some information about what's wrong

you need to reset the module. The tab is created during module installation --> when you change installation related code, you need to reinstall the module

Are you using default schema of urls?

Also, open javascript console, and if you find any error, copy and paste it here

You need to provide more information if you want our help: - firefox version - your operation system - thirtybees version - and most importatnly -- your url address

yep, that doc is a good start

https://forum.thirtybees.com/topic/1798/bcc-for-all-outgoing-emails/

@x97wehner I don't have 2checkout account, so I can't verify that the following will work. Could you please check Edit file /modules/checkout/controllers/front/validation.php and change line 40 from php Tools::redirect('index.php?controller=order-confirmation&id_cart='.(int)$cart->id.'&id_module='.(int)$this->module->id.'&id_order='.$checkout->currentOrder); to php Tools::redirect('index.php?controller=order-confirmation&id_cart='.(int)$cart->id.'&id_module='.(int)$this->module->id.'&id_order='.$checkout->currentOrder.'&key='.$customer->secure_key); That should do the trick

@x97wehner what payment module is that? Shouldn't be hard to fix it to work as other payment modules

also ensure that directory /config/xml/themes exists and is writable