Restore Drupal Planet feed #159

Closed
opened 2019-01-02 23:13:00 +00:00 by cedewey · 41 comments
cedewey commented 2019-01-02 23:13:00 +00:00 (Migrated from gitlab.com)

Our Drupal planet feed used to come from https://agaric.com/taxonomy/term/5/feed but now comes from https://agaric.coop/taxonomy/term/36/feed

We also need to add the summary of articles to the feed.

Work Required

  • Update the feed with the summary and provide a friendly alias like /drupal-planet-feed
  • Post issue in Drupal Planet queue to have RSS feed changed
  • Update markup to properly render posts in RSS readers
  • Remove the word "text" in the description
  • Change 'drupal-planet' alias from 'taxonomy/term/36/feed' to 'taxonomy/term/36/teasers/feed'
  • Test
    • Note that the feed will not parse locally unless services.yml is changed to twig debug: false
  • Update Drupal Planet posts to use two Text Paragraphs - cutting off the summary wherever seems appropriate.
  • Deploy
  • Monitor, make sure it's rendering properly in people's planet feeds.
Our Drupal planet feed used to come from https://agaric.com/taxonomy/term/5/feed but now comes from https://agaric.coop/taxonomy/term/36/feed We also need to add the summary of articles to the feed. ## Work Required * [x] Update the feed with the summary and provide a friendly alias like /drupal-planet-feed * [x] Post issue in Drupal Planet queue to have RSS feed changed * [x] Update markup to properly render posts in RSS readers * [x] Remove the word "text" in the description * [x] Change 'drupal-planet' alias from 'taxonomy/term/36/feed' to 'taxonomy/term/36/teasers/feed' * [x] Test * Note that the feed will not parse locally unless services.yml is changed to twig `debug: false` * [x] Update Drupal Planet posts to use two Text Paragraphs - cutting off the summary wherever seems appropriate. * [x] Deploy * [ ] Monitor, make sure it's rendering properly in people's planet feeds.
cedewey commented 2019-01-02 23:14:42 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
cedewey commented 2019-01-03 00:15:16 +00:00 (Migrated from gitlab.com)

mentioned in merge request !45

mentioned in merge request !45
mlncn commented 2019-01-03 20:20:30 +00:00 (Migrated from gitlab.com)

marked this issue as related to #56

marked this issue as related to #56
mlncn commented 2019-01-03 20:24:40 +00:00 (Migrated from gitlab.com)

Given that our worker-owner person content got shoved to the very top of the Drupal Planet feed, with display problems, after this merge request went in, we need to do some work on the RSS XML output and formatting in addition to getting the RSS feed Drupal Planet looks for updated to our alias.

From checking out the source of other feeds:

  • <title> should be plain text, not a link.
  • <pubDate> should be formatted something like Mon, 24 Dec 2018 10:52:14 +0100 rather than 2019 January 02
  • <dc:creator> should also probably not be a link, and may be easier to just set to agaric.coop for now
Given that our worker-owner person content got shoved to the very top of the Drupal Planet feed, *with* display problems, after this merge request went in, we need to do some work on the RSS XML output and formatting in addition to getting the RSS feed Drupal Planet looks for updated to our alias. From checking out the source of other feeds: * `<title>` should be plain text, not a link. * `<pubDate>` should be formatted something like `Mon, 24 Dec 2018 10:52:14 +0100` rather than `2019 January 02` * `<dc:creator>` should also probably not be a link, and may be easier to just set to agaric.coop for now
mlncn commented 2019-01-03 20:31:05 +00:00 (Migrated from gitlab.com)

Also the description of the entire feed (<description>Drupal related posts by the Agaric tech cooperative.</description>) shouldn't be the same for all terms.

Also the description of the entire feed (`<description>Drupal related posts by the Agaric tech cooperative.</description>`) shouldn't be the same for all terms.
cedewey commented 2019-01-03 20:58:33 +00:00 (Migrated from gitlab.com)

mentioned in merge request !46

mentioned in merge request !46
cedewey commented 2019-01-18 17:31:26 +00:00 (Migrated from gitlab.com)

