Restore RSS feeds of new modules, themes, distributions

In addition to "New modules (full modules and sandboxes)*", RSS feeds for Themes and Installation profiles are not working either. Found these on https://drupal.org/node/63589.

Yeah, for some reason the pages at /taxonomy/term/X seem to be 404ing. I don't really understand this, since they're there in stock D7 core.

Confirmed

Actually this is probably two different problems:

1) Taxonomy pages are 404ing.
2) The distinction between module, theme, etc. is no longer based on taxonomy, but based on content type. So if we want to restore this functionality, we'd need to create new views. To not break bookmarks, these would be at taxonomy/term/14 (modules) taxonomy/term/15 (themes) and taxonomy/term/96 (distros)

@webchick: Is this something I can help with? I am not sure of the process to develop for drupal.org, but I could help with the views if that works.

Possibly related: Drupal project's release feed is 503ing (https://drupal.org/node/3060/release/feed)

This is also related to #2129427: RSS feeds bringing Drupal.org down which is the issue regarding 503's on the feed.

Oops. Missed this. Thanks for asking, shrop! Yes, indeed! :)

There are instructions for how to get a dev site to help squash d.o bugs at https://drupal.org/contribute/drupalorg/code (more specifically, https://drupal.org/node/1018084). Since it'll likely be awhile before the d.o team can get to this, given the other major/critical issues in the queue, someone else stepping up to try and restore this functionality would be awesome.

This is a legit bug, not a support request.

Thanks @webchick!

Changing status back to 'Active' to avoid confusion, as we no longer user 'needs review' as confirmation step.

Yes, same here and I'm glad I finally found this issue. RSS feeds are broken when you want to subscribe to module updates from the https://drupal.org/node/NID/release page. To reproduce, try clicking on the RSS icon (will bring you to https://drupal.org/node/NID/release/feed) and it'll return the following message always:

Our servers are currently a bit busy, please try refreshing the page after a few seconds. 
Thanks!

So these links are broken.

https://drupal.org/node/3060/release/feed
https://drupal.org/taxonomy/term/14/0/feed
https://drupal.org/taxonomy/term/15/0/feed
https://drupal.org/taxonomy/term/96/0/feed

Do we just need to create a view with those feeds? I'm not sure how to do that in the sandbox so that it can be brought over to live.

Updating title

Note this page gives a WSOD:
http://drupal.org/node/199251

from:
all/modules/drupalorg/drupalorg_project/drupalorg_project.module

      case 199251: // List projects with commit RSS feeds.
        $node->content['body']['#value'] .= drupalorg_project_list_commit_rss();
        break;

re WSoD reported in #18, this seems to be the cause:

Fatal error: Call to undefined function pager_query() in /var/www/dev/sprint10-drupal.redesign.devdrupal.org/htdocs/sites/all/modules/drupalorg/drupalorg_project/drupalorg_project.module on line 652

RSS feeds of new releases for projects were fixed and feeds for taxonomy pages are working fine. For #18 I opened separate issue #2264721: Port drupalorg_project_list_commit_rss to D7.

Problem here is only with the new projects feeds: modules, themes, distributions. Updating issue summary accordingly.

valthebald, are you still planning to work on this one?

There should be separate feeds for sandboxes and full projects. This probably should be a generic solution in Project module.

@tvn, where is it documented now what the new feeds are? I used to like the twitter feed and found it the most convenient way to keep up.

New feeds? They do not exist yet, this whole issue is about creating them.

The issue is about restoring the previously working feeds and I saw your note "RSS feeds of new releases for projects were fixed and feeds for taxonomy pages are working fine.", so I assumed they were now working. Maybe we need the issue summary updated again.

What's left to do then to have working RSS feeds and a working twitter feeds for new projects?

Actually, lets keep this in drupalorg. These RSS feeds directly correspond to pages which the project_solr module is currently generating. Unfortunately, project_solr is some old code which is showing its age; more functionality, like RSS should not be added.

Instead, use apachesolr_views to make these RSS Views. The Views should be laid out in a way to mirror the pages like https://drupal.org/project/project_theme and https://drupal.org/project/project_module?solrsort=ds_created%20desc&f[4..., so the HTML displays can eventually replace those pages. Actually doing that replacement would be out of scope for this issue; the HTML displays should be disabled, or at a non-conflicting path. The RSS links can be injected into the existing pages.

The Views should be exported to a new feature in drupalorg/features and any custom code in drupalorg.module.

Actually, I was wrong. apachesolr_views is not actively maintained, and we would run into bugs switching to it. Instead, lets attach the feeds to the Views that make https://drupal.org/project/project_theme/index and https://drupal.org/project/project_module/index. This View is overridden by drupalorg, so watch out for exporting too much.

Updating summary.

So far...

• Added a project_rss view mode for nodes within project module.
• Created a View with two contextual filters, one for node type and the other for project type. These create fields including https://opdavies-drupal.redesign.devdrupal.org/project/project_theme/fee... and https://opdavies-drupal.redesign.devdrupal.org/project/project_module/fe...
• Managed the display of the project_module content type for the project_rss mode to display a summary or trimmed description.

Left to do...

• Change the display for the other project content types.
• Generate patches for the code changes.
• Bundle up the DB changes ready for deployment.

Here's the first patch, for project module.

Patch for drupalorg module to follow.

@drumm: I've exported the project content types into Features, as discussed. Can you test on a fresh database installation please?

For #34 -

• Let's enable and use the built in/default RSS view mode. (Unless there is a good reason to add a new one.)
• Can the View be a new display of project_index, instead of a completely new View?

Let's enable and use the built in/default RSS view mode. (Unless there is a good reason to add a new one.)

This is set to "Full text", at least on my dev site, which means that everything is displayed including the release table and maintenance information. The old feed had less information which was the reason for adding the project_rss view mode.

Can the View be a new display of project_index, instead of a completely new View?

Yes, it could. I did put it there originally, but I was having to override values from the Master display to add the second contextual filter etc., so thought that it would be cleaner to have it in its own View. Happy to move it though if you prefer.

This is set to "Full text", at least on my dev site, which means that everything is displayed including the release table and maintenance information.

This is how it looks with the full text setting - https://opdavies-drupal.redesign.devdrupal.org/project/project_module/fe....

Let's enable and use the built in/default RSS view mode. (Unless there is a good reason to add a new one.)

Ah, I think I see what you mean now. There's a RSS option within the custom display settings fieldset on each content type. That should be fine also and would make the project_rss one redundant so I'll remove that from the code.

Patches updated.

42: project-rss-feeds-2126331-42.patch queued for re-testing.

Everything is committed, with some minor changes. Will be deployed some time tomorrow.

In project module -

• The patches were actually against the unstable1 tag, but this View hasn't changed since then, so they worked, with manually applying.
• I moved the $view_mode !== 'rss' check within a level. This doesn't make a difference in the end, but will be better organized for any future additions.

In drupalorg -

• I made an export straight from staging to see the differences from this.

Deployed and added redirects for the 3 URLs mentioned in the issue summary.