I noticed that when doing either a bulk update, or when allowing a user to update their username, new feed aliases are added, but the old ones don't go away. In particular, the blog feed and tracker feed don't get updated. This can be an issue when a new user joins who has the changed user's old username.

Comments

ddyrr’s picture

ddyrr commented
Priority: Normal » Minor

I just turned on my brain and realized that deleting the old one may not be desirable... although, in some instances it is, but that is a smaller issue.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Version: 5.x-1.1 » 5.x-1.2
Priority: Minor » Normal

This seems like a normal issue to me - they should respect the update action settings like all other aliases.

Can you confirm this is still in 5.x-1.2?

Thanks!

ddyrr’s picture

ddyrr commented

Yes. I upgraded, ran another test, and found that this is still an issue. The blog feed and tracker feed were both left behind with the old username, while the same entries were added for the new username. I should also mention that my paths are set like this:
blog/[user]
track/[user]
which creates fee entries like this:
blog/[user]/feed
track[user]/feed
I think usually they are set up like this:
[user]/blog
[user]/track
so I don't know if that's an issue. I couldn't set mine up that way, because it was screwing up my profiles and causing them to have [user]-1 instead of just [user]. If that was a known issue that has been fixed, then I could just change it to the usual [user]/blog, if that is what is causing the problem with the feeds. Thanks

Leeteq’s picture

Leeteq commented

Subscribing.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Title: Doesn't update feeds, only adds new ones » RFC: should feed aliases get updated following normal "update action" settings?

So, the behavior is easy to repeat:

1. Enable blog, feed aliases for blogs, tracker, feed aliases for trackers
2. Enable the "create a new alias, replacing the old one"
3. Create a user
4. Edit the user's name

Here's the raw database dump that shows what happens:

mysql> select * from url_alias;
+------+--------------------+---------------------------+
| pid  | src                | dst                       |
+------+--------------------+---------------------------+
| 1026 | user/48            | supsup/qwerasdf           | 
| 1027 | blog/48            | blogs/qwerasdf            | 
| 1028 | blog/48/feed       | blogs/qwerasdf/feed       | 
| 1029 | user/48/track      | users/qwerasdf/track      | 
| 1030 | user/48/track/feed | users/qwerasdf/track/feed | 
+------+--------------------+---------------------------+
5 rows in set (0.00 sec)

mysql> select * from url_alias;
+------+--------------------+------------------------------+
| pid  | src                | dst                          |
+------+--------------------+------------------------------+
| 1026 | user/48            | supsup/qwerty-asdf           | 
| 1027 | blog/48            | blogs/qwerty-asdf            | 
| 1028 | blog/48/feed       | blogs/qwerasdf/feed          | 
| 1029 | user/48/track      | users/qwerty-asdf/track      | 
| 1030 | user/48/track/feed | users/qwerasdf/track/feed    | 
| 1031 | blog/48/feed       | blogs/qwerty-asdf/feed       | 
| 1032 | user/48/track/feed | users/qwerty-asdf/track/feed | 
+------+--------------------+------------------------------+
7 rows in set (0.00 sec)

However, as you point out in #1, having duplication here in the name of preserving links might be OK...if the blogs/qwerasdf/feed alias gets deleted then anyone who has subscribed to it will no longer get updates - instead the reader will very likely fail silently (at least my readers fail silently on 404s).

I'm posting an RFC on groups.drupal.org - hopefully that will get some input on it.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

and note that http://drupal.org/node/91748 has a fix for it.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Version: 5.x-1.2 » 5.x-2.x-dev
Category: bug » task

If we fix this it will be in the 2.x branch.

Also, changing to a "task" until we determine if it's a bug or not.

Freso’s picture

Freso commented
Version: 5.x-2.x-dev » 7.x-1.x-dev

"If we fix this it will be in the 2.x branch." - 2.x branch of 6.x, that is.

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Category: task » support
Status: Active » Fixed

I can't duplicate this with the current code. It seems to be replacing the existing aliases perfectly across all branches. Marking as fixed. If this can be re-confirmed using the latest code from CVS, please change this issue's status back to active.

Status: Fixed » Closed (fixed)

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