I have only been playing with mysite for about a week and have been surprised by how robust and flexible it is as a module.
I did run into a rather annoying glitch concerning the path aliasing option that comes with it, however. The problem was my user 1 was named 'admin', so when I turned path aliasing on, the url for his mysite page was /mysite/admin. This seems to have conflicted w/ the default content and settings pages for mysite, because when I try to configure content for that user, it is being applied as the default.
Seems weird, given that the link from within the mysite admin configuration page for default content is to: /admin/settings/mysite/content..... but when I visit this url I'm still forwarded to /mysite/admin/content instead, even w/ aliasing off. Is that supposed to be happening?
As a side note, when I finally removed path aliasing in the settings page, it stopped creating new aliases but I had to delete all the old ones manually. . . seems like that functionality might should be built in.
Just my two cents from spending a small bit of time w/ this module...
Comments
Comment #1
agentrickardThis is officially, by design. The menu issue is a trick involving submenu items and how the default user is configured.
This problem only affects users named 'admin', unfortunately.
Here's how it works.
User 0 == default user == mysite/admin/content
This menu item is provided by the MySite module and is fixed.
So when aliasing is turned on for you:
User 1 == admin == mysite/admin
And you get a conflict.
This is a documented shortcoming, also "by design," but it could be a feature request.
Comment #2
vegeneric commentedHey, thanks for the quick response. No biggie for me to change out my user 1's username on this particular site.... but it does seem like out of all the millions of usernames people use on websites, admin is probably the most consistently used.
Thanks again for your response and all the work on this sweet module.
Comment #3
agentrickardYeah, this is a case of the most obvious solution to solving my problem causes inadvertant issues for others.
I may try to fix this in the next release, so marking as a bug instead of "by design."
Comment #4
agentrickardcleaned this up in 5.x.3
Comment #5
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.