datakick

this could be theme issue. What theme do you use?

Let me explain how thirty bees installation works: first, php files must make it into destination directory. This can be done either by extracting thirtybees.zip file and uploading its content via ftp. This is the most common case. Alternatively, this process can be automated by some third party tool (softacoulous, etc) once php files are in destination directory, you just navigate to this directory using your browser, and start the installation process installer only creates and populates database tables done Now, as you can see, during installation the responsibility of this *crap* software is only to populate tables. If you complain about your root directory being overwritten, then this must have happened during step #1. Depending on what installing option you chosed, there are only two conclusions: if you uploaded content of zip file via ftp, then you must have fucked up, and uploaded to wrong destination. This is entirely your fault if you used third party tool (softacoulous, etc), then this third party tool fucked up. And I repeat - third party tool. Not created or maintained by thirtybees.

Glad I could help. Let's add some check and big warning into the module's back office page, so this won't happen to other users

If you look into your javascript console, you will find the reason: Live Stripe.js integrations must use HTTPS. For more information: https://stripe.com/docs/security#tls You have to Enable SSL , and you should also set automatic redirect from http to https version. Read here for more info

Abandoned cart is a time-based trigger, so you will need to setup a measure. It's an advanced concept, you need to have good knowledge of sql, and know the database structure of thirtybees. In this case, the measure would calculate age of every (non converted) cart. Then you can use 'Measure changed' trigger -- you can react on a situation when cart age changed from 9 to 10 days, for example.

That's not a bug. This means that urls for all known pages are already defined. Try to delete one first -- then you will be able to re-create it.

I'm afraid you will have to modify your theme templates, and comment out sections you don't want to display

They should. How did you cantact them?

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.