I'm happy to announce the release of mojoPortal 2.2.7.8, available now on the download page.

Important Upgrade Notes

We added a feature to combine and minify the CSS files in the skins. Those using custom skins should modify their skins as described here after upgrading.

This release also contains Oomph, as described in my previous post.

We have a new Croatian language translation thanks to Slaven Brumec.

Other than the above and a few bug fixes and feature tweaks as discussed in the forums since the last release, the main focus of this release is changes to make developers happy as discussed below.

Source Code Project Re-Organization

All of the content features like Blog, forum, Gallery, Maps, etc, have been moved out of the core mojoPortal projects into the mojoPortal.Features.* projects. This makes it possible to build and package a leaner version of mojoPortal without any features except Html Content. I will still continue to make the official mojoPortal releases with all the features, I have no plans to package separate mojoPortal lite packages myself, but the idea is that developers can package their own application with mojoPortal without having to include all the features we have. If you work with the mojoportal-core.sln Visual Studio Solution, it will build without any of the extra features and you can package it with UnLeashIt. If you build the mojoportal-complete.sln solution, post build events will copy the extra features up to the core Web project, so you don't want to do that if you plan to package without those features. Once they are copied up to the Web project UnLeashIt will include them, so you need to keep it clean by not building that solution if you want to package without those features.

As a result of this, features are now basically self contained within folders, like the Blog is in the siteroot/Blog folder and forums are in the siteroot/Forums folder and so on. For backward compatibility I created pages with the old names that will do a 301 redirect to the new pages. I also was careful to make sure friendly urls for existing blog posts would continue to work correctly.

The only thing site owners need to change is if they previously submitted a blog site map to google using siteroot/BlogSiteMap.ashx, you need to change that to siteroot/Blog/BlogSiteMap.ashx

When Should We Target .NET 3.5?

I'd like to gather input and opinions about when we should change the target platform to .NET 3.5. I'm eager to start playing with Silverlight in mojoPortal and it seems to need the 3.5 versions of ScriptManager to host the <asp:Silverlight control

The issues I see are:

• We need to be careful to keep compatibility with Mono. I think we can move forward with using .NET 3.5 on Windows and continue to build for .NET 2.0 for the MonoDevelop solution. We really won't add non-supported features in the core projects but we need to be able to specify 3.5 settings in Web.config of the core Web project. We already maintain a different Web.config file for Mono packages so this should not be a problem. We can put 3.5 functionality like Silverlight into separate projects and use post build events to deploy them into the main web for runtime as we do with most features. So these projects can be left out of the MonoDevelop Solution until they are supported. In summary I think we can workaround all issues relating to Mono and should be able to move forward while still maintaining Mono compatibility.
• Hosting - This is the issue I'm not entirely sure of and would appreciate any input. If the next release of mojoPortal for Windows targets the 3.5 runtime is that available at your hosting or will it pose a barrier to upgrade? It seems like most of the big name hosts have .NET 3.5, they don't like to be left behind by the competition.
• Visual Studio 2005 Issues? - As far as I know VS 2005 can target 3.5 without problems except maybe for Windows Workflow development and it doesn't have some of the built in project templates for 3.5 .NET projects. We already maintain separate VS 2005 solution files so we could leave out any projects if they don't work.

UPDATE:

Forgot to mention that I updated the project road map yesterday.

I'm happy to announce the release of mojoPortal 2.2.7.7, available now on the download page.

This is a minor bug fix release for things reported in the forums since the last release.

This release does have significant changes/improvements in the experimental WebStore feature so those experimenting with this feature may be more interested in upgrading. I call it experimental primarily because at this stage of the development I can't promise smooth upgrades for this feature and because its not yet feature complete enough for general purpose ecommerce. It is functional for selling of download products and is in use on this site in the mojoPortal Store. I've been working pretty actively on this feature lately driven by a need to improve the store on this site. Strategically I also think that getting this feature in shape to really handle general ecommerce scenarios is going to be very valuable in driving popularity of mojoPortal.

I'm also happy to note that mojoPortal now has a presence on Codeplex, and our downloads are available there in addition to on Novell Forge. We are still using the Subversion repository on Novell Forge for now. I've been experimenting with Codeplex hosting since they released their server side svn bridge as I mentioned in this previous post. The Codeplex team is working on some additional features to the svn bridge that are needed before we can use it for our repository. Specifically, the svn merge commands which are really needed to manage moving changes from sandboxes into trunk are not yet available but they are confident that these features will be implemented, so ultimately we will move our repository there once its all working well. In the meantime we are glad to be able to have our release and code packages available at Codeplex and giving us more visibility in the .NET community. For those who are working with the source code I stll recommend you get it directly from svn trunk.

Now we also have a formal Issue Tracker available on Codeplex. If you want to report bugs in a formal fashion with steps to produce the bug and the ability to track when the issue is closed, feel free to use the new issue tracker. For less formal reporting of problems or bugs the forums here on mojoportal.com are still the best bet.

I'm happy to announce the release of mojoPortal 2.2.7.6, available now on the download page.

