I've installed the Charts module with Google Charts and created a pie chart with Views aggregation. The chart displays the user's user points per category (I created several user points taxonomy terms) and is situated on the user pages (which is rewritten with user_view). I'm getting the following errors:

  • Strict warning: Declaration of userpoints_views_handler_field_category::init() should be compatible with views_handler::init(&$view, &$options) in _registry_check_code() (line 3160 of C:\wamp\www\mysite\includes\bootstrap.inc).
  • Strict warning: Declaration of userpoints_views_handler_field_category::pre_render() should be compatible with views_handler_field::pre_render(&$values) in _registry_check_code() (line 3160 of C:\wamp\www\mysite\includes\bootstrap.inc).

What's going wrong and how can I solve this?

Comments

autopoietic’s picture

Status: Active » Closed (cannot reproduce)

Hello Jeroen,

Coincidentally discovered this issue whilst poking around to help with your question.. spooky..

I am pretty sure this is an error with userpoints rather than charts, as I replicated your situation (as I understand it) in a blank d7 install and the error occurred when I added a contextual filter for user:uid to the view (and disappears if filter removed). At this stage I had the view display configured to table, not chart, so the charts module should not have been involved.

I think this issue might therefore be of greater relevance:

https://drupal.org/node/1447666

Jeroen94’s picture

Project: Charts » User Points
Version: 7.x-2.0-beta5 » 7.x-1.0
Component: Views integration » Code: userpoints
Status: Closed (cannot reproduce) » Needs work
Jeroen94’s picture

Hi Tom,

Thanks for your answer, you correctly understand my situation. I moved the issue to the User Points queue, but I'm not sure whether the issue you refer to can help me. I'm not working with the dev-version and I can't find a file called userpoints_views_handler_field_category.inc in the views > handlers folder. Did I miss something or is there another solution?

deanflory’s picture

I just submitted a separate issue about something similar:

Here are the errors I'm getting upon submission and reload of the Modules page (others included in case they are somehow related):

  • Strict warning: Only variables should be passed by reference in user_details_help() (line 20 of /.../sites/all/modules/user_details/user_details.module).
  • Strict warning: Declaration of userpoints_ranking_handler_filter_last_period::init() should be compatible with views_handler_filter::init(&$view, &$options) in _registry_check_code() (line 3138 of /.../v02/includes/bootstrap.inc).
  • Notice: Undefined index: entity type in views_handler_field_entity->init() (line 44 of /.../sites/all/modules/views/handlers/views_handler_field_entity.inc).
  • Strict warning: Only variables should be passed by reference in user_details_help() (line 20 of /.../sites/all/modules/user_details/user_details.module
deanflory’s picture

Keeping the issue alive.

Jeroen94’s picture

@deanflory: Have you been able to solve the problem yet? Nobody seems to mind helping...

deanflory’s picture

No, not fixed yet, seems to rear it's head when I clear all caches 2-3 times in a row. The user_details errors have been fixed and I suspect the views_handler error above is due to something in a view like proximity that I haven't had time yet to sort out/remove.

I've done nothing tricky or hackish with userpoints, really only enabled the module, set up the categories and set up the points for each on each node type. I can't remember off the top of my head how I'm displaying those on user profiles, if it's via the user_details block or individually.

It may be that the user points error is triggering by the views error but I'll have a chance to knock that out in the next few days and will try to report back if it's fixed, just strange that it just popped up recently with Drupal 7.24-7.26 upgrades and module updates.

Wtower’s picture

Jeroen94’s picture

Status: Needs work » Closed (duplicate)
Issue tags: -Strict warning, -error

Solved for me after the latest update to 7.x-1.1.