Viewing 8 replies - 1 through 8 (of 8 total)
  • cavemonkey50

    (@cavemonkey50)

    That error points to an issue with authentication. Are you having trouble authenticating with Google, or have you authenticated a Google account that does not have any Analytics accounts associated with it?

    cavemonkey50

    (@cavemonkey50)

    This also points to the experimental function get_analytics_visits_by_page. How are you using this function?

    Thread Starter Steven Vachon

    (@prometh)

    Everything’s been authenticated.

    I wasn’t having this issue before updating to the latest version, and I’m using it in a very simple fashion:

    get_analytics_visits_by_page($current_url, 99999);

    cavemonkey50

    (@cavemonkey50)

    Thanks for the clarification that this worked fine before the update. I have an idea now of what’s breaking the function, and I apologize for not completely testing that function.

    Right now, I’m planning on releasing a bug fix this weekend at the latest with any bugs that have cropped up since release. I will make sure this is fixed for that release, and if I have any trouble reproducing the issue, I’ll respond back here.

    For now, I believe the issue is related to a variable not being set. By setting $_POST[‘token’] to the token found in your database, it should solve the issue if you’re looking for a temporary workaround.

    For the future, I do have a much better stat system planned that will make getting stats like page visits and other API data a breeze with themes. The system is prototyped out; it’s just a matter of finding time to code it. When I do get around to writing the code, would you be interested in helping beta test the new system?

    Thread Starter Steven Vachon

    (@prometh)

    Sure, I’d be glad to help. I’ve actually been somewhat anxious about it since you first released the function in v6.0

    Is this the same bug that shows up in the Settings part of the plugin too, where the roles to track and not are listed with checkboxes?
    I get the following series of errors:

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/htdocs/wp-content/plugins/google-analyticator/google-analyticator.php on line 362
    /> Administrator

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/htdocs/wp-content/plugins/google-analyticator/google-analyticator.php on line 362
    /> Editor

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/htdocs/wp-content/plugins/google-analyticator/google-analyticator.php on line 362
    /> Author

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/htdocs/wp-content/plugins/google-analyticator/google-analyticator.php on line 362
    /> Contributor

    Warning: in_array() [function.in-array]: Wrong datatype for second argument in /var/www/htdocs/wp-content/plugins/google-analyticator/google-analyticator.php on line 362
    /> Subscriber

    Thread Starter Steven Vachon

    (@prometh)

    Just curious on how the new stat system is coming

    cavemonkey50

    (@cavemonkey50)

    No ETA. To be honest Google Analyticator has really been on the back burner lately.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘[Plugin: Google Analyticator] possible bug (error included)’ is closed to new replies.