Using The MyPage Feature

Important Update for mojoPortal version or Higher

The ASP.NET WebParts framework never really caught on, though similar in concept to SharePoint WebParts they are not the same thing and not compatible technologies. While there are 3rd party WebParts for SharePoint, no 3rd party WebParts have emerged for ASP.NET WebParts and most people consider it a dead end technology at this point. Therefore we've decided to de-couple the MyPage feature from mojoPortal so that it is not a part of the core mojoPortal framework. It will no longer be included as of mojoPortal

The MyPage feature is now available as a separate download from here. There is a folder for .NET 4 and .NET 3.5 each one contains a wwwroot folder. You would copy the "contents" of the wwwroot folder (not the folder itself) into the root of your mojoPortal installation.

The source code is still included in the mojoPortal source code but it is excluded from the solution so you would have to add it back if you want to work with the source code.

add this to user.config
<add key="MyPageIsInstalled" value="true" />.

and uncomment some things in Web.config

<!-- uncomment this if you have the MyPage Feature installed -->
        <add assembly="Microsoft.Web.Preview, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<!-- uncomment this if you have the MyPage Feature installed -->
        <add tagType="System.Web.UI.WebControls.WebParts.WebPartManager" mappedTagType="Microsoft.Web.Preview.UI.Controls.WebParts.WebPartManager"/>
        <add tagType="System.Web.UI.WebControls.WebParts.WebPartZone" mappedTagType="Microsoft.Web.Preview.UI.Controls.WebParts.WebPartZone"/>

Using MyPage Feature

Here is a link to a Flash Video demo showing how the Personalization feature works in mojoPortal.

Remember that the ASP.NET WebParts does not currently work with mono and therefore MyPage doesn't work either.

This feature is enabled by going into Site Settings and checking the box "Enable MyPage Feature".

The MyPage feature utilizes the ASP.NET 2.0 WebPart framework for creating personalized pages. This is similar to what Yahoo has with My Yahoo or what google has with personalized pages. Users can customize the page by choosing available content and adding it to the page. Users can also remove content or move it around using drag and drop.

Any content instance within a mojoPortal site can be made available for MyPage by going into the Module Settings (gear icon) and checking the box labeled "Available For My Page". The RSS Feed Aggregator module is probably the easiest way to get external content and make it available for MyPage. Using the new Content Manager feature, content can be created without adding it to any site page and still be made available for MyPage.

Important: The My Page feature is designed for making content available to the public. It is not driven by role based security. By making content available on MyPage you are making it available to everyone.

When logged in as a user in the Admins or Content Administrators roles, you can specify content on MyPage that is visible to all users including anonymous users. You do this by using the little person icon in the upper right. When it shows one person you are in "User Scope" which means you are only customizing the page for yourself (the logged in user), but if you click the little person icon, you will see it change to 2 people which means you are in "Shared Scope". Content you add to the page while in Shared Scope is visible to all users. Pay close attention when adding content in Shared Scope because after each item you add it will go back to User Scope and you need to set it back to Shared Scope before each itme is added. Clicking the green plus icon in the upper right is what shows the Catalog of content made available for MyPage.

A logged in user can personalize MyPage. A logged in user can hide content that was added by the Admin/Content Administrator in shared scope and can choose the content to show on the page from the available content. Any customization done by the logged in user who is not an Administrator only pertains to his own login and is always in User Scope.

Created by Joe Audette on May 29, 2006
Last Modified by Joe Audette on Jan 30, 2014