Views RSS feeds have a validation recommendation

I got the same problem, my rss feed is produced using a views.

I've validated it and I got just this warning:

- Missing atom:link with rel="self"

linkedin do not publish my feed.

How can I add this reference in my feed ?

This is my feed: http://www.datacheck.it/news/feed

to jvieille: I think that you have to change your feed content to eliminate all other issues.

Hi

I am closing this issue to clean up the issue queue. Feel free to reopen the issue if there is new information and the problem still resides. If not please make sure you close your issues that you don't need any more.

Maybe you can get support from the local user group. Please take a look at this list at groups.drupal.org.

I get the same problems with LinkedIn groups rejecting RSS feeds from my site. Specifically, http://validator.w3.org/feed gives:

description should not contain relative URL references

Missing atom:link with rel="self"

My feed is http://www.indigoblue.co.uk/rss/tag/nfp

I could not see any reference to this being fixed in Views 6.x-3

Updating issue description and attaching a patch suggestion.

- Missing atom:link with rel="self"

It is fixed by patch in #5 by Fengtan(Thank you!). I confirm that it works as it should.

@freddi the patch is not included in views-7.x-3.11 -- at the moment it is pending the review of a Views maintainer

Any progress?

Attaching screenshots so it is easier for people to understand the issue and the solution.

Seems reasonable, thank you!

I tried to port the patch to Drupal 8 - see file attached.
It is not quite working yet since the <atom:link> tag gets auto-escaped in the Twig template, and also the way of rendering the tag (#markup) could be improved, but maybe this can help.

Is there any news for D8?

Do Drupal RSS feeds not validate? Using Drupal 8.3.7:

feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 2, column 0: Use of unknown namespace: http://ogp.me/ns# [help]

line 2, column 0: Use of unknown namespace: http://schema.org/ [help]

line 2, column 0: Use of unknown namespace: http://rdfs.org/sioc/ns# [help]

line 2, column 0: Use of unknown namespace: http://rdfs.org/sioc/types# [help]

line 2, column 0: Use of unknown namespace: http://www.w3.org/2004/02/skos/core# [help]

line 2, column 0: Use of unknown namespace: http://www.w3.org/2001/XMLSchema# [help]

Not sure if same issue but I find RSS feeders don't see the feed on the page, don't auto detect it but some will see it if we paste the link in, others will not. Frustrating. We replaced an old wordpress site where RSS readers would find the feed easily.

As of Drupal 8.3.7 patching RSS.php with :

  /**
   * Return an array of additional XHTML elements to add to the channel.
   *
   * @return array
   *   A render array.
   */
  protected function getChannelElements() {
    $url = $this->view->getUrl()->setAbsolute()->toString();
    return [
      [
        'namespace' => ['xmlns:atom' => 'http://www.w3.org/2005/Atom'],
        '#type' => 'html_tag',
        '#tag' => 'atom:link',
        '#attributes' => [
          'href' => $url,
          'rel' => 'self',
          'type' => 'application/rss+xml',
        ],
      ],
    ];
  }

Allow the RSS to validate aigainst the atom:link warning.

(Patch attached for 8.5.x)

Fixing test failings by removing the namespace from the element after parsing.

#25 fixes missing atom link for me.

Thank you omegadela!

Drupal core 8.9.2

Would be great to have test coverage. 9.1.x is the current dev branch.

I applied this patch in 9.3.3. After refreshing and exporting my xml, the xml validator broke saying something was wrong. Unfortunately I couldn't debug further.

Here's a simple test.

Mixed feelings on the implementation.

Pro:

• Works on existing sites with modified templates

Con:

• Every other field like this in core is in the template
• Since it works with existing templates it might add duplicates for sites already adding it

woops, here's the patch

Reroll against 10.1.x (automerge / no conflicts)

#39 applies cleanly on top of 9.5.0.

Indeed it also applies to 9.5.2 whereas #37 does not apply to 9.5.2

+++ b/core/modules/views/src/Plugin/views/style/Rss.php
@@ -88,7 +88,19 @@ public function buildOptionsForm(&$form, FormStateInterface $form_state) {
+    $url = $this->view->getUrl()->setAbsolute()->toString();

Are we sure this is always going to return the correct path? Is the display always set to the RSS display when we reach this point or can we get a page display or a fatal error here?

Also, I agree with #36, is this the best way to fix this? This could lead to the same element being there multiple times. It might be the best way, but having some validation for this route over changing the template would be good.

Still errors of unknown namespaces...

The IS is still talking about D7 and contrib View, where it looks like this has actually been addressed, so could somebody update the IS to make it more current? I'm assuming this is still an issue

Aside from the issue summary update, there is a fix here for the cdata that is out in 11.0 and 10.4 #3433: Use CDATA in XML RSS Feeds.

The core rss feed should be generated on that version and run through a validator to identify any remaining issues.

Have tested on 11.x and it still producing the same recommendation. Updated the issue summary steps to remove reference to drupal 7 and use terminology in the current views UI - also tweaked to title to clarify this is a recommendation not an error.

Moved the existing patch to an MR.

Tested again and Len's comment is #42 is correct - this patch causes an error when following the steps to reproduce. Once you add the new view and before saving it the preview will through an exception as we are trying to get a route for a view that does not exist.

Once the view is saved the validation recommendation is resolved - leaving as "Needs work" as the approach to resolve the issue does not have consensus.

reroll the patch against 10.4.1

Worked around the creation failure with a quick check.

Would have expected _something_ to have been there but I guess not. Otherwise I would expect the view to be populated so we wouldn't get an empty URL in normal usage.

Appears to have phpstan issue, also could use a rebase

If you are another contributor eager to jump in, please allow the previous poster(s) at least 48 hours to respond to feedback first, so they have the opportunity to finish what they started!

Fix in #53 doesn't fix the error.

PHPStan is correct, view is always present here - this issue is when toString is called on the URL object and it goes through the route handler - it is here a route not found exception is thrown that Route "view.foo.feed_1" does not exist.. This is applicable for both a new view and adding a new display to a view.

First thought was that we can do Url::fromUserInput('/' . $this->view->getPath())->setAbsolute()->toString(); which does return the correct path when the view is not saved - but then I noticed in views UI its actually saying "Path: This display has no path." above the preview.

Looking at https://git.drupalcode.org/project/drupal/-/blob/main/core/modules/views... it checks using hasUrl which catches that exception.

This means that the preview shows based on the saved route - but it keeps in consistent with the UI.

The Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

Think the bot was wrong on this one.

This one feels super close, left 1 comment on the MR