MyPage feature

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This thread is closed to new posts. You must sign in to post in the forums.

10/3/2011 1:08:56 PM

John S

Total Posts 190

View Posts

MyPage feature

Hi All,

Anyone done much with the MyPage feature? I've run into an odd situation. Developing with VS2010 and running the site in the VS web server all seems to work fine. I can navigate to mypage.aspx in IE, add a few modules, and it looks the same if I bring the page up in Firefox or Chrome. But after publishing the site to my test server (2008, IIS7), I can set up stuff in one browser, but other browsers will still have an empty MyPage. Same login and username, but it's not getting the personalization data for the MyPage in different browsers. Anyone know what might cause this behavior?

On another note, does anyone know how to hide and/or format the minimize/close/edit menu links for a web part? I see where the image is specified in the resource file, but nothing I do in a style sheet seems to have any effect on these menu items. (I'd really like to remove the "edit" menu item)

Thanks,

John

10/4/2011 8:57:17 AM

Joe Audette

Total Posts 18439

View Posts

Re: MyPage feature

Hi John,

I have no idea about the browser specific problems on your production machine. I would use Firebug and/or Chrome dev tools to look at the network requests for any problems and the script console to see if any errors are happening, check the mojoportal log etc.

As far as removing the edit buttons, that is not possible because MyPage/WebParts are intended by design for user interaction to personalize the content by adding content they are interested in from the catalog of available content.

The images are hard coded like:

/Data/SiteImages/editsettings.png
/Data/SiteImages/close.png
/Data/SiteImages/del.png
/Data/SiteImages/min.png
/Data/SiteImages/max.png

so the only way to customize them is to replace those files with new files of the same name and do the same again after upgrades.

I guess you could put a 1 pixel image for the edit icon so it would not be visible.

Note that as of recent source code, the MyPage feature has been moved into a separate project mojoPortal.Features.MyPage and moved out of the mojoPortal.Web project. And this project is not included in any of the default .sln files so you would need to add it to your custom .sln file if you want to work with the code.

WebParts never caught on in ASP.NET and are basically dead end technology so the MyPage feature is deprecated, it still exists and does what it does for those who want to use it but it is disabled by default in mojoPortal 2.3.7.0 (though it is included in the package and can be enabled by config). At some point in the near future I will stop including it in the package and make it a separate download. I have no future plans for WebParts or the MyPage feature, but one could fork the code of that project now that it is separate from mojoPortal core and customize it as they see fit.

Hope that helps,

Joe

10/4/2011 2:49:38 PM

John S

Total Posts 190

View Posts

Re: MyPage feature

Hi Joe, Yes we did have this discussion offline about the future of the mypage feature. Since Sharepoint is still pretty popular and they advocate creating ASP.NET web parts over Sharepoint web parts when doing custom development, I figure the technology will still be around for awhile, even if the popularity of web part pages like this didn't really fly. Our marketing department really fell in love with the concept, so here we go. Thanks for the heads up on the code changes. I'll probably go ahead and update my code and fork the mypage project off now so I can do some other things with it. Many thanks again for all your effort!

10/6/2011 12:39:23 PM

John S

Total Posts 190

View Posts

Re: MyPage feature

Hey Joe,

If I could throw one more question on the subject out there: i got code updated to 2.3.7.0 with the separate mypage project and everything seems to be updated fine and building without errors. The mypage feature seems to be working all the same as before with one exception, it no longer seems to have the capability to drag web parts to reposition them on the page. Any idea what might have happened there?

Thanks again,

John

10/6/2011 12:54:59 PM

Joe Audette

Total Posts 18439

View Posts

Re: MyPage feature

Hi John,

Copy the Microsoft.Web.Preview.dll from the _libs folder into your /bin folder and make sure you have uncommented the the needed items in Web.config as in the My Page article. That should solve it.

Note that this is another indicator of how dead end ASP.NET WebParts really are. When Microsoft first released .NET 2.0 with WebParts the drag and drop only worked in IE, and they later released this preview dll to make it work in FF and Safari, but they never followed through with a final version or any updates after this preview.

Best,

Joe

10/6/2011 1:08:00 PM

John S

Total Posts 190

View Posts

Re: MyPage feature

Thanks again Joe, I figured it was something simple I missed. I had everything but the few lines uncommented in web.config. Good to go now!

You must sign in to post in the forums. This thread is closed to new posts.