"Warning: An error occurred" and no debug logs

[emiLy]

I upgraded from 1.3.8 to 1.5.1 a few months ago and just recently the following started happening:

- After order confirmation, the user gets the "Warning: An error occurred, please refresh" message. The user hits refresh and the order gets submitted twice.

- Only one item from the order gets stored in the database, though all items get listed in PayPal or in Linkpoint.

I tried looking in both /cache/ and /logs/ for MyDebugxxxxxx.log and there aren't any in either place.

I'm not sure where to go next.

[picaflor-azul]

Make sure that you have the permissions set on your logs folder to be writeable.

Thanks,

Anne

[emiLy]

The logs directory is writeable.

[lat9]

Check to see that your host hasn't disabled the ability to control the error-reporting capabilities of PHP. Take this code:

<?php
  define('DIR_FS_LOGS', 'c:/xampp/htdocs/test/logs');
  
  $debug_logfile_path = DIR_FS_LOGS . '/myDEBUG-' . time() . '-' . mt_rand(1000,999999) . '.log';

/**
 * Error reporting level to log
 * Default: E_ALL ^E_NOTICE
 */
  $errors_to_log = (version_compare(PHP_VERSION, 5.3, '>=') ? E_ALL & ~E_DEPRECATED & ~E_NOTICE : version_compare(PHP_VERSION, 5.4, '>=') ? E_ALL & ~E_DEPRECATED & ~E_NOTICE & ~E_STRICT : E_ALL & ~E_NOTICE);


///// DO NOT EDIT BELOW THIS LINE /////

//////////////////// DEBUG HANDLING //////////////////////////////////

    ini_set('log_errors', '1');          // store to file
    ini_set('log_errors_max_len', '0');  // unlimited length of message output
    ini_set('display_errors', '0');      // do not output errors to screen/browser/client
    ini_set('error_log', $debug_logfile_path);  // the filename to log errors into
    ini_set('error_reporting', -1 ); // log only errors according to defined rules
 
 error_log ('did this get there?');
 
  
 echo 'log_errors: ' . ini_get ('log_errors') . "\n";
 echo 'log_errors_max_len: ' . ini_get ('log_errors_max_len') . "\n";
 echo 'display_errors: ' . ini_get ('display_errors') . "\n";
 echo 'error_log: ' . ini_get ('error_log') . "\n";
 echo 'error_reporting: ' . ini_get ('error_reporting');

Change the file-system path to that specified in your /includes/configure.php and save the file as some_special_filename.php in the root directory of your store. Navigate your browser to www.example.com/some_special_filename.php and make sure that the 'error_log" value displayed is the filepath that was set. Make sure to erase the file once you've run the test.

If the error_log directory doesn't match the DIR_FS_LOGS path, you should contact your webhost and ask them why they are preventing you from changing the error-reporting directives.

[emiLy]

Did that test (thank you!) and everything worked properly and it made a debug file in the logs folder. So apparently Zen Cart is not making the logs even though it should be capable of it. What do I look for next?

[mc12345678]

Did that test (thank you!) and everything worked properly and it made a debug file in the logs folder. So apparently Zen Cart is not making the logs even though it should be capable of it. What do I look for next?

While not privy to the plan considered by lat9 and anne, I would think something to try/check next wwould be to turn on logging for PayPal, attempt a transaction, and then turn off logging and report results (with whatever names obscured as desired.) Or if not at least that, then see if processing through a check/mail (sorry, forgot the specific term) to ensure that it is not something specifically ZC related.

[lat9]

Did that test (thank you!) and everything worked properly and it made a debug file in the logs folder. So apparently Zen Cart is not making the logs even though it should be capable of it. What do I look for next?

Re-check your /includes/configure.php file, to make sure that the DIR_FS_LOGS definition is exactly the same as the one you used in the test (no extra or missing /'s, for example).

[DrByte]

What's your PHP version?
What are ALL the plugins/addons/modules you've added to your site? (that's most likely where your problem is, especially related to checkout)
Do you get any of these same errors on the Admin side?