datakick

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

@gandalf I don't think we can consider module to be badly-developed just because it uses php filesystem api. I personally have created a few modules that would be impacted by this (their content would not be synchronized by default). Now, there exists thousands of modules out there compatible with ps16/thirtybees. We can't really expect their developers to update them all, or force them to use some fs abstraction layer. It's just too late for that. That said, I still thing application layer is not the right place for this. Especially since there are very few merchants that would actually use this kind of feature.

@gandalf Application is not the right layer that should address this. In fact, it's not even possible with open system like thirtybees. We could fix all places in core that touches filesystem and change it to use this filesystem abstraction layer, but what about third party modules? Any module can use php filesystem functions directly, so this abstraction would be bypassed anyway. You would end up much worse -- some assets would be correctly synchronized, while others would not. And there's nothing thirtybees can do here -- we can't just force module developers to use our filesystem abstraction. If you want to sync files, you need to do that on different / lower level. Either at php server (php module that tweaks filesystem api), or at OS level (map thirtybees installation over distributed virtual volumes).

I think the main reason behind this request are the dynamically generated assets - regenerated thumbnails images, CCC css + js files, etc. But that's mainly infrastructure problem, and should not be solved at application level.

Out of curiosity - you do have dashboard's demo mode disabled, right?

You can migrate productcomments reviews to revws module, though

what do you mean by disconnect and reconnect to the frontoffice ?

@30knees this issue was already fixed in 1.0.21 / 2.0.3 release, please install latest version and test again

Main page is generated by index controller, so just enable left column for it:

FPC does not really work. I suggest you to disable it completely for the time being.

I've tested it and it works on my 1.0.7 as expected. Verify that you have themeconfigurator module enabled. You can also check that this module is in list of hooks called for left/right columns: