datakick

Are you selling virtual products? Because if not, you shoud have the same vat rate regardless of destination country - for regular products, your country tax rate should apply. If you are selling virtual products, then the only way to have the same final price is by using Specific prices. A lot of work

@Enev sent me the module, thanks for that. The module in question modifies the way product routes are handled in core - it overrides default product route that is defined in Preferences > SEO & Urls This is one of the few areas where thirtybees is intentionally not compatible (other areas are full page caching, for example).Thirtybees come with build-in 'pretty url' feature, so its dispatcher is very different from the ps16 dispatcher. This module attempt to hack it fails, unfortunately. From the module code it's obvious that this was always a friction point. When any friendly-url module was installed, this module stopped working, and additional hacks needed to be implemented. In the code you can find special cases for modules mpcleanurls, psseobooster, Advanced Url module, cleanurls, prettyurls. I'm afraid this is indeed not compatible module. It's up to its author if he adds compatibility for thirtybees friendly-url implementation.

guys, please PM me links to those incompatible modules, I'll check them and let you know. I'm quite curious what the problems are.

did the developer told you what he did to make it compatible?

and do those modules work on ps1.6?

Thirtybees require address to determine final price, tax, discounts, etc.

You need to edit Meta.php, method getCategoryMetas, lines ~ 443-449 https://github.com/thirtybees/thirtybees/blob/21b15c3e17188037e4862ddf357b6a3d65f1c3bd/classes/Meta.php#L443-L449 There are three similar lines looking like this: $row['meta_title'] = $title.$row['meta_title'].(!empty($pageNumber) ? ' ('.$pageNumber.')' : '').' - '.Configuration::get('PS_SHOP_NAME'); You want to edit these lines to look like this: $row['meta_title'] = $title.$row['meta_title'].(!empty($pageNumber) ? ' ('.$pageNumber.')' : '');

Not always. For example, when selling Electronically supplied services (for example selling ebooks, or software licenses), merchant must use customer's country VAT tax rate. Merchant must collect VAT, and either register and pay VAT in each and every EU country, or use MOSS scheme.

command line tool is not php extension. Install php extension. Something like this: https://www.digitalocean.com/community/questions/curl-is-not-installed-in-your-php-installation

I don't believe you have curl in php installed. That's the only reason this error can occur.

Are you logged in as an administrator?

There is prestashop 16 module. Have you tried that one?

you can replace $this->errors[] = Tools::displayError('Invalid Content'); with die(Tools::displayError('Invalid Content')); The result will be ugly white page, but that's ok, since this should be visible to attackers only

I don't think this is related. You should look to server log for any errors. Also check browser console network tab and look into ajax response content -- there are often some helpful information there. Also, don't forget to turn on debug mode in Advanced parameters > Performance.

I see that your site does not look so good. Looks like your modules were disabled / unhooked. You will need to go to Modules and reset each and every one of them, so they re-hook properly. This is one of the issues that was (to some level) fixed in 1.1.x. Too bad you updated only to 1.1.0.

1.0.8 is not latest version, far from it. And this version had few bugs regarding theme installations. Some of them were fixed or mitigated in 1.1.0 and 1.1.x. That's why I asked you to update to latest version -- it's possible your issue is already solved.

So which one is it?

First update to latest version of thirtybees, ideally 1.1.x - bleeding edge. It might sound scary to newcomers, but it's the most stable of them all. If it still doesn't work on latest version, file a bug on github.

That's not so simple. By introducing this class it become public api. Anyone could override it. Modules could expect it exists and use it... It's not much likely, but it could happen. By removing / renaming this class, we would create backwards incompatibility. And that's very much against he tb policy. I personally believe that, in this case, the functionality should be removed from core and moved to module. But if we decide to go this route, it needs to be done properly and safely. So the change won't take down anyone's server. You know, not the ps17 way.

core updater --> bleeding edge 1.1.x.

So you made it to thirtybees. Congrats. If the autoupgrade module is really not installed, it might be just some relics in your database. You can install one of my free modules - consistency checks - to get rid of it. https://store.getdatakick.com/en/modules/consistency

I'm sure it's not needed. Just give migration a go

What PS version are you on? You dont need to be on latest version to migrate.

This file looks ok. It should be config.xml with lowercase `c`, but it shouldn't matter much. The question is how the rest of the zip file looks like

Don't use it. Use redirect to stripe, and your flow should work correctly.