Profile URL Changes
At least one of my clients uses the API for some integrations and the recent profile URL change borked his integrations. If we could possibly get a heads up of a few days prior to any forthcoming URL changes, that would be great!
A blog post would be useful here, as well as some individualized emails.
Thanks! ![]()
Comments
-
We absolutely should have announced this change ahead of time. The reason we didn't is that it wasn't done on purpose; a config setting change got cowboy-coded which caused this as a side-effect. We didn't catch it until it caused Reactions to break in production.

For context, the old default was
/profile/{id}/{name}and the new one is/profile/{name}. Both have always worked. The default is what our navigation links in Vanilla use.An integration with our official API would not have relied on a userid being in the URL, so it sounds like they're doing something a bit hacky.
Enabling non-unique usernames would actually restore the old structure, but that's not a good trade off. In this case, I suggest they modify their code to not rely on the userid being present - that's what we did to fix Reactions.
As much as I don't like how it happened, I do like the new defaults more than the old ones, so I don't really want to revert the switch.
0 -
Thanks for the info, Linc. I think that the client in question (Royal College of Dentists of Canada) has made the appropriate changes on their end for their integrations, but they simply requested a heads up in the future. Good to know that we would announce it under normal circumstances.
FWIW, personally, I like the new defaults, too!
0