Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
D7 7.21, Views 3.5, Statuses 7.x-1.0-beta2 clean install
Views errors and warnings cascade down the site:
Style RSS Feed requires a row style but the row plugin is invalid.
This goes away when selecting input format html in Views on all fields.
This warning is flooding the logs:
trict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_equal() should be compatible with views_handler_filter_string::op_equal($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_contains() should be compatible with views_handler_filter_string::op_contains($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_word() should be compatible with views_handler_filter_string::op_word($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_starts() should be compatible with views_handler_filter_string::op_starts($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_not_starts() should be compatible with views_handler_filter_string::op_not_starts($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_ends() should be compatible with views_handler_filter_string::op_ends($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_not_ends() should be compatible with views_handler_filter_string::op_not_ends($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_not() should be compatible with views_handler_filter_string::op_not($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_shorter() should be compatible with views_handler_filter_string::op_shorter($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_longer() should be compatible with views_handler_filter_string::op_longer($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
Strict warning: Declaration of statuses_tags_views_handler_filter_has_this_tag::op_regex() should be compatible with views_handler_filter_string::op_regex($field) in _registry_check_code() (line 3066 of /home/public_html/includes/bootstrap.inc).
and now when saving module settings:
Fatal error: Class 'RulesEventSet' not found in /home/public_html/sites/all/modules/statuses/submodules/statuses_tags/views/statuses_tags_views_handler_filter_has_this_tag.inc on line 171
Comment | File | Size | Author |
---|---|---|---|
#9 | repeated-warnings-1947612-9.patch | 5.02 KB | jweirather |
Comments
Comment #0.0
cutmedia CreditAttribution: cutmedia commentedadded fatal error
Comment #1
cutmedia CreditAttribution: cutmedia commentedBumping this to elevate, is nobody receiving this error? Statuse 7.x-1.0-beta2+3-dev.
The error appears when updating modules and the call is to Rules even though I have Statuses Comments Rules Integration and Statuses Rules switched off.
Fatal error: Class 'RulesEventSet' not found in /home/public_html/sites/all/modules/statuses/submodules/statuses_tags/views/statuses_tags_views_handler_filter_has_this_tag.inc on line 171
Comment #2
IceCreamYou CreditAttribution: IceCreamYou commentedThe RSS issue is addressed in #1490566: Views RSS support missing
The other strict warnings are probably because that handler needs to be rewritten -- it was copied pretty much directly from Views 6.x-2.x
But the word "RulesEventSet" doesn't appear anywhere in the module, so I'm not sure where that's coming from. Line 171 of that file is the closing curly-brace of that class, followed by just a blank line before the end of the file, so it's not a very descriptive error.
Comment #3
liza CreditAttribution: liza commentedam getting similar warnings after creating a VIEW that includes status TAGS:
these spewed relentlessly (about 30 times) on the system message & dlog.
i am on a set up with
DRUPAL 7.22
STATUSES 7.x-1.0-beta2+6-dev
CHAOS TOOLS 7.x-1.3+2-dev
VIEWS 7.x-3.7
the main distribution is PANOPOLY (which is also acting up due to Status).
Comment #4
festerm CreditAttribution: festerm commentedSame thing to me, first after enable an OG context module it shows a fatar error: Class 'RulesEventSet' not found at statuses_tags_views_handler_filter_has_this_tag.inc
After disable the module it keeps showing the same kind of error seen above.
Comment #4.0
festerm CreditAttribution: festerm commentedadded all noteices
Comment #5
Kebz CreditAttribution: Kebz commentedI just now got these "strict warnings" below. The only thing I did prior to is install and enable these modules:
=================
STRICT WARNINGS
=================
Comment #6
Kebz CreditAttribution: Kebz commentedI just disabled the "Statuses Tags" module for now
Comment #7
Leeteq CreditAttribution: Leeteq commentedComment #8
jweirather CreditAttribution: jweirather commentedI just wanted to post a couple of notes, based on my install.
1) These strict warnings appear to be coding standards errors coming from PHP, as of 5.4(?). From what I read, there is probably a function call that needs an argument appended/prepended or something. I'll see if I can sort out the specifics and try to contribute a patch.
2) Even with the errors, statuses tags appear to be working properly. I get the errors one time, on saving a statuses view, and they go away after a single page refresh.
Comment #9
jweirather CreditAttribution: jweirather commentedI'm attaching an attempt at a patch. It applies for me and the repeated errors are gone. Additionally, hashtag suggestions and the view at /tags/tagname are both working, which is about the extent of what I know to test and/or need to test.
Please note that I'm new to patching, and new to statuses, so it's (extremely) likely that I missed something.
Details: It appeared that the views_handler_filter_string() class had changed in updated versions of Views, and only takes one argument now, but the statuses_tags_views_handler_filter_has_this_tag() was passing two arguments. The second (culprit) argument was "$db_or", which appeared(?) to allow chaining together query conditions. I removed the argument from the calls to the class functions and initialized it instead inside of each functions. I'm sure there are consequences of this that I don't yet know, but it appears to be working for my own, limited, use case.
Also, please refer to comment #8, point 1), with regard to why the errors may suddenly be appearing: upgrading PHP to 5.4+.
Comment #10
IceCreamYou CreditAttribution: IceCreamYou commentedThanks for the patch, jweirather. The purpose of the $db_or variables (and the reason for providing the class in the first place) is to allow specifying which tag types (e.g. @mentions or #hashtags) to include in the query. Most likely D7 Views has a better way of doing this, but some investigation will be required before that code can just be removed.