assigned to @mlncn and unassigned @cedewey

assigned to @mlncn and unassigned @cedewey
cedewey commented 2019-01-18 17:31:42 +00:00 (Migrated from gitlab.com)

Assigned to @mlncn to complete the reconfiguring of our RSS feeds.

Assigned to @mlncn to complete the reconfiguring of our RSS feeds.
mlncn commented 2019-01-18 22:24:48 +00:00 (Migrated from gitlab.com)

TLDR: Translation capability made the taxonomy term listings (including feeds and the planet feed) become empty, unless the translation language constraint is removed.

The thing that was 'breaking', that was really making it difficult for me to continue styling the feed, was after the translation stuff was working (despite the red herrings of configuration import failures), it caused the existing condition on the taxonomy term view (including feeds) - "Content: Translation language (= Content language selected for page)" - to make nothing show up.

@gnuget (this part may have been cut off from the IRC message)

Maybe worth another blog post? Taxonomy term listings and feeds should be multilingual by default for sites doing 'best effort' translation, but the default configuration assumes complete translation basically, so only showing contet that has a selected language. At least i think that's what's happening?

TLDR: Translation capability made the taxonomy term listings (including feeds and the planet feed) become empty, unless the translation language constraint is removed. The thing that was 'breaking', that was really making it difficult for me to continue styling the feed, was after the translation stuff was *working* (despite the red herrings of configuration import failures), it caused the existing condition on the taxonomy term view (including feeds) - "Content: Translation language (= Content language selected for page)" - to make *nothing* show up. @gnuget (this part may have been cut off from the IRC message) Maybe worth another blog post? Taxonomy term listings and feeds should be multilingual by default for sites doing 'best effort' translation, but the default configuration assumes complete translation basically, so only showing contet that has a selected language. At least i think that's what's happening?
gnuget commented 2019-01-18 22:29:21 +00:00 (Migrated from gitlab.com)

Something similar happened to me, if the blog post language value is "und" it won't allow to translated the node (the translate tab is hidden), it needs to be "en" in order to see the option to translate the node.

Something similar happened to me, if the blog post language value is "und" it won't allow to translated the node (the `translate` tab is hidden), it needs to be "en" in order to see the option to translate the node.
mlncn commented 2019-01-18 22:42:38 +00:00 (Migrated from gitlab.com)

mentioned in commit 1d3b9cd2eb

mentioned in commit 1d3b9cd2ebc30a75863f08205b2c058980640553
mlncn commented 2019-01-18 22:45:02 +00:00 (Migrated from gitlab.com)

