datakick

Out of curiosity I have created a test product, with base price = 100. I set not tax for the product. I then set quantity discounts in the same way you did. My result: It looks like it works correctly.

@haylau From the information you provided I don't really understand what is wrong, or what expected values should look like. Plese provide more detailed information: product base price discount settings expected results actual result It would be best if you could reproduce the problem on vanilla installation of thirty bees, to ensure that the problem is not caused by some of your modules and/or overrides. Thank you

That's a good question 🙂 I guess it was the easiest solution at a time. I agree we should get rid of these third party service dependencies. I filed an enhancement request on github for this one to not forget it

You are right, making it not visible really break javascript. That's insane. Please file bug on gitub (although that will fix the issue in niara/community theme) You could try to fix it yourself. Edit file product.js, find function findSpecificPrice, and remove this: .not(':hidden'); This is second similar issue I've seen lately. We really need to implement some javascript data layer for themes, and not depend on data stored in dom.

Are you sure that hiding section using css blocks the functionality? That would be very strange. Try again addding 'hidden' class, or setting style display to none, on section with discount table

What functionality do you guys need from such sync module? Is it one way, or two way sync? Orders, catalog, mapping, price management,... ? If we coould put together scope, some dev (maybe me) could pick up the task.

Maybe you have found bug in bing engine 🙂

I looked in the source page and there is no link containing p=2?p=2 anywhere, so this doesn't seem to be related to build-in paging mechanism. Most likely there is some link somewhere in the web (not necessarily on your site) containing this bad url parameters. You need to look at your site and check everywhere if you could spot this link, and fix it. If the bad link is on third party website, well there is not much you can do. You could propose fix to FrontController that could gracefully solve this situation.

Yes, you shouldn't encounter any issues or problems Nope, core update does not touch third party modules at all

Oh, I found a bug in the server tooling. @ariom please try update now

What version of core updater do you use? I just tried it, and it works fine for me. In server logs I can see that your core updater module sends request to list content of revision 1.1.x, but that doesn't exists anymore. But your module evidently believes it does, which is strange. Maybe some caching issues -- try to delete file /cache/GitUpdateStorage.php and try again.

What languages do you have installed in your shop? What is the actual warning/error message?

Every action have some parameters, and you need to somehow provide values for these parameters. The easiest way is to use Constant value - every time the action run it will pass this value as action parameter. Sometimes, you need to provide dynamic data. For this, you can use Bind -- you will bind parameter value to some information provided by Trigger (Every trigger provide different set of information). For example, trigger 'Stock quantity changed' provides information about 'new quantity', and you can use this information in action. Interpolation is something between Constant and Bind - you provide constant text, but part of this text will be replaced with dynamic values from (possibly multiple) action variables. This is useful for example if you want to construct email subject like "Hello {{firstname}}, your order {{order.reference}} has been shipped" Note that when you writing value for Interpolation, you need to pres @ and then select the variable to be inserted. And that's all. Simple.

@SLiCK_303 / @30knees - you know, just a regular maintenance you already do on your own website. Upgrading to new versions, installing selected thirtybees modules, setting up products etc -- with the goal to showcase most of the thirtybees features in an appealing way.

Is anyone willing to help maintain the demo sites? I'm sure there are a lot improvements that could be done, but unfortunately I don't have time to do it.

Try to edit file /modules/opartdevis/opartdevis.php, line 87, and change Configuration::updateValue('OPARTDEVIS_SHOWFREEFORM') to Configuration::deleteByName('OPARTDEVIS_SHOWFREEFORM');

Hello everyone, if you are still running your store on PHP 5.6 then please note that thirtybees version 1.2.x is the last one to support this version. Since thirty bees 1.3.0 we will require php 7. You still have some time to upgrade your php environment. You shouldn't encounter any problems or issue, as version 1.2.0 is fully PHP 7 compatible.

file permissions maybe?

I'm running latest version of paypal module on my demo site and it works just fine for me. You can check yourself https://demo.getdatakick.com If it doesn't work on your site then there must be some interference there

This will be fixed in next major version

No. I originally wanted to implement this functionality into the datakick module, but I dropped the idea. I'm not sure how big of a market is there for such module.

@moaai Yeah, I know that this is the 'common presta' way to implement custom fields, unfortunately. I have seen this kind of recommendation in many posts on prestashop (and even on thirtybees) forum. But that doesn't make it right. Object model definition is a shared class property, not instance property. Constructor (or any other instance method) should not modify it. Redefining the whole property in product override is not an ideal. It can cause a lot of problems in case we change the model definition in core. But I believe it's a lesser of two evils. Regarding restoring the original code in initProcess method -- I (reluctantly) agree to do that. This code was removed probably because the object model is instantiated later (int processSave or processAdd method) anyway. But the instantiation is conditional -- i the object already exists, it will not be loaded again -- so it should not pose any performance issue. And it will make thirtybees codebase a little bit more compatible. I still don't like it because it feels like rewarding bad behavior 😉 The code will be in bleeding edge soon.

Yep. main branch represents future major release (1.3.0). All new features will be committed there. Updating to this branch will give chance to test you new functionality early on. you could also use 1.2.x branch. This is a bleeding edge for upcoming bugfix release 1.2.1. This branch will not contain any new feature work, only selected bug fixes

This is not a problem with tbupdater, this is some other issue with your server. Your thirtybees is probably using wrong version of GuzzleHttp library. This library is part of /vendor directory. First, check (using core updater) that this directory is properly synchronized. If it is, then there is probably some module that includes old version of GuzzleHttp library, and thirtybees is using this version instead of build-in version.

Yes, unfortunately that happens sometimes. There can be various reasons why this happens: Your customer might close the browser before the redirection is done they can have some browser 'security' plugin installed that prevented the final redirect if you use cloudflare (or similar) then they could have mark your visitor as an attacker and block the access to your site your server could have been overloaded and did not accept new connection at the time there could be error inside payment handler on your site etc... All you can do is look into the server logs (both server and thirtybees logs) to see if there was any error in the timeframe of the payment