This solution builds on the existing userdisp.aspx – all you need is an assembly with the ProfileMySiteRedirectControl class (Solutionizing.ProfileMySiteRedirect.dll in my example), wired up through a Control element in a feature manifest.

Hope this helps ~
Keith

Sorry – one supplemental Q – I’ve just checked and I can’t see a link for Regional Settings on userdisp.aspx – I just get “My Alerts” – any ideas?

Thanks again.

A.

You are correct that with MOSS the profile fields are read-only. However, there are also two site-specific links on that page: My Regional Settings and My Alerts. Providing access to those is the purpose of the force parameter.

Alternatively, you could set My Settings to ignore Force and just provide those site collection preference links elsewhere, maybe in the Personal Action menu. However, going that route means that all documentation of the standard WSS/MOSS behavior will be useless to your users, so weigh accordingly.

Cheers ~
Keith

I am trying to get my head around the confusing world of Mysites/Profiles and the WSS simple user details page.

I follow everything you’ve said and also had previously looked at Zac Smith’s example. But I wonder if you can clear something up….?

You say above that “the My Settings link should stay at the user information list to allow editing.” – I don’t get this.

As I understood it, the WSS style user page doesn’t allow editing if you have a MOSS user profile, is that right? In this (my) case when you click “My Settings” from the Welcome control you get a pretty useless read-only page which won’t let you edit any of the fields…. So having the redirect to the mysite (with the edit details link) would be much more useful. I see how I can do this by removing the Force=True logic, but just wanted to check that my understanding is correct and that my environment is behaving as designed….. is it right that the user info page via “My Settings” isn’t editable in this case? If so, what did you mean above? Thanks for any help, appreciate it.