@gnuget Should we be bulk-updating all nodes then? An update hook will work for this! (Also, we're pulling into the park now!)

@gnuget Should we be bulk-updating all nodes then? An update hook *will* work for this! (Also, we're pulling into the park now!)
mlncn commented 2019-01-19 06:59:54 +00:00 (Migrated from gitlab.com)

mentioned in commit 0459585965

mentioned in commit 04595859650b452376972976b1882e5d520c2ec5
mlncn commented 2019-01-20 15:44:56 +00:00 (Migrated from gitlab.com)

So i'd very much prefer not to just cut off at a certain number of characters or words. We consider our Summary field much to short for the purpose. Paragraphs module has done a lot to provide administrative summaries but there's only a long-out-of-date patch seeking to provide a paragraph summary formatter sufficient for visitor-facing teasers.

@cedewey How do you feel about making the first text paragraph our RSS feed 'description'? Some blog posts might need to have their text paragraph split but i think this approach provides a good balance between control and complexity (especially given the lack of other options).

So i'd very much prefer not to just cut off at a certain number of characters or words. We consider our Summary field much to short for the purpose. Paragraphs module has done a lot to provide [administrative summaries](https://www.drupal.org/project/paragraphs/issues/2862083) but there's only a long-out-of-date patch seeking to provide a [paragraph summary formatter sufficient for visitor-facing teasers](https://www.drupal.org/node/2433933). @cedewey How do you feel about making the **first text paragraph** our RSS feed 'description'? Some blog posts might need to have their text paragraph split but i think this approach provides a good balance between control and complexity (especially given the lack of other options).
mlncn commented 2019-01-21 05:32:59 +00:00 (Migrated from gitlab.com)

mentioned in commit 93a85a8d6b

mentioned in commit 93a85a8d6b74a70b9ce7cd776fc22d53f8b0813d
cedewey commented 2019-01-21 18:04:06 +00:00 (Migrated from gitlab.com)

Sure, that seems fine, at least for the time being. We should add some
help text to make this clear to authors. I'll do that.

Sure, that seems fine, at least for the time being. We should add some help text to make this clear to authors. I'll do that.
mlncn commented 2019-01-21 18:04:07 +00:00 (Migrated from gitlab.com)

mentioned in commit 7184d9cfc3

mentioned in commit 7184d9cfc33f2d6dd1a726314879a29225d003de
mlncn commented 2019-01-22 17:22:36 +00:00 (Migrated from gitlab.com)

marked the checklist item Update the feed with the summary and provide a friendly alias like /drupal-planet-feed as completed

marked the checklist item **Update the feed with the summary and provide a friendly alias like /drupal-planet-feed** as completed
mlncn commented 2019-01-22 17:22:38 +00:00 (Migrated from gitlab.com)

marked the checklist item Post issue in Drupal Planet queue to have RSS feed changed as completed

marked the checklist item **Post issue in Drupal Planet queue to have RSS feed changed** as completed
FreeScholar commented 2019-01-23 05:51:11 +00:00 (Migrated from gitlab.com)

There is a link on the bottom of this page: https://www.drupal.org/node/230418/revisions/view/3437513/11215911 that leads to a 404 resolving here https://agaric.coop/keywords/drupal-planet
@mlncn @wolcen

There is a link on the bottom of this page: https://www.drupal.org/node/230418/revisions/view/3437513/11215911 that leads to a 404 resolving here https://agaric.coop/keywords/drupal-planet @mlncn @wolcen
cedewey commented 2019-01-24 18:36:54 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
mlncn commented 2019-01-24 19:19:00 +00:00 (Migrated from gitlab.com)

[apologies never hit submit on this comment some days ago]

@cedewey so where it stands now is after deployment, the 'drupal-planet' alias needs to be changed from 'taxonomy/term/36/feed' to 'taxonomy/term/36/teasers/feed'

The feed that should be tested therefore is /taxonomy/term/36/teasers/feed

Note that this will not parse locally unless services.yml is changed to twig debug: false

[apologies never hit submit on this comment some days ago] @cedewey so where it stands now is after deployment, the 'drupal-planet' alias needs to be changed from 'taxonomy/term/36/feed' to 'taxonomy/term/36/teasers/feed' The feed that should be tested therefore is /taxonomy/term/36/teasers/feed Note that this will not parse locally unless services.yml is changed to twig debug: false
cedewey commented 2019-01-25 20:45:19 +00:00 (Migrated from gitlab.com)

assigned to @gnuget and unassigned @mlncn

assigned to @gnuget and unassigned @mlncn
cedewey commented 2019-01-26 03:24:10 +00:00 (Migrated from gitlab.com)

marked the checklist item Update markup to properly render posts in RSS readers as completed

marked the checklist item **Update markup to properly render posts in RSS readers** as completed
cedewey commented 2019-01-26 03:24:50 +00:00 (Migrated from gitlab.com)

@gnuget if you can deploy this to the test site, I can then change the /drupal-planet alias and test it.

@gnuget if you can deploy this to the test site, I can then change the `/drupal-planet` alias and test it.
cedewey commented 2019-01-28 20:36:00 +00:00 (Migrated from gitlab.com)

assigned to @cedewey and unassigned @gnuget

assigned to @cedewey and unassigned @gnuget
cedewey commented 2019-01-28 23:11:51 +00:00 (Migrated from gitlab.com)

@gnuget @mlncn ,

Looking good! The one thing remaining I can see is that the word "text" is showing up at the beginning of the description each time.

@gnuget @mlncn , Looking good! The one thing remaining I can see is that the word "text" is showing up at the beginning of the description each time.
cedewey commented 2019-01-28 23:12:01 +00:00 (Migrated from gitlab.com)

assigned to @gnuget and unassigned @cedewey

assigned to @gnuget and unassigned @cedewey
cedewey commented 2019-01-28 23:12:29 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
cedewey commented 2019-01-28 23:13:21 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
mlncn commented 2019-01-28 23:40:22 +00:00 (Migrated from gitlab.com)

marked the checklist item Remove the word "text" in the description as completed

marked the checklist item **Remove the word "text" in the description** as completed
gnuget commented 2019-01-29 00:58:46 +00:00 (Migrated from gitlab.com)

I just deployed this in production

I just deployed this in production
cedewey commented 2019-01-29 15:14:51 +00:00 (Migrated from gitlab.com)

I'm keeping this open with the ~Deploy tag until we are certain this is working properly because right now it is not. As part of the deployment process the path needed to be updated for /drupal-planet. I've done this, but the planet hasn't updated its feed since we made that change.

I'm now going back through recent Drupal Planet tagged posts and setting the teaser text by breaking up the intended teaser text into its own text paragraph.

In the future, whoever deploys needs to read the issue description carefully, especially the Work Required section and make sure every step is completed.

I'm keeping this open with the ~Deploy tag until we are certain this is working properly because right now it is not. As part of the deployment process the path needed to be updated for /drupal-planet. I've done this, but the planet hasn't updated its feed since we made that change. I'm now going back through recent Drupal Planet tagged posts and setting the teaser text by breaking up the intended teaser text into its own text paragraph. In the future, whoever deploys needs to read the issue description carefully, especially the Work Required section and make sure every step is completed.
cedewey commented 2019-01-29 15:14:58 +00:00 (Migrated from gitlab.com)

marked the checklist item Change 'drupal-planet' alias from 'taxonomy/term/36/feed' to 'taxonomy/term/36/teasers/feed' as completed

marked the checklist item **Change 'drupal-planet' alias from 'taxonomy/term/36/feed' to 'taxonomy/term/36/teasers/feed'** as completed
cedewey commented 2019-01-29 15:15:02 +00:00 (Migrated from gitlab.com)

marked the checklist item Test as completed

marked the checklist item **Test** as completed
cedewey commented 2019-01-29 15:29:51 +00:00 (Migrated from gitlab.com)

marked the checklist item Update Drupal Planet posts to use two Text Paragraphs - cutting off the summary wherever seems appropriate. as completed

marked the checklist item **Update Drupal Planet posts to use two Text Paragraphs - cutting off the summary wherever seems appropriate.** as completed
cedewey commented 2019-01-29 15:30:04 +00:00 (Migrated from gitlab.com)

marked the checklist item Deploy as completed

marked the checklist item **Deploy** as completed
cedewey commented 2019-01-29 15:30:26 +00:00 (Migrated from gitlab.com)

changed the description

changed the description
gnuget commented 2019-01-29 15:53:00 +00:00 (Migrated from gitlab.com)

Yes, the right thing to do was write a hook_update to make this change automatically in the deploy.

My bad, next time I will do it.

And it seems that the bad links are going to be preserved until new blog posts make them disappear, so... would it be a good idea to publish our blog posts to help that to happen faster?

Yes, the right thing to do was write a hook_update to make this change automatically in the deploy. My bad, next time I will do it. And it seems that the bad links are going to be preserved until new blog posts make them disappear, so... would it be a good idea to publish our blog posts to help that to happen faster?
gnuget commented 2019-02-24 21:18:16 +00:00 (Migrated from gitlab.com)

This has been working for a few weeks now, I'm going to close this.

This has been working for a few weeks now, I'm going to close this.
gnuget commented 2019-02-24 21:18:16 +00:00 (Migrated from gitlab.com)

closed

closed
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: agaric/agaric-coop#159
No description provided.