TracyS Posted August 5, 2010 Share Posted August 5, 2010 The developer of this contribution was able to tell by the readouts on the debug messages where there was a problem. Some of them are obvious and can at least show you how far your script is getting before a problem happens so you know where in the code to look to try and find why that problem is happening. I haven't used the debug through admin, I manually enter the php to print the results to see what they script is doing. Those print in the source code of whatever page you have the script on (typically at the very bottom of the source code). For example, in my catalog/checkout_confirmation.php I can put <?php echo '<!--DEBUG'; echo '<pre>Object order is: '; print_r($order); echo '</pre>'; echo'-->'; ?> Then you go through your site as a customer, place an order and when you get to the checkout confirmation page, view your source code to see what you have inside <!--DEBUG <pre> </pre>--> tags. It may help show you what is or is not functioning so you know what part of code to review. If I remember correctly, DCC isn't supposed to function with debug turned on (I don't remember for positive though)so you might try with it turned off as well as on and see if you get different results. Thanks, I'll try that. Though I'd rather know WHY the problem exists, instead of just mindlessly fixing it. Can anyone explain the debugging messages and how to view them? Quote ~Tracy Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.