datakick

nowhere 🙂 In fact, this function is defined in product.js, which is part of your theme. But it's not guaranteed that this function exists in all themes -- it's really theme specific. Which is a shame. One of the great things that ps17 did is they introduced core javascript interface. Modules can use this interface to subscribe to events on page, and to modify content such as change attribute, etc. All ps17 themes support this. That makes ui development much more easier. TB should definitely introduce something similar, if you ask me

Call function getProductAttribute() every time you change attribute value. Something like this: document.getElementById('group_1').value = count; getProductAttribute(); That should do the trick

you can look into Advanced parameters > Logs, maybe there will be some hint there. Long shot, though...

You are assuming that users of the module are willing to participate in this discussion. Unfortunately, most of them aren't. I learned this the hard way -- most people on the forums are just silent leeches. And not only on this forum. But that doesn't mean that nobody use this module.

I don't think this feature is needed by (majority of) merchants. This functionality expects many people to actively work inside the ecommerce platform, which is not the case in most thirty bees use cases. Even when the company using tb is rather big, there are usually only a handful of people that needs to log in to ecommerce software. And they usually divide the responsibility vertically (few of them handle products, others process orders, and different team is in charge of cms). I agree this would be nice to have functionality. But I know about a lot of other areas that should receive overhaul first. Just my 2 cents

You should raise these objections as github issues. That way the author of the module will actually be notified. I doubt they will notice this forum thread.

you can safely ignore linting warnings for now. For development, all you need to do is install dependencies: npm install This also installs gulp. You can then run it like this: ./node_modules/.bin/gulp Gulp will watch your sass files, whenever you change any, it will automatically compile them to css on the fly. That's all there is, really

You are right, tb does not recreate them automatically. It should, but it doesn't. Maybe somebody will fix this bug in the future. Sorry for the bad advice. The correct advice is to delete the content of /cache/smarty/compile and /cache/smarty/cache directories

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

And what did you do right before you went to sleep ? 🙂

You should escape the value, otherwise some characters (apostrophe, etc...) can break the layout {$product->meta_title|escape:'htmlall'}

This can happen when there is a directory higher in the tree where you (your web server) don't have execute permission. If a parent directory has no execute permission, then user cannot stat any subdirectories (regardless of the permissions on those subdirectories and/or files). Anyway, this is not an application issue, it's server misconfiguration

It's definitely a good idea. It shows the problem at hand quite nicely - the whole directory /cache/smarty is not writeable, at least for your web user

delete /cache/smarty/compile and /cache/smarty/cache directories, and let tb recreate them.

disable JS CCC, and then check console again. There should be more user friendly stacktrace

Please file github issue.

Hi Dan, I'm afraid there's not much to do. Thirtybees (or prestashop for that matter) does not handle payment process in any way. Selected payment option is not part of cart final price calculation. In fact, in standard payment process, the thirtybees will learn about chosen payment option only *after* payment is completed (user is first redirected to payment provider, and then back to thirtybees/module specific endpoint that will validate and convert cart to order). This is very unfortunate flow, but it's what we need to use, for compatiblity reasons. I know that there exists some modules that, using plenty of hacks, can achieve some sort of surcharges for payment options. But these modules depends on lot of overrides, both in php and in theme. These hacks will not work with chex, not unless they were written for it in the first place.

Does the nochex module implement displayPaymentEU hook? Not all payment module do. You can check this by installing Advanced EU Compliance module, and enable its OPC -- I bet this module will not be listed there as well.

Yes, this is OK. In fact, it is how it was designed. This action never changes ID of customer. Customer ID parameter is used to figure out 'what' customer should be modified. In most cases, this should be bound to ID that trigger provides. Every trigger provides different set of data. For example, trigger 'After record has been created' provides information about created record (for example customer), including its ID. Trigger 'Before record is created' will provide similar data, but without ID -- record is not stored in database yet, and therefore ID does not exists. Trigger page view will provide information about page that visitor just opened. It's important to understand that Trigger and Action are not strongly related. You can use any trigger with any action, really. For example, you can create rule like 'If somebody visits url that contains word wheee then assign customer with ID 23 to group Visitors', and it would work. It doesn't make sense, but it would work just fine.

Hi, this rule would work, but only if you enter value '1' as a VAT number. You should use different condition, such as 'VAT number is not empty'

It's hard / next to impossible to adjust UI of html input file field. There's no cross-browser compatible way to do this, as far as I know. However, there exist a lot of libraries that handles this issue by rendering input field as hidden element, and doing the UI manually. For example https://www.dropzonejs.com/. It should be fairy easy to modify template and replace input file fields with the js implementation

The problem will be with mysql database user priviledges settings. Your db user doesn't have rights to create temporary tables. You should contact your hosting provider, and ask them to fix the permissions

https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_create-temporary-tables

You have probably enabled Advanced Parameters > Performance > Move JavaScript to the end option. If so, please file an issue in https://github.com/thirtybees/thirtybees/issues , as it would be a bug in core.

Well, you should see them in the page source