mojoPortal 2.2.7.9 Released

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

New Related Sites Mode

mojoPortal has for a long time had the multiple sites feature which enables you to host multiple sites on a single installation using a single database. The feature was carefully designed to keep the sites and users completely independent so that each site is isolated from the others from a security perspective. But for some scenarios its desirable to host multiple sites but use the same users and roles in all of them. For example, maybe you want to have different versions of your site for different languages bu you want the same users in all of the sites. Or maybe a university wants to create separate sites for different departments but they want the students to have the same sign in credentials in all of them. This is now possible with simple configuration settings as indicated in the documentation. Multiple sites can be configured either based on host names or by folders beneath the root site. With the folder based sites, since they share a common cookie, once the user is signed into any of the sites he is signed into all of them.

New 301 Redirect Manager

When you create pages in mojoPortal, the page gets a friendly url based on its title, like /fun-stuff.aspx would be the url for a page named Fun Stuff. Now if you change the name of the page later it will get a different url, so for example if I change the name to Really Fun Stuff, its going to get a new url /really-fun-stuff.aspx.

Now from an SEO (Search Engine Optimisation) point of view, its not a good idea to be changing your urls willy nilly. If someone bookmarked your old url you don't want it to be broken, or if its already popular in search results, you don't want it to be a broken link. So ideally, you need to have the old page do a 301 redirect to the new page. The 301 status code tells the browser that the page moved permanently. Now mojoPortal will create the 301 redirect for you automatically when you re-name a page or blog post. However, its still not a great idea to be renaming your pages frequently, you should avoid it generally but if you need to its ok to do it. You can also see the 301 redirect mappings and manually manage them from Administration Menu > Advanced Tools > 301 Redirect Manager. You need to be very careful with this feature, you do not want to create circular redirects where 2 urls redirect to each other.

This is the last Release Targeting ASP.NET 2.0

This release as previous ones targets the 2.0 ASP.NET runtime. I requested feedback in my previous post about changing to target the 3.5 ASP.NET runtime and everyone who responded was in favor. I've already changed it in my svn sandbox and will change it in trunk soon. I find that on a machine with VS 2005 I am still able to build and run the solution as long as .NET 3.5 is installed. Using the Mono 2.0 release I could still get it working if I swaped out the Web.config so it used 2.0 version of System.Web.Extensions. Using the latest Mono built from svn I see that the Mono version of System.Web.Extensions has changed to 3.5, but I'm getting an error running it and will have to investigate further.

So the next release will target .NET 3.5. If someone needs a 2.0 build it will be possible for them to change the build target back to 2.0 (in Visual Studio 2008) and rebuild, because I'm not really planning to use 3.5 specific features in the core projects for a while yet. I just need to use the 3.5 version of ScriptManager to support features like Silverlight that I will use in external projects. Just like our other features, the external projects will copy the needed files up to the main Web project so it can work at runtime. This allows us to move forward and take advantage of new things in 3.5 while keeping general compatibility with Mono and 2.0 .NET. Changing the target to 3.5 NET on the core projects only changes the Web.config file and the .csproj file

I'm very excited to start working with Silverlight 2 and RESTful web services using the REST toolkit. I'm just beginning to do exploratory prototyping now but I'm seeing some very cool possibilities.

Gravatar Joe Audette is the founder of the mojoPortal project and was the primary developer until February 2017.

Comments

re: mojoPortal 2.2.7.9 Released

Monday, November 24, 2008 6:15:28 AM

Cool..

Please make sure it still works ok with Mono 2.01 and the soon to be released Mono 2.2

Keep up the great work.

Regards

Andrew

unknown

re: mojoPortal 2.2.7.9 Released

Monday, November 24, 2008 7:57:07 PM

this will be the last release targeting 2.0 .NET by default, the next release will target 3.5
this is not a good idea. I think.

Justin

re: mojoPortal 2.2.7.9 Released

Tuesday, November 25, 2008 1:55:06 AM

Joe,

I just wrote a lengthy reply to a question you asked me in the prior post.

I am surprised you ran into a problem using System.Web.Extensions 3.5 on Mono.  I am also surprised you had to use the SVN release to get at it.  It seems like months I have been using the 3.5 version of ScriptManager (with MS AJAX) on Mono for another project.  It is for sure available out of the box on Mono 2.0.1 and I thought 2.0 as well.

Thank you for keeping Mono compatibility in mind.  I am interested to see what REST stuff you will be working on.

Justin

Justin

re: mojoPortal 2.2.7.9 Released

Tuesday, November 25, 2008 2:05:59 AM

Joe,

On my Ubuntu Intrpeid Ibex machine (using Mono 2.0.1 packages) my 3.5 version of System.Web.Extensions comes from the package libmono-system-web2.0-cil

This is the same package that provides the 2.0 (~1.06) versions for me.

On CentOS I had been compiling Mono from source and I am pretty sure the 3.5 stuff was there even before the release version of the Mono 2.0 code but perhaps after 1.9.

I know you are an OpenSUSE guy and I do not know how Mono is packaged there.

Justin

re: mojoPortal 2.2.7.9 Released

Tuesday, November 25, 2008 5:10:20 AM

Hi,

this will be the last release targeting 2.0 .NET by default, the next release will target 3.5
this is not a good idea. I think.

you are the first one to say so but you give no reasons at all. I can't give too much weight to unknown people who don't give any reason for their point of view. If you really think I should reconsider this choice, you need to make a better case for that decision.

Best,

Joe

Richard Bourque

re: mojoPortal 2.2.7.9 Released

Tuesday, November 25, 2008 5:57:04 AM

You know me, as long as it works with Mono I'm happy.   It doesn't matter what versions are behind the scenes. 

re: mojoPortal 2.2.7.9 Released

Wednesday, November 26, 2008 10:39:09 AM

I can't wait for the 3.5 integration.  I need to move some of my modules to LINQ.

Thanks,

Mansoor Lakhani.

re: mojoPortal 2.2.7.9 Released

Wednesday, November 26, 2008 10:45:20 AM

If you get the latest svn trunk code it is already changed to 3.5 framework.

Best,

Joe

Shaun Geisert

re: mojoPortal 2.2.7.9 Released

Tuesday, December 02, 2008 10:47:28 AM

Great work Joe - beginning to update a half dozen sites today to this new version.  And, from my point of view, 3.5 integration is a very good next step for Mojo, even if the benefits of doing so aren't seen for a few revisions...

Comments are closed on this post.