Many of the new Acquia employees are posting things to their personal blog as well as the company blog, this is causing double posts on Drupal Planet. Perhaps we could ask these users to make sure they are using a 'Drupal Planet' specific tag instead of just 'Drupal' for one or both of the blogs, and not tag duplicate posts with 'Drupal Planet' on both blogs, but only one of them?

Comments

mikey_p’s picture

mikey_p commented

Examples include

http://jeffwhatcott.com/drupal/content/whats-drupal-community-view-futur..., http://acquia.com/blog/whats-drupal-community-view-future-open-source

AjK’s picture

AjK commented

I'm sure the people at Acquia will pick up on this but, as with any d.o webmasters issue, I have sent out an email with a request for comment/feedback.

jwhatcott’s picture

jwhatcott commented

Hi Michael. Sorry this caused an issue. We're happy to implement any reasonable solution.

It looks like Planet Drupal currently pulls all Acquia.com blog posts and in the case of my personal blog, it only pulls posts that are tagged as "drupal". I think a better approach would be to have both feeds be set to pull only the terms "Drupal Planet" and then we can place the tag in one or the other, but not both.

For my site, the proper feed to implement the above would be:

http://jeffwhatcott.com/drupal/taxonomy/term/83/0/feed

For acquia.com, the correct feed would be:

http://acquia.com/taxonomy/term/29/0/feed

I've tagged only a couple of posts with these so far, but we'll use them like this from here on out.

Make sense?

mikey_p’s picture

mikey_p commented

Oh no big deal at all from my end, I just thought that perhaps you might wanna take a look at it since it's a pretty widely read page. I wasn't going to bring it up at first, so I hope this hasn't troubled you at all.

AjK’s picture

AjK commented
Status: Active » Fixed

I have altered both Jeff's and Acquia's feed to that supplied by Jeff in #3. Hopefully that should resolve the issue. Thanks.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.