aris1234

I thought the order status change was a separate http (not HTTPS) call from PayPal which called: modules/gateway/PayPal/ipn.php So, I don't think the change being talked about here is related to that (please correct me if i'm wrong). The PHP fsock calls are when the shop software calls paypal to request processing of a payment - and this includes all the billing details, what was bought, etc. In my test in the sandbox - I think this part is working. The http IPN callback didn't work - but i'm not sure this is a separate issue.

Upgrading is easier said than done - particularly if you have a lot of modifications. If it isn't broken, i'm not fixing it

I tried it on the IPN sandbox and i'm not 100% sure it worked properly. It seems to have passed my details to PayPal correct, and processed the payment, but on going back to the store it said: Error: No payment gateway variable is set! To be fair, i've not tested with the sandbox before - so this could well be normal sandbox to CC3 behaviour.

IMHO any good application should have excetption handling which caters any eventuality - particularly ones on open systems where you do not know how or what might be configured or installed. CC already seems to check for xcache conditions - as it is CC which is presenting the error - so surely it could just say 'ah, a problem with xcache - we will just not use it'.

If it will work with or without xcache, maybe CC should just ignore it if not configured rather than give an error. I had to change the following in the xcache.ini file: [xcache.admin] xcache.admin.enable_auth = On [xcache] xcache.var_size = 100M

Does CC use xcache at all?

To be fair, I did re-download and re-install Turnkey - so it may well be a new version and changed though really - it is just Debian underneath. I didn't install xcache - it was just there. Nevertheless - it is an another scenario which needs to be catered for - surely CC can just ignore it? Those first steps when a user first installs a product are critical - if they mess people about, most will just toss it aside and move on.

I'm using Turnkey LAMP VM image in a virtual box to test/stage this. It is basically Debian - but pre-configured for specific scenarios - in this case, LAMP based apps like CC. As this is really just Debian - you may want to put checks in your installer to sort this out. I used the same to test a beta (either b1 or b2) of v6 - and never had this issue. Don't know what has changed.

Ok, so I had to edit the main xcache.ini file and set: xcache.admin.enable_auth = Off and xcache.var_size = 100M Surely this stuff should work out of the box, at least CC should cater for this condition.

Doesn't seem to work. # cat ini-custom.inc.php <?php ini_set('xcache.admin.enable_auth', false);

I see this at initial install, and every page afterwards even after install. Notice: XCache can't be used until `xcache.admin.enable_auth` is set to 0 in php.ini in /var/www/cc/classes/autoloader.class.php on line 130 Shouldn't the install script pick this up? Ok, so I can go into the global PHP.ini for xcache and switch it off - but that is global. Where is the best place to change this for CC only?

How do I delete of 'rest of world'? Essentially I want the following: Free delivery to UK Surcharge for delivery for items over a certain weight to certain postcodes (i.e. highlands, Islands and NI) Surcharge for delivery to other countries - and potentially certain postcodes within those countries - all based on weight. All other shipping requests should be refused. When I delete a shipping rate (because I can't edit it) and re-add it - it doesn't show in the order of weight - it shows in the order I added them. This is probably only cosmetic, but may confuse on more complicated configs.

Yes, I can delete them. Is this plugin ready for prime time? Another thing - in the zones menu: The radio box selections don't seem to correspond to anything useful. Is that a bug too? Additionally - when you go into zones - there is no easy way to get back to 'general' as the zones tab seems to disappear.

Ok, I created two methods in your demo system - but I seem unable to modify them. I can create new ones with the shipping weights needed, but when I try to edit one - it just reverts back to what it was before. Is this a bug - or because i'm using a demo system?

Any chance you could install the all-in-one module in your v6 demo back end so I can have a look? Never mind - I seem to have managed to do it myself