I get the following Fields notice when using a Star Rating field in a Views Block:
Notice: Undefined offset: 0 in views_handler_field_field->set_items() (line 760 of ~MYSITE/sites/all/modules/views/modules/field/views_handler_field_field.inc).

To produce this issue, I found I must create the following conditions:

  1. Create a content type that uses a Star Rating field and create nodes with that field populated.
  2. Create a Block Display in Views. Page Display is not affected.
  3. Add the Star Rating field in the display settings and save the view.
  4. Filtering in Views must have at least one result. No results removes the message.
  5. You must be in the Block Display settings -OR- on a page where the block is showing.

Interestingly, the FiveStar module seems to have had a similar issue, which was quickly fixed. See: http://drupal.org/node/1213448

Comments

tomogden’s picture

tomogden commented

One more qualification:
- At least one of the nodes in the results must have the Star Rating field unset.

This seems to make all the difference.

W.M.’s picture

W.M. commented

Hello tomogden,

I doubt that this is a Star Rating module problem. It looks like it is a Views issue. I have Views version 7.x-3.0-rc1 installed at one of my sites.

I don't use Star Rating or / and Voting API at all. I am seeing this error message when supplying one particular term argument to the contextual filter. As a matter of fact, I do not see the error message when supplying "1" as an argument in the URL but see it if I supply "2" in the same URL ! Very strange.

I have to emphasize that the view looks as it should, nothing missing. But with the red-box error message sticking at top.

I hope that this information will be useful. Please let me know if you have found a solution.

I guess we might need to check if a similar issue has been reported at Views pages.

CarbonPig’s picture

CarbonPig commented

subscribe - bump - same error message - not quite sure when/why this started happening.

bryancasler’s picture

bryancasler commented

I think this might be cause by the entity cache module

ivnish’s picture

ivnish
he/him
commented
Issue summary: View changes
Status: Active » Closed (outdated)

Drupal 7 is EOL. Issue will be closed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.