roband7

I do remember @mdekker writing someplace (I forgot where) that he wanted to make the installer and upgrader more robust before releasing 1.0.4. But all the latest commits have been all over the place except in these two components. So I'm also a bit confused about the plan...

We use the webservice API a lot. So far we haven´t had to change a thing when moving from PS to TB. For all practical purposes the APIs are identical.

I also get these "Internal Error. Oops! Looks like something went wrong!" Once every 2 or 3 weeks this happens for a specific topic, and I can then never open that topic without getting the error. Looks like a bug and/or config error in the forum software.

Technically it's quite possible to program a new core, while still leaving a compatibility layer for PS 1.6. Developers hate making stuff like that, but if there's a business case for it, it's sure doable.

Thanks for the update. I'll check out the RC when it arrives.

I have to set up a new shop soon, and planning ahead a bit, I was just wondering if a 1.0.4 release is planned soonish, say like before christmas?

The code in the paypal 6 module, in controllers/front/expresscheckoutconfirm.php, function assignCartSummary(), the assignment: $cart->idcarrier = arraykeys($deliveryOption)[0] Could that be the problem? Other code in core that picks the id_carrier from deliveryOptions does it differently.

I don´t have much to add really. The code looks for classes/controller/cbdom.php and that file doesn´t exist. You need to ask the people that develop the ccavenue addon.

The installation doesn't look complete, or it assumes you have done some sort of post-installation setup that you haven't done. It assumes the existence of: classes/controller/cbdom.php This file seems to be missing at your site. Was this addon perhaps just copied over from another site and you missed some files. Is there perhaps an addon install procecure you should have used instead? Probably better if you check with someone that supports the ccavenue addon than here.

Also, if the shop has: "Display unavailable product attributes on the product page" set to NO "Allow ordering of out-of-stock products" set to NO Then it also doesn´t make much sense to display out-of-stock combinations.

It's a known problem in 1.0.2. The easiest fix is probably to just copy classes/AttributeGroup.php and classes/stock/StockAvailable.php from github 1.0.x. There really needs to be a 1.0.3 release soon.

Crap, looks like the forum software ate some of the special characters in my post. Just check the similar function at the end of classes/Attribute.php, that one does it correctly.

Looks like a regression in 1.0.2, classes/AttributeGroup.php function getHigherPosition() was bugged by: commit bc9637ba9092ad0ba3a4d5c3744a068e025e58b8 Author: Michael Dekker git@michaeldekker.nl Date: Thu Jun 22 02:42:04 2017 +0200 Cleanup AttributeGroup To fix it, just replace: ->select('MAX(position') With: ->select('MAX(position)')

@vzex said in TinyMCE editor in the back office: @lesley said in TinyMCE editor in the back office: Are you still getting the 500 error when you try to upload images? Yes after a new clean install yesterday Does TinyMCEeditor require imagic module installed to add images because I did not install imagic Nothing in thirty bees needs imagemagick, it´s an optional module. For the 500 error surely you have something logged server-side. Check the log directory in your backoffice and/or the PHP error log.

I'm worried this topic is derailing a bit. @vzex Doesn't really want or need imagick. There should be no need to install the thirty bees imagemagick addon in his case. We just went down that road because of errors done by the host, the PHP install complained about an incorrect version imagick extension.