WordPress.org

Ready to get started?Download WordPress

Forums

Error Log Dashboard Widget
Displaying from beginning of file not end (7 posts)

  1. barbfeldman
    Member
    Posted 1 year ago #

    I love the idea of this plugin, but it is displaying the OLDEST errors (from the beginning of the error_log) not the NEWEST errors (from the end of the error_log file)

    Is there an easy way to fix this?

    http://wordpress.org/extend/plugins/error-log-dashboard-widget/

  2. Andrey "Rarst" Savchenko
    Member
    Plugin Author

    Posted 1 year ago #

    This is odd, since it's whole point of it to display fresh ones.

    Could you provide example of log that exhibits the behavior?

  3. barbfeldman
    Member
    Posted 1 year ago #

    Looking at the time stamps in the dashboard, I see they are in the right order. But maybe the real issue is that it is not REFRESHING what I see in the dashboard?

    18-May-2013 17:32:34 UTC PHP Warning: unserialize() expects parameter 1 to be string, array given in /home/XXX/public_html/wp-content/plugins/wordpress-firewall-2/wordpress-firewall-2.php on line 567

    18-May-2013 17:32:25 UTC PHP Warning: unserialize() expects parameter 1 to be string, array given in /home/XXX/public_html/wp-content/plugins/wordpress-firewall-2/wordpress-firewall-2.php on line 567

    18-May-2013 17:32:17 UTC PHP Warning: unserialize() expects parameter 1 to be string, array given in /home/XXX/public_html/wp-content/plugins/wordpress-firewall-2/wordpress-firewall-2.php on line 567

    I put a copy of the error_log at this location:
    http://www.activitysheets.net/error_log.txt

    (NOTE: I removed part of my pathname for security)

    Thanks,
    Barbara

  4. Andrey "Rarst" Savchenko
    Member
    Plugin Author

    Posted 1 year ago #

    Not sure what happens. If I feed your logs as is to it I seem to get correct most recent entries in newer to later order:

    22-Jun-2013 19:45:41 UTC	WordPress database error  [...]
    22-Jun-2013 12:03:06 UTC	PHP Warning: Cannot modif [...]
    22-Jun-2013 12:03:06 UTC	PHP Warning: Cannot modif [...]
    22-Jun-2013 12:03:06 UTC	PHP Warning: Cannot modif [...]
    22-Jun-2013 12:03:06 UTC	PHP Warning: date() expec [...]
    18-Jun-2013 20:11:49 UTC	PHP Fatal error: Call to  [...]
    18-Jun-2013 09:49:03 UTC	PHP Fatal error: Call to  [...]
    18-Jun-2013 09:48:01 UTC	PHP Fatal error: Call to  [...]
    17-Jun-2013 09:42:40 UTC	PHP Fatal error: Call to  [...]

    There is no caching in plugin that could make it stuck.

    Are you sure you are looking at same log file in filesystem that widget is looking at? By default it gets file to display from ini_get( 'error_log' ).

  5. barbfeldman
    Member
    Posted 1 year ago #

    When I run phpinfo.php, it tells me that 'error_log' has a value of 'error_log' ... no other path info is included. And the error_log I am looking at is in the public_html folder, so basically the root of the site.

    I tried disabling W3 Total Cache .. that didn't seem to make a difference. And then I deleted and re-installed the Dashboard plugin. No difference either.

    ??

    Barbara

  6. barbfeldman
    Member
    Posted 1 year ago #

    I think I am looking at a different error_log!!!

    How do I verify which log it is getting? How do I modify which log it is reading?

    Barbara

  7. Andrey "Rarst" Savchenko
    Member
    Plugin Author

    Posted 1 year ago #

    When I run phpinfo.php, it tells me that 'error_log' has a value of 'error_log' ... no other path info is included.

    My guess would be that makes log relative to active PHP entry script file and since WP has several of them (admin is different from front end, etc) you probably have several logs all over from it.

    If you enable WP_DEBUG_LOG (see http://codex.wordpress.org/Debugging_in_WordPress#WP_DEBUG_LOG ) it will point logging to WP_CONTENT_DIR . '/debug.log' and widget will pick that up.

    But since that is public location and not really recommended to keep on you can just set different path via ini_set('error_log','path'); or filter error_log_widget_logs.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags