13 Responses to “User Profile MySite Redirect via Delegate Control”

  1. Links (12/11/2008) « Steve Pietrek - Everything SharePoint Says:

    […] User Profile MySite Redirect via Delegate Control […]

  2. MySite Redirect Update « Solutionizing .NET Says:

    […] December 24, 2008 — Keith Dahlby Per Ian’s suggestion, I’ve updated the MySite Redirect solution (CodePlex) to support the Force=True parameter passed by the “My Settings” […]

    • francis Says:

      I have download the version 0.2, added solution and installed the feature but the My Settings link still points to the userinfomationlist on the site. Any step by step instruction is appreciated.

      • Keith Dahlby Says:

        If I’m understanding the question correctly, the My Settings link should stay at the user information list to allow editing. The redirect works on all other links to that user (from user fields, for example). If you do want to redirect away from the My Settings list, you can download the source and build your own version with the lines concerning Request.QueryString["Force"] commented out.

  3. Francis Says:

    Thanks for the quick response. This is what led me to your solution. We do not have Mysites enabled for our staff. We would like them to still have access to their My Profile page and click on Edit details to update their profile details successfully. Staff should not see their private Mysite but when they click on athe mysettings link to be directed to their Myprofile page. We are using MOSS2007 SP1 Only.

    • Keith Dahlby Says:

      Rather than redirect the My Settings link, I would add a separate link to My Profile. This could either be added to the Personal Action menu (where My Settings is) with a custom action, or as a replacement for the My Site link through the GlobalSiteLink1 delegate control. I may add these as additional features for this solution. Also, check out Ian’s post on the other details of using User Profiles without a MySite.

      • Andy Says:

        Keith, thanks for taking the time to write this up, I’ve found it helpful.

        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.

      • Keith Dahlby Says:

        Andy ~

        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 ~

      • Andy Says:

        Ah, I see…. “Regional Settings” and “My Alerts” – that makes sense. I can see why you might need to go the page now. I’m happy that I understand what’s going on, thanks for clarifying.

        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.


  4. Refactoring with LINQ & Iterators: FindDescendantControl and GetDescendantControls « Solutionizing .NET Says:

    […] and GetDescendantControls June 23, 2009 — Keith Dahlby A while back I put together a quick and dirty implementation of a FindControl extension […]

  5. Perry Says:

    Should there be a userdisp.ascx in the codeplex source somewhere?

    • Keith Dahlby Says:

      Perry ~

      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 ~

  6. andersrask Says:

    Actually there is no need to find the UserListForm control. You already have the SPListItem available from the OnFormInit method: just cast objOfInterest as an SPListItem and you are good to go :)

    public void OnFormInit(object objOfInterest)

    Redirect(objOfInterest as SPListItem);

Comments are closed.

%d bloggers like this: