Hi,

Congrats on your new site, it looks great! I've added it to our site list.

It is a shame if you had to fork mojoPortal and cut yourself off from upgrades. Hopefully you managed your customizations without making changes to mojoPortal code or else cloned the features you needed to modify.

I'm not sure where you got the idea that we don't support urls like http://onlynaturalfood.com/recipe_739_Spicy_Bean_Salad.aspx, you can easily create urls like that for pages or blog posts with our built in friendly url system and for custom features you could also have used our internal friendly url system the same as we do in included features.

At any rate, glad you were able to achieve your goals.

Best,

Joe

Hi Kris,

Since you said you had to modify the blog edit page I assume you used a modified version of the blog. The blog feature is a good example of how it can be done. The blog module is the part of the blog that lives on a CMS page and it shows a list of recent posts, but the post links go to the /blog/ViewPost.aspx?pageid=x&mid=y&itemid=z but the user sees a friendly url like /title-of-blog-post.aspx which our internal url re-writer maps to the real url.

So if I were implementing a recipe module I would use the same pattern, I would have a pageable list of recipes in the module control and link to detail pages usingfriendly urls. You can see from studying the /blog/EditPost.aspx.cs how the friendly url is created from code. So the friendly urls are created automatically when a blog post is made and it does not require creating a new CMS page. CMS pages do use friendly urls, but friendly urls can be used to map to any real url supported by any feature. WebStore also makes friendly urls for products and offers and my Event Calendar Pro feature makes friendly urls for event detail pages.

I will be covering this more as I complete the rest of my video training series. I plan to cover how to implement friendly urls and how to make a feature searchable in our search engine.

Best,

Joe

H Kris,

You don't need to create a mojo page, it is sufficient to create a friendly url assuming your custom feature has a real page to map to with query string params.

So the RecipeModule.ascx would be the part that is hosted in a mojoportal CMS page and it would have a pageable list of recipes that links to say /recipes/RecipeDetail.aspx?pageid=x&mid=y&recipeid=z but instead of linking directly like that with the query string params, you would create a friendly url that points to the real url using our FriendlyUrl business class. Then what you need is an extra field on your recipe object/table where you also store the friendly url for the recipe like ~/my-bbq-chicken.aspx. The reason to store it also in your feature table is simply so you know how to link to it from the pageable list.

In addition to passing in feature specific params for your real url (RecipeDetail.aspx for example), you must also pass pageid and module id as pageid=x &mid=y 

These params are used for helper methods to enforce cms page security on feature pages  and it also keeps the menu highlighted correctly.

I recommend have a guid column on your recipe table and keep a unique guid there for each recipe. This guid can be stored as the pageGuid on the FriendlyUrl object which allows you to delete the friendly url if you delete the recipe.

You can just generate the friendly url based on a patttern like replace spaces with underscores or dashes and add the .aspx. We also have a method SiteUtils.SuggestFriendlyUrl(txtTitle.Text, siteSettings); that can be used to suggest a friendly url that doesn't already exist in the site. It replaces white space with a single dash and cleans out characters not suitable for urls.

In the blog we use a web service and javascript to suggest a friendly url from this method but allow the user to override our suggestion.

Hope it helps,

Joe

To make a feature searchable in the mojoportal search engine, you have to implement an indexbuilderprovider for your feature.

http://www.mojoportal.com/makingcustomfeaturessearchable.aspx

For any feature where you create friendly urls, you should also create a feature specific sitemap.ashx url that can be submitted to google and other search engines. So for example the blog has /blog/BlogSiteMap.ashx which can be submitted to google as a site map. This is discussed on the bottom of this page:

http://www.mojoportal.com/search-engine-optimization.aspx

Hope it helps,

Joe