Vers. 1.3.8: Entries in error log

  • bviadmin

    (@bviadmin)


    3 years ago

    Hi there,
    since update to 1.3.8 yesterday there are entries in my error-log:

    —————-

    [05-Nov-2021 08:43:41 UTC] PHP Warning: arsort() expects parameter 1 to be array, null given in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 708
    [05-Nov-2021 08:43:41 UTC] PHP Warning: Invalid argument supplied for foreach() in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 710
    [05-Nov-2021 08:43:41 UTC] PHP Warning: arsort() expects parameter 1 to be array, null given in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 708
    [05-Nov-2021 08:43:41 UTC] PHP Warning: Invalid argument supplied for foreach() in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 710
    [05-Nov-2021 08:43:41 UTC] PHP Warning: arsort() expects parameter 1 to be array, null given in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 708
    [05-Nov-2021 08:43:41 UTC] PHP Warning: Invalid argument supplied for foreach() in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 710
    [05-Nov-2021 08:43:41 UTC] PHP Warning: arsort() expects parameter 1 to be array, null given in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 708
    [05-Nov-2021 08:43:41 UTC] PHP Warning: Invalid argument supplied for foreach() in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-includes/plugin.php on line 710
    [05-Nov-2021 08:43:41 UTC] PHP Fatal error: Uncaught Error: Class ‘WP_Widget’ not found in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/includes/class-widgets.php:38
    Stack trace:
    #0 /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/post-views-counter.php(176): include_once()
    #1 /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/post-views-counter.php(116): Post_Views_Counter->includes()
    #2 /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/post-views-counter.php(661): Post_Views_Counter::instance()
    #3 /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/post-views-counter.php(666): Post_Views_Counter()
    #4 /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/includes/ajax.php(61): require_once(‘xxx/xxxxx/xx/…’)
    #5 {main}
    thrown in /xxx/xxxxx/xx/xx/xxxxxx/htdocs/WordPress_xx/wp-content/plugins/post-views-counter/includes/class-widgets.php on line 38

    —————-

    Deinstallation an fresh installation do not help.
    I downgrade to Vers. 1.3.7 and the errors are gone.

    Wordpress 5.8.1
    PHP 7.4.25
    Counter-Mode: JavaScript
    Exclude Visitors: robots, logged in users
    Strict counts: Checked – Enable to prevent bypassing the counts interval (for e.g. using incognito browser window or by clearing cookies).

    Greetings,
    Andy

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author dFactory

    (@dfactory)

    Thanks

    We’ll have a look into this

    keengamer

    (@keengamer)

    Yes, new version is buggy. It stopped completely to count views correctly. We have also our log full of errors. We just rolled back and it works fine.

    The problem must be connected to some settings, cache or who knows what. There was an error in the console related to jquery.

    Also, if we hit our page directly, the plugin ran fine. BUT if we went to our site from Google, using mobile view and using Pixel 2 XL from Google then this error was immediately visible. In my opinion Google uses some cache which is not working well now for you.

    Also, we use Cloudflare and we use automatic signed exchange https://blog.cloudflare.com/automatic-signed-exchanges/ Therefore some pages are loaded in a different way. This could be related to it. Or not.

    In every case we had to rollback to the previous version.

    Karel

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Vers. 1.3.8: Entries in error log’ is closed to new replies.