myDEBUG Backtrace [Support Thread]

[lat9]

My, my! That was fast ... v1.0.2 is now available for download!

[DivaVocals]

My, my! That was fast ... v1.0.2 is now available for download!

That's 'cause you got JUICE.. (pays to be behind the velvet rope!!)

[izar74]

Hi,

i got a strange report:

[25-May-2015 14:59:07] PHP Warning:  debug_print_backtrace() expects exactly 0 parameters, 1 given in /var/www/vhosts/.../httpdocs/includes/extra_configures/enable_error_logging.php on line 20

It should report something different instead of that, right?

In every debug file is the same regerdless the error reported after.

I checked the plugin file and it should be installed correctly... What am i missing?

[lat9]

@izar74: You're running on a PHP version less than 5.3.6, right?

[izar74]

@izar74: You're running on a PHP version less than 5.3.6, right?

ops, forgot to add the server configuration...

Yes, the server is actually using PHP: 5.3.3, is that the problem?

[lat9]

Well... it's the reason! The parameter was introduced in PHP 5.3.6.

You can edit the /includes/extra_configures/enable_error_logging.php file and its admin counterpart, changing the line that reads:

  debug_print_backtrace (DEBUG_BACKTRACE_IGNORE_ARGS);

to

  debug_print_backtrace ();

[izar74]

Well... it's the reason! The parameter was introduced in PHP 5.3.6.

You can edit the /includes/extra_configures/enable_error_logging.php file and its admin counterpart, changing the line that reads:

  debug_print_backtrace (DEBUG_BACKTRACE_IGNORE_ARGS);

to

  debug_print_backtrace ();

Thanks a lot :-)

[lat9]

I've submitted v1.0.3. This version calls the debug_print_backtrace function with arguments dependent on the PHP version ... so no more PHP warnings for PHP versions less than 5.3.6 (which are no longer supported, anyway).

If you're currently using the plugin on a later version of PHP, there is no need to update.

[lat9]

v1.0.3 is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=1879

[lat9]

I just submitted v1.1.0 for review. The information logged now contains the REQUEST_URI (actual page and parameters) and REMOTE_ADDR (the IP address) values active when the debug-log occurred.

There have been times when an issue occurs only on a specific page's access and/or when a specific IP address is accessing (like a script kiddie forcing out-of-memory conditions), so that additional information will help in figuring out what's going on when a debug-log occurs.