This was driving me batty, too! And it was the https in the HTTP_SERVER setting that I had overlooked EVERY time.
Thank you so much for this thread and the patient answers.
deb
This was driving me batty, too! And it was the https in the HTTP_SERVER setting that I had overlooked EVERY time.
Thank you so much for this thread and the patient answers.
deb
This used to work in the version 1.3 series.define('HTTP_SERVER', 'http://www.theeroticshop.net');
define('HTTPS_SERVER', 'https://www.theeroticshop.net');
define('HTTP_CATALOG_SERVER', 'http://www.theeroticshop.net');
define('HTTPS_CATALOG_SERVER', 'https://www.theeroticshop.net');"
It is a change in the 1.5 version that requires the 'HTTP_SERVER' to be 'https' for payment modules.
Same thing got me too. So I gues il just use a full ssl admin from now on. Perhaps the wiki page that the message links too could be slightly edited to inform paypal pro users that this is an essential step.
Wow, this is retarded i might say. I was staring at the code for 3 hours until I found that HELPFULL post.
Somebody seriously think admins are going to read comments? Come on. I would have to spend 10 year extra of my life if I would start reading comments on every code page I open.
I wish there were EXAMPLES in the code for HTTPS. that way anybody could quickly catch that HTTPS and HTTP servers both use httpS.
Anyway, thanks a lot for the answer. It saved me extra 10 hours I would spend on debugging the entire shopping cart. I already spent 5 hours yesterday figuring out why 2CO modules are not properly removed upon uninstall.