I have a brand new 4.7.5 install. When installing the Views Bonus module and visiting admin/views_bonus, I receive this error:

Warning: Invalid argument supplied for foreach() in /var/www/modules/views_bonus/views_bonus.module on line 116

If I select any of the available views and click Submit I'm brought to a screen that shows:

Warning: Invalid argument supplied for foreach() in /var/www/modules/views_bonus/views_bonus.module on line 116

Warning: Cannot modify header information - headers already sent by (output started at /var/www/modules/views_bonus/views_bonus.module:116) in /var/www/includes/common.inc on line 267

There is no other output on the screen so there is no other possible course of action other than to backspace. When I do, I can see that my settings have been saved but the Invalid argument message is still displayed on the screen and, when I visit the Views admin page, the only additional views I can see are:

Monthly archive
Panels by Term
Taxonomy Directory

I don't have Lineage installed so I wouldn't expect to see that View but I cannot see Audio:Playlist, Grid View or Summary+full view or any of the other Panels views.

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

1) The foreach error is fixed.

2) At the top of the views_bonus admin page: Choose which plugins you would like to have active on your system. Most plugins provide new view types which may be accessed from the "Type" dropdown in the "Page" and "Block" sections of the view edit page.

Please, please someone tell me how to make it so people read that. I am very weary of people not knowing where to look for the views bonus pack plugins. I do everything I can to try and put it in people's faces, and people still complain that they don't know where to find the plugins. I am at a loss. I could put it in big red letters and a <blink> tag but people would complain even more about that.

Help me out, because all I can figure is that the language just isn't clear enough.

Patrick Nelson’s picture

Patrick Nelson commented

Merlin,

Firstly, thanks for fixing the bug.

Secondly, I'm sorry that I didn't read the documentation properly. For what it's worth, I don't think you can do more to "make it so people read" it because, sometimes, people just don't - for a variety of reasons. In my case, on this occasion, it was just that I had an awful lot to do that day, and skimmed through it without really reading properly. As I say, I'm sorry for that - normally I take the time to read everything before asking questions on here.

Thanks once again for the fix - and for all the contributions that you make to Drupal - you certainly make my life easier and I do appreciate it.

Regards

Patrick

merlinofchaos’s picture

merlinofchaos commented

I'm sorry; I've been a bit tired and frustrated, and I really shouldn't have come out quite like that. You've always been a solid user who's provided good feedback when you submit issues, and you deserve an apology. It's a bit of a sore spot for me, and I shouldn't let that get to me like that.

Patrick Nelson’s picture

Patrick Nelson commented

Merlin,

No problem - your comments really struck a chord because, on nearly every Drupal site I build, I end up saying to the users "Please, please, please READ what is on the screen!", so I felt a bit sheepish at having been caught out myself.

I may be a bit gentler on them in the future, so thanks! ;)

Regards

Patrick

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)