adammde

Hi Bill I used the copy method, but I think I must have missed that file, mine listed 4.1 as the version number, and the code was: // initialize the message stack for output messages require(DIR_WS_CLASSES . 'message_stack.php'); $messageStack = new messageStack; // set which precautions should be checked define('WARN_INSTALL_EXISTENCE', 'true'); define('WARN_CONFIG_WRITEABLE', 'true'); define('WARN_SESSION_DIRECTORY_NOT_WRITEABLE', 'true'); define('WARN_SESSION_AUTO_START', 'true'); define('WARN_DOWNLOAD_DIRECTORY_NOT_READABLE', 'true'); // START STS 4.1 require (DIR_WS_CLASSES.'sts.php'); $sts= new sts(); $sts->start_capture(); // END STS 4.1 Moved those lines as per your code, all is right with the world again, thanks :lol: Adam By the way, I've mostly lurked here and never needed to ask much, but when I have, I've been very impressed with the help and speed, thanks very much :thumbsup:

Hey Bill and everyone, I've been running MS2 with STS4.5.8 for a while, but a customer just notified me of a bug. He tried to edit his address, which was fine, but the final stage "continue" button led to the following: I have tried editing my test account information and adding new addresses, and I get the same error with every change I make. I even get the error when clicking "back" or "delete" as well as "continue". Any ideas? Thanks, Adam. EDIT: Further testing: It seems submitting changes to the account causes a logout - clicking the browser "back" button causes every site link to give the same error (catalogue entries, account button etc).

I put "wpcallback" in place of "your_script_here", and it works perfectly. The callback page looks like a dog's dinner without the lovely STS, but for the 3 seconds it's shown it's not a significant problem. As this appears to be a historical problem mentioned in this thread and many others, I'll put a few keywords at the end of the post so others with the same fault can find it easily. Thanks again Bill, Adam --- WorldPay , wpcallback , STS , callback fails ---

Bill, I updated from STS 4.5.2 to 4.5.8, in an attempt to fix the Worldpay callback fault as suggested on page 144 of the thread, however the fault persists. My installion is very simple: MS2+STS 4.5.2+Show Sub-Categories+Worldpay 1.9 I overwrote the existing files with those from STS 4.5.8 the MS2 and STS folders, then added back the box class and a minor mod to general.php to directly call my logo and to swap 'logoff' and 'myaccount' and remove the | All works fine up to the callback. I turn off STS, the Worldpay callback also works fine. I turn it on, I get this: ...And no order is received by the osCommerce backend. Is there a simple way to disable STS for the callback? Thanks again for the help :)

...and one more thing, I'm using MS2.2, not RC1. I've just looked at the packages and it seems 4.5.3 was RC1 only, but 4.5.4 and higher will work on my MS2.2 as well as RC1? Thanks again for all your help :)

Thanks for the insanely fast response :) The store is live, and I'm using an additional menu mod "Show Sub-Categories", is there anything I should watch for? Adam

Hi all :) I'm using STS 4.5.2 with Worldpay 4 1.9 and have run into the callback template problem. I've read many posts, the most recent of which was someone on page 70-something here asking if it had been resolved. I've seen code from 2002 - does this work with STS 4.5.2, or is there a newer known fix to disable STS for the callback? Thanks in advance and for the great contribs :) Adam

Look at this post first Bill, thanks for posting in my thread above. The contrib I was trying to get working with STS was the one found here: Show Sub-Categories I searched the forums for posts mentioning STS and Show Sub-Categories together, but found nothing. I didn't check the powerpack or trawl this thread. I'd imagine the powerpack includes something along the lines of Show Sub-Categories. Indeed, the problem was an erroneous closing </table> tag produced by the menu contrib. It seemed simpler to insert an opening <table> tag before $categories in the STS template to fix the layout issue, although finding the problem in the php would be better to remove an additional nested table. Thanks again, Adam.

Fixed: I loaded the page and read through the HTML output, and found a closing /table tag that shouldn't have been there. Unfortunately it wasn't clear which part of the PHP was writing it, so I simply inserted an opening table tag before the category menu in the STS template. Layout is now fine again. However a better solution would be to find the conflict between STS and the menu contrib to figure out where the closing /table tag is coming from... Adam

Hi all, I have been using STS and it works great... up until I tried using the Show Sub-Categories mod (latest version as shown here). After integration, all boxes stretch to 100% of the screen width, although functionally it's fine. Is this a problem of STS trying to parse the already-modded category list layout into a table, or did I mess up? Any help much appreciated! Adam