Hi Sean,

I managed to reproduce this issue in my local instance. It appears that user alias(saving users without permalink) and saving users with permalinks are not validating for duplicates between each other.

This causes issues with which user profile is being loaded when the url contains no id(eg: /2978-anne, /3392-anne vs /anne).

I will log this issue in our tracker so we can address this in the next release.

Thank you so much. In the meantime, how do you suggest I locate the users in my system that have this problem. I believe it has probably happened more than once. I will then need to change the permalink of some of the users but I do not know which ones.

I did just bump up against another one: https://www.drcarney.com/kathy

I think I will need some kind of report of which users have duplicate URLs so we can fix them from the backend.

Hey Sean,

After checking your database and running some queries, it appears that these permalinks are duplicates(https://take.ms/xJ88S), meaning there are already users without permalinks having those names.

Thank you. I will try to fix all of those right away. Hopefully no others will happen before the fix becomes available.

do you think this will be available soon?

Sean

OK. I just realized that I am not able to fix my problem with this information. You have shown me the URLs that are being used by two or more people but I do not which people. I tried to look for instance for the string 'anne' in the users search and MANY people showed up.

OK. I have been able to figure these out by trial and error. What I have to do is go to the URL that has duplicate users and then go to profile page. Such as https://www.drcarney.com/susan

Once I am there I can click on the About link to find out which Susan on our web site this is for. Then I change their perma-link in the back end. At this point I can then reload the profile url again and it then changes to a different user.

I can then click on their About link to figure out who they are.

All of them are done but I believe we may have uncovered another separate but very related possible bug. It appears that for some people the perma-link is NOT being used for their Profile url but is being used for their other urls.

For example. Right now you can visit the following page to see a profile url:

https://www.drcarney.com/susan

This is the Profile page and it appears to be generating that URL based on the users "Username"

Now click on the Timeline and the About links and you will see that the urls that are generated differently.

They appear to be based on the users perma-link instead.

https://www.drcarney.com/sue

(this is the exact same page as the Profile page)

https://www.drcarney.com/sue/about

I would think that ALL of the urls for a particular user should be based on their perma-link once a perma-link is established.

Hey Sean,

Currently the reason 'susan' loads sue's profile is because no user is using the 'susan' permalink, so it falls back to check on the alias

I apologize because there was a small mistake in my query. Actually the 'susan' permalink has no issue because both users already have their permalink set(previously: https://take.ms/i7Mkx).

This means if you access /susan previously, the system knows that it should load id 3517 and respectively so for /sue. Since susan has no issue, it also means that only these users would experience the duplicate issue(https://take.ms/cEjlS).

As such, it is ok for you to change back the permalink for id 3517 to 'susan'(since I noticed you already changed it to 'susans').

I changed the users permalinks to remove any chance of a conflict until the code is changed to make this problem no longer possible. I figured we would not spend time on this until it was patched.

I am thinking that this is not yet patched?

Thanks, Sean