FBSS for D6 has a Views row plugin that handles the "Feed" display for RSS feeds from the default views. statuses.info still has a files[] entry for statuses_views_plugin_row_rss.inc but the file itself is missing. I removed it in this commit along with views-view-row-rss.tpl.php because it was causing problems, but RSS support should be added back.

CommentFileSizeAuthor
#1 statuses-views-broken-rss-1490566-1.patch2.67 KBicecreamyou

Comments

icecreamyou’s picture

icecreamyou commented
Status: Active » Needs review
StatusFileSize
new statuses-views-broken-rss-1490566-1.patch2.67 KB

It looks like Statuses views can actually use the default RSS style plugin this time around, which means this issue now simply requires replacing the old feed display from the views that still have it (statuses_all and statuses_tags) with the new feed display. An example export is below (although we need to fill out the fields better):

$handler = $view->new_display('feed', 'Feed 2', 'feed_2');
$handler->display->display_options['defaults']['hide_admin_links'] = FALSE;
$handler->display->display_options['pager']['type'] = 'none';
$handler->display->display_options['style_plugin'] = 'rss';
$handler->display->display_options['row_plugin'] = 'rss_fields';
$handler->display->display_options['row_options']['title_field'] = 'message';
$handler->display->display_options['row_options']['link_field'] = 'sid';
$handler->display->display_options['row_options']['description_field'] = 'message';
$handler->display->display_options['row_options']['creator_field'] = 'user_contextual';
$handler->display->display_options['row_options']['date_field'] = 'created';
$handler->display->display_options['row_options']['guid_field_options'] = array(
  'guid_field' => 'sid',
  'guid_field_is_permalink' => 0,
);

Adding the new feed displays depends on #1779234: Convert default Views exports to Views 3 syntax, although the real "bug" here is the old/broken feed displays so I'd be fine with removing those separately. Untested patch attached to do so.

mathankumarc’s picture

mathankumarc commented
Status: Needs review » Needs work

Views is not happy with this patch. Getting the following errors after applying this patch,

Notice: Undefined property: stdClass::$display_plugin in view->init_display() (line 282 of views/includes/view.inc).
Notice: Undefined property: stdClass::$display_plugin in views_get_applicable_views() (line 1306 of views/views.module).
Notice: Undefined property: stdClass::$display_plugin in view->init_display() (line 282 of views/includes/view.inc).

icecreamyou’s picture

icecreamyou commented

What I did to get the patch in #1 was look at the diff between the exported view in D6 with and without the feed display. I guess a better way would be to just edit the view in D7, remove the feed display, and then export it using the Views 3.x format.

icecreamyou’s picture

icecreamyou commented

Marked #1904022: statuses_rss in views_plugin_list as duplicate

semei’s picture

semei commented
Issue summary: View changes

I still get this error with the latest dev. Isn't there any clean way yet to resolve the issue?

kebz’s picture

kebz commented

I just now got these "strict warnings" below. The only thing I did prior to is install and enable these modules:

  • date_ical module enabled
  • date_ical module installed
  • calendar module enabled
  • calendar module installed




=================
STRICT WARNINGS
=================

  • Strict 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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /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 3179 of /includes/bootstrap.inc)
kebz’s picture

kebz commented

I just disabled the "Statuses Tags" module for now

ed523’s picture

ed523 commented

I too am experiencing this and fixed it by disabling statuses tags which is too bad. There's this https://www.drupal.org/project/hashtags but it says it's a way to add hastags to nodes and statuses aren't nodes...