Support » Plugin: Post Views Counter » PHP Notice: Undefined index (v1.3.2)

  • Hi,

    Can you fix this PHP Notice: Undefined index in a new version release?
    Thanks πŸ™‚

    `Notice: Undefined index: in /wp-content/plugins/post-views-counter/includes/dashboard.php on line 164

    Stack Trace
    ———–
    1. Post_Views_Counter_Dashboard->dashboard_widget_chart(”)
    /wp-includes/class-wp-hook.php:287
    2. WP_Hook->apply_filters(”, Array(1))
    /wp-includes/class-wp-hook.php:311
    3. WP_Hook->do_action(Array(1))
    /wp-includes/plugin.php:478
    4. do_action(‘wp_ajax_pvc_dashboard_…’)
    /wp-admin/admin-ajax.php:176

    Context
    ——-
    URL : /wp-admin/admin-ajax.php?_fs_blog_admin=true
    Referer : /wp-admin/?edit=ws_php_error_log
    HTTP Method : POST
    HTTP Status : 200
    ajaxAction : pvc_dashboard_chart
    isSSL : Yes
    Current Filter : wp_ajax_pvc_dashboard_chart

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Erik Molenaar

    (@erikmolenaar)

    I am also getting one on property ‘colors’. Can this please be fixed in an upcoming release? Thanks for maintaining this awesome plugin!

    PHP Notice: Trying to get property 'colors' of non-object in /wp-content/plugins/post-views-counter/includes/dashboard.php on line 164

    Stack Trace:

    1. Post_Views_Counter_Dashboard->dashboard_widget_chart('')
       /wp-includes/class-wp-hook.php:287
    2. WP_Hook->apply_filters('', Array(1))
       /wp-includes/class-wp-hook.php:311
    3. WP_Hook->do_action(Array(1))
       /wp-includes/plugin.php:478
    4. do_action('wp_ajax_pvc_dashboard_...')
       /wp-admin/admin-ajax.php:176

    Context:

    URL            : /wp-admin/admin-ajax.php?_fs_blog_admin=true
    Referer        : https://www.myawesomesite.com/wp-admin/index.php?elm-log-cleared=1
    HTTP Method    : POST
    HTTP Status    : 200
    ajaxAction     : pvc_dashboard_chart
    isSSL          : Yes
    Current Filter : wp_ajax_pvc_dashboard_chart
    Plugin Author dFactory

    (@dfactory)

    Hey,
    Thanks for pointing this out.
    Should be fixed in just released 1.3.3

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.