In addition to bug fixes for things reported in the forums since the last release, this release includes the new Content Rating System and Feed Manager improvements mentioned in this previous post, as well as the new option in Site Statistics to show a graph of new site member registrations that I mentioned in this post.

I'm happy to announce the release of mojoPortal 2.2.7.3, available now on the download page.

Important Upgrade Information

After upgrading to the new version, you will need to delete the following files from your /bin folder.

• PollFeature.UI.dll
• PollFeature.Business.dll
• PollFeature.Data.dll
• SurveyFeature.UI.dll
• SurveyFeature.Business.dll
• SurveyFeature.Data.dll

The reason these need to be deleted is because the Poll and Survey have been combined into these dlls:

• mojoPortal.Features.UI.dll
• mojoPortal.Features.Business.dll
• mojoPortal.Features.Data.dll

The good news is that the Poll and Survey now work for all the different databases, MS SQL, MySql, PostgreSql, Firebird Sql, and SQLite. Previously we only had support for MS SQL and MySql for those features.

Everyone who purchased Event Calendar Pro (and I mean both of you ;-D), will also need to upgrade to version  0.0.0.2-b (a free upgrade, just download the product again). There were changes in mojoPortal that required small changes in this feature, there are no functional changes to this feature right now.

Feature Improvements

• Blog - I added an Excerpt option due to popular demand in the forums. Improved support for Persian localization, thanks to Asad Samarian.
• RSS Feed Module - Walter Ferrari added options for showing and hiding various things, an Excerpt option, and Ajax paging.
• Forum - I added a captcha if anonymous posting is enabled to reduce spam.
• Image Gallery and Shared Files - I added some ajaxiness

New Multi Site Configuration Options

Its now possible to use different SMTP settings in each site of a multi site installation. To enable this, set this setting to true in your Web.config or user.config file:

<add key="EnableSiteSettingsSmtpSettings" value="false" />

after doing this a new Mail Settings tab will appear in Site Settings.

New Global Options

These settings are not site specific so they will affect all sites in a multi site installation.

There is a new config option to email site administrators if a new user registers. Set this to true if you need that functionality:
<add key="NotifyAdminsOnNewUserRegistration" value="false" />

The following config options were added based on a request in the forums to make it possible to show more information on the member list page for an intranet site:
<add key="ShowEmailInMemberList" value="false" />
<add key="ShowLoginNameInMemberList" value="false" />
<add key="ShowUserIDInMemberList" value="false" />

Accessibility and Usability Improvements

FCKeditor now works with Safari and Chrome, so we have enabled it for these browsers in mojoPortal.

All site management features should now work even if javascript is disabled. Previously most of the features could function even with javascript disabled but we went through and found a number of places where we were using <asp:LinkButton and replaced it with <asp:Button. We did this because the ASP.NET LinkButton is the only button type in ASP.NET that doesn't work if javascript is disabled. We added some new css to style the new buttons to look like links instead of buttons. Fortunately, other than the LinkButton, almost everything in ASP.NET is built to degrade gracefully but remain functional if javascript is disabled. So, with a little care its not difficult to build accessible applications and sites.

We replaced the use of ExtJs Tabs with YUI Tabs in Site Settings, Page Settings, and other places where we have settings grouped on tabs. This change was made partly because the YUI tabs are a bit more accessible, but also because we have been running into issues where the ExtJs tabs don't work right. I've hadd issues in Firefox 3 where if there was an FCKeditor on more than one tab, changing between the tabs doesn't show the correct editor. Others have reported interaction bugs with ExtJs tabs when using the new 3.5 Ajax Extensions. Since the ExtJs project changed their license to GPL, which is not compatible with mojoPortal, we can no longer get upgrades to ExtJs and can only use the old version under a compatible license. So, it seems better to switch to the YUI tabs. The only downside is that the ExtJs tabs had a few better looking skins for the tabs but YUI only has one. So some of you may not find the new YUI tabs to be as good looking as the old ExtJs tabs, but since the YUI tabs are also skinnable, we may be able to come up with better looking skins in the future.

New Extensability Point

There is a new plugin system for UserSignInHandlers that allows developers to plug in their own handlers that can fire after a user signs into the site. People have asked for this so that they could implement custom redirect logic depending on user roles and other criteria.

New Translation

Resource files have recently been translated into Spanish thanks to Manuel de la Pena

Seems like a lot has been accomplished since the last release only 33 days ago. Lots of exciting things going on in the pipeline that I will blog about later.

As always be sure and backup before upgrading and if you have any troubles post in the forums and we will try to help.

I'm happy to announce the release of Event Calendar Pro version 0.0.0.2

This release adds support for rendering events that span across days, weeks, or months, on the Month View.

From the beginning I felt rendering events that span across days was an important feature and I had hoped to have it working for the initial release, but since it took longer than expected to release this product I didn't want to delay any longer while I worked on this new calendar rendering. It was kind of tricky to achieve it. I struggled with it for about 4 days before finally arriving at a decent solution for rendering the events across days.  I hope you like it.

Event Calendar Pro includes 1 year of free upgrades, so anyone who already purchased it can just download it again from their order history to get the new version.

You can also try it out at demo.mojoportal.com