With the release of MWPSKex.#008 all changes are now available with this extended version of MWPSK that you can download from here: burstmode.de Download page.

These files have been updated:

• /web.config
• /site.master
• /SectionControls/ContactForm.ascx
• /SectionControls/ContactForm.ascx.cs
• /SectionControls/Guestbook.ascx.cs

Existing users of MWPSKex can easily update to the #008 release: Just copy the affected files from the downloadable archive over the existing #007 files. But be sure you have a backup at your hands before you begin to make any changes / updates!

Merry Xmas and a wonderful new year for all the MWPSK/MWPSKex users out there!

• Raimy´s HitCounter2 EasyControl is now included. Please visit Raimy´s homepage to read further information about it.
   
• The "EMail On New Comment" extension for MWPSK´s default blog module will allow you to get an Email message each time somebody adds a new comment to your blog. This Email will contain the whole text of the new comment. This way you can decide instantly wether it contains information that will need rework in any way. The credentials of the default mail server will be used when sending the Email (same as for the contact form). You will be able to supply a specific recipient Email address as well as the subject line for that Email.
   
• "Prevent New Comments" is another extension to MWPSK´s default blog module. This one will allow you to prevent users to add new comments to your blog. This can be useful when you´ll be away from your computer for a longer time (vacation or so) and you therefore cannot monitor new comments.

!!! Important update instructions !!!
For the blog extensions to work some new settings had to be added to a blog´s configuration data. If you already have a (MWPSK default) blog and intend to update to this MWPSKex version then you´ll have to update your blog´s configuration data! This is how you can do it: After installing the complete MWPSKex.#007 package or just the desired files (see below) log in as administrator. Go to your blog, choose edit mode, edit configuration and click "Save". This way the new columns will be added to the configuration data. If you have several blogs within your website, you´ll have to repeat this for every blog!
If you do not update your configuration data as described then MWPSKex will throw an exception every time somebody will try to view old comments or add a new comment.

All of the new blog settings can be set up in a blog´s configuration data.

The following list enumerates all the files that had to be changed to get the Blog extensions running. HitCounter2 is an EasyControl - see Raimy´s homepage for installation instructions if you don´t intend to use the whole MWPSKex.#007 package.

"EMail On New Comment" extension requires the following files to be modified (watch out for "MWPSKex.BlogEx.#001.I" comments in the source files):

• http://www.burstmode.de:80//App_Code/Sections/Blog.cs
• http://www.burstmode.de:80//SectionControls/Blog.ascx
• http://www.burstmode.de:80//SectionControls/Blog.ascx.cs
• New resource keys: MWPSKex_BlogEx_ctl_EmailOnNewComment, MWPSKex_BlogEx_ctl_EmailRecipientOnNewComment, MWPSKex_BlogEx_ctl_EmailSubjectOnNewComment

"Prevent New Comments" extension requires the following files to be modified (watch out for "MWPSKex.BlogEx.#001.II" comments in the source files):

• http://www.burstmode.de:80//App_Code/Sections/Blog.cs
• http://www.burstmode.de:80//SectionControls/Blog.ascx
• http://www.burstmode.de:80//SectionControls/Blog.ascx.cs
• New resource keys: MWPSKex_BlogEx_ctl_PreventNewComments

You can download the whole project from my download page.

You can also update your installation manually: The update procedure is pretty much the same as described here: MWPSKex.#001.

Have fun!

http://www.codeplex.com/MyWebPagesStarterKit/Thread/View.aspx?ThreadId=28781

Please update file http://www.burstmode.de:80//App_Code/Controls/TemplatedContent.cs as described in that discussion or download the complete solution again.

You will have to make function CreateChildControls() look like this:

protected override void CreateChildControls()
{
    if (_template != null)
    {
        PlaceHolder ctl = new PlaceHolder();
        _template.InstantiateIn(ctl);
        try
        {
            Controls.Add(ctl);
        }
        catch
        {
            ctl.EnableViewState = false;
            Controls.Add(ctl);
        }
    }
}

By default "My Web Pages Starter Kit" (MWPSK) Version 1.2.1 offers the ability to set a theme at website level. This theme will apply to all pages forming the website.

With the release of MWPSKex.#004 you will be able to set the desired theme at page level. If you wish to you could assign a different theme for every single page in your site. "Theme" in that context means layout and look & feel.

MWPSK Version 1.2.1 ships with 16 different themes out of the box. You will be able to choose from them instantly. If you have developed your own themes you will also be able to select one of those for your page(s).

Take a look at the new MWPSKex Demo page. For that page I changed the default "SwishBlue" theme to "SwishViolet". You will notice the difference ;)

You can download the whole project from my download page and use it as it comes with all the other extensions. Alternatively you can just have a look at the files that had to be modified and update your running site. Take care though if you opt to do so: you should really compare my files to yours with a tool like WinMerge (see links page). There are some other modifications in those files due to older extensions I decided to include. And of course: Always have a backup at hand prior to making any changes ;)

These files have been modified:

• http://www.burstmode.de:80//App_Code/Controls/PageBaseClass.cs
• http://www.burstmode.de:80//App_Code/Controls/TemplatedContent.cs
• http://www.burstmode.de:80//App_Code/WebPage.cs
• http://www.burstmode.de:80//Administration/Navigation.aspx
• http://www.burstmode.de:80//Administration/Navigation.aspx.cs

Additionally in file http://www.burstmode.de:80//App_GlobalResources/StringsRes.resx take care to add these new entries:

• MWPSKex_adm_Navigation_CurrentPageTheme
  (fieldlabel to display currently selected page theme)
• MWPSKex_adm_Navigation_ResetPageTheme
  (caption for reset button)

Hope you have fun with that extension! Feel free to let me know how it works for you.

What will be up next? ... Some time ago Rickard Magnusson offered an extension he called "PageThemeAdmin". At first look it seems this is much the same like my "PageTheme Selector". But there are some differences. Rickard would not change the default theme that would have been selected at website level. Instead he opted to change the underlying master file and thereby applying different SkinIDs. I like this approach too for this reason: It allows you to stay with the default theme of the website which certainly has a certain look & feel. All the CSS resources and images get served from the same set of files. No need to duplicate them. In one of the next releases of MWPSKex I will take care of something that will be based upon his PageThemeAdmin extension.

I put a little work in it and got them running with my tribe of the "My Web Pages Starter Kit" cms system that is based upon version 1.2.1. (official release version of MWPSK at the time of writing)

The "Custom sidebar HTML" extension is a nice one: It allows you to add custom HTML fragments in the sidebar container. This custom HTML can be supplied at page-level. As an addon I extended the original code of TBPrince: with my version you will be able to add HTML above and/or below the default sidebar container. This might turn out to be useful at times. And I was able to make it work with the homepage too.
To get more control over position and appearance of the HTML fragments you can define CSS classes "sidebarTopHTML" and "sidebarBottomHTML" in a file like "http://www.burstmode.de:80//App_Themes//PageLayout.css".

The "Hide from authenticated users" extension is pretty much the same as the original one posted by TBPrince. It will prevent pages from showing up as soon as a user has logged in. Administrators and Power-Users will still be able to see these pages. This extension can be useful for dedicated login pages for example. (One doesn´t need to see a login form anymore after the login procedure has been completed successfully.)

You can download MWPSKex.#005 - which is a complete project containing all modifications incorporated so far - at www.burstmode.de. Alternatively you can have a look at these files with a tool like WinMerge to see what has been modified:

To follow the "Custom sidebar HTML" extension see these files and watch out in the source files for marks "MWPSKex.#005.I":

• http://www.burstmode.de:80//App_Code/WepPage.cs
• http://www.burstmode.de:80//App_Code/Controls/SidebarControl.cs
• http://www.burstmode.de:80//Administration/Navigation.aspx
• http://www.burstmode.de:80//Administration/Navigation.aspx.cs
• You´ll also have to extend file http://www.burstmode.de:80//App_GlobalResources/StringsRes.resx. Be sure to add valid descriptions for keys "MWPSKex_adm_SidebarTopHTMLContent" and "MWPSKex_adm_SidebarBottomHTMLContent".

To follow the "Hide from authenticated users" extension see these files and watch out in the source files for marks "MWPSKex.#005.II":

• http://www.burstmode.de:80//App_Code/WepPage.cs
• http://www.burstmode.de:80//App_Code/SitemapEditor.cs
• http://www.burstmode.de:80//App_Code/Providers/CustomXmlSitemapProvider.cs
• http://www.burstmode.de:80//Administration/Navigation.aspx
• http://www.burstmode.de:80//Administration/Navigation.aspx.cs
• You´ll also have to extend file http://www.burstmode.de:80//App_GlobalResources/StringsRes.resx. Be sure to add valid descriptions for key "MWPSKex_adm_Navigation_HideToAuthenticated".

Hope you have fun with that!

And remember to list your MWPSK website at www.burstmode.de so others can get an idea of what is possible with this beautiful and leightweight open source cms system!

Since I´ll need that feature for our new company website too, I decided to add it to MWPSKex which led to it´s current release MWPSKex.#003. Take a look at the dowload page at www.burstmode.de. You will find a complete solution there.

These files had to be modified:

• http://www.burstmode.de:80//App_Code/WebPage.cs
• http://www.burstmode.de:80//App_Code/SitemapEditor.cs
• http://www.burstmode.de:80//App_Code/Providers/CustomSitemapDataSource.cs
• http://www.burstmode.de:80//Administration/Navigation.aspx
• http://www.burstmode.de:80//Administration/Navigation.aspx.cs

Additionally in the default resource file "http://www.burstmode.de:80//App_GlobalResources/StringsRes.resx" a new key "MWPSKex_adm_Navigation_VisibleInMenu" with a value of "Visible in menu" had to be added.

Finally in (all) of the skin files in folder "http://www.burstmode.de:80//App_Themes/":

• add this directive: Register TagPrefix="cc3" Namespace="MyWebPagesStarterKit.Providers"
• and replace the default sitemap datasource with our custom one: cc3:CustomSiteMapDataSource runat="server" ID="menuDataSource" ShowStartingNode="false"

Hope this will be useful to anybody...

Just use the contact form to tell me the URL you´d like to see listed there. Any additional information about your website will be very welcome!

I will not list any websites that contain illegal or offending content.

So what is "imgmap"? In short words it is "a browser-based, javascript powered image map editor". This brief description was taken from it´s homepage: http://www.maschek.hu/imagemap/index. Adam Maschek produced a great piece of code that allows us to edit HTML client side image maps in the blink of an eye! imgmap not only is a FCKEditor plugin. Numerous projects use it to do the same job. Alfonso Martínez de Lizarrondo did some great work to get the FCKEditor plugin working.

So maybe you like to have a look at these sites:
imgmap home page
imgmap project page
imgmap FCKEditor plugin homepage

In this post I´m gonna describe what to do to get imgmap working in a MWPSK environment. If you like to use imgmap as well then you can decide: follow each step of this description or just download the MWPSKex.#002 package from my download page. MWPSKex.#001 is a fully functional MWPSK V1.2.1 setup that includes version 2.6.2 of FCKEditor and the imgmap plugin. The included version of imgmap is V2.0beta6.

Have a look at Alfonso´s page: http://martinezdelizarrondo.com/fckplugins/imgmap/docs/install.html
This is a general description of how to install the FCKEditor plugin.

Here are the steps with some specific hints for MWPSK:

1. Make sure you have a backup of your site prior to modify it!
   
    
2. Download the imgmap editor V2.0beta6 from it´s project page. The zipped archive contains another set of zip archives - one of them being Alfonso´s plugin.
   
    
3. Extract and copy all files of the included subarchive "plugin_fck78.zip" to folder http://www.burstmode.de:80//FCKEditor/editor/plugins/imgmap/
   
    
4. From the main archive copy at least files "excanvas.js", "imgmap.js" and the desired language files to folder http://www.burstmode.de:80//FCKEditor/editor/plugins/imgmap/
   
    
5. Modify file "http://www.burstmode.de:80//FCKEditor/fckconfig.js": Find the section where plugins should be loaded - search for "FCKConfig.Plugins.Add". Here append this line of code: "FCKConfig.Plugins.Add( 'imgmap', 'en') ;"
   
    
6. Now you have to extend FCKEditor´s toolbar(s): MWPSK by default uses a toolbar named "customized". In file "http://www.burstmode.de:80//FCKEditor/fckconfig.js" look for something like FCKConfig.ToolbarSets["customized"]. In that assignment add the 'imgmapPopup' option like Alfonso described on his page.

So far except the toolbar modification (which should be done to toolbar "customized" instead of "Basic") is pretty much the same as any "normal" imgmap plugin setup. At this point you can see the imgmap button in MWPSK´s FCKEditor when you select an image. You can also use right mouse button and choose from the popup menu.

But you will notice that when the imgmap editor gets invoked you won´t see the image you selected beforehand in FCKEditor. You will just see that annoying little icon of a broken image url. Why is that?

When you inspect that image url with a tool like FireBug or DebugBar (have a look at my links page) you will find that the broken image url reads something like that: "/ImageHandler.ashx?UploadedFile=true&pg=%7D0%7D&image=/App_Data/UserImages/image/myimage.jpg?1216749922281"

What happened here? MWPSK serves images out of the App_Data folder by using an ASP.NET HTTP handler: ImageHandler.ashx in this case. By doing so one has more control over the "how" and "to whom" pictures get served. The actual location of the desired image is supplied via the "image" parameter. The part that poses a problem to the default MWPSK ImageHandler is that last part of the url starting with the interrogation mark: "?1216749922281".

the imgmap online editor appends the current time of day to any image url supplied to prevent browsers from caching it. Have a look at file "http://www.burstmode.de:80//FCKEditor/editor/plugins/imgmap/imgmap.js". There you will find a line reading "this.pic.src = img + '? '+ (new Date().getTime());". This is where the time-string gets appended.

Now there are at least two possible solutions to our problem:

#1 would be to replace that line simply by "this.pic.src = img;". If you decide to do so, your default ImageHandler will be fine to serve the image and you can use imgmap editor instantly. (Just pay attention: there comes another "packed" version of the "imgmap.js" file with the default release: "imgmap_packed.js". Be sure to modify this file too if you copied it in the imgmap directory and if you opted to use solution #1.)

However, I prefer solution #2: Modify MWPSK´s ImageHandler. I don´t like to remove the imgmap no-cache trick since there will be a reason why Adam has choosen to do it like this. And since MWPSK is open source we can modify the handler without problems:

Modify file "http://www.burstmode.de:80//ImageHandler.ashx": after the line of code that reads "string path = string.Empty;" append these instructions:

string urlParams = string.Empty;
if (!string.IsNullOrEmpty(file))
{
  int parPos = file.IndexOf('?');
  if (parPos > -1)
  {
    urlParams = file.Substring(parPos + 1);
    file = file.Substring(0, parPos);
  }
}

this little piece of code will strip the parts causing problems from the name of our image. It saves the stripped value(s) in an (so far) unused variable in case we will need them in a later version of MWPSKex. One never knows ...

So after these lines of code the remaining parts of the MWPSK´s ImageHandler just serve the image as if imgmap had never appended anything to the filename. And this it why it now works :)

Hope this was intersting for you too. For me it was! And many thanks to Adam Maschek who supplied me some hints about FCKEditor´s version strings ;)

Remember that you can download the complete MWPSKex.#002 package from my download page. It contains the newer FCKEditor version that was introduced by MWPSKex.#001 and also the imgmap plugin described in this post. All the rest of it´s code is from the default MWPSK V1.2.1 release.

Note: If you consider to use the imgmap plugin then you should update the FCKEditor that ships with MWPSK V1.2.1 to a newer version. See my prior post on that topic: MWPSKex.#001. The downloadable package MWPSKex.#002 includes all required modifications.

To achieve this, first step is to integrate a more current version of FCKEditor. (Preliminary tests have shown that one will get into trouble when trying to use the outdated version of FCKEditor that currently ships with MWPSK.)

So let´s talk about versions first: At the time of writing current version of MWPSK is V1.2.1. It ships with FCKEditor version 2.3.1. Most current (stable) version of FCKEditor is 2.6.2. A major bug that affects the use of HTML client side image maps was addressed with FCKEditor version 2.5 (see here).

What follows is a brief description of what to do to get the newer version running. If you´re starting from scratch with MWPSK you might want to take a look at my MWPSKex download page. I took a snaphot of my project with all modifications described here already done.
However, if you have done your own modifications to MWPSK, or if you´re just interested in where to make the changes for a newer FCKEditor version, then you can read on:
 

1. If you have made any changes to your FCKEditor setup then make sure you have a backup!
   
    
2. Download version 2.6.2 of FCKEditor along with version 2.5 of the associated FCKEditor.Net ASP.Net control. You will find both of them on the FCKEditor homepage. (If you use other versions then this description might not be suitable for you.)
   
    
3. Delete these two folders from your MWPSK project: http://www.burstmode.de:80//App_Code/FCKEditor/
   http://www.burstmode.de:80//FCKEditor/
   
    
4. Extract the FCKEditor.Net ASP.Net control (version 2.5) to folder
   http://www.burstmode.de:80//App_Code/FCKEditor/
   
    
5. Extract the FCKEditor (version 2.6.2) to a temporary directory. From there copy subdirectory "editor", both .js-files and all .xml-files to folder
   http://www.burstmode.de:80//FCKEditor/
   
    
6.  Edit file "fcconfig.js": Copy the customized toolbar sets "customized" and "customized2" from your backup copy below the "Default" and "Basic" sets. (MWPSK by default uses the "customized" set.)
   
    
7. Again in file "fcconfig.js" make sure you set variables "_FileBrowserLanguage" and "_QuickUploadLanguage" to "aspx".
   
    
8. In directory "http://www.burstmode.de:80//App_Code/FCKEditor/" either delete the .snk-file or make sure this file can be found at runtime by editing file "AssemblyInfo.cs" in same directory. (I just deleted it since I see no reason to use strong names here in a web application.)
   
    
9. Edit file http://www.burstmode.de:80//FCKEditor/editor/filemanager/connectors/aspx/config.ascx: You have to take care that only users with appropriate access rights can use the filemanager. I changed function "CheckAuthentication" to return true or false according to this:
   return ((HttpContext.Current.User.IsInRole(RoleNames.Administrators.ToString())) ||
               (HttpContext.Current.User.IsInRole(RoleNames.PowerUsers.ToString()))) ? true : false;
   
    
10. In file http://www.burstmode.de:80//App_Code/FCKEditor/FileBrowser/FileWorkerBase.cs change function "FileUpload": right before the call to
    this.SendFileUploadResponse( iErrorNumber, isQuickUpload, sFileUrl, sFileName );
    add
    string pageId = "{0}";
    sFileUrl = ResolveUrl("http://www.burstmode.de:80//ImageHandler.ashx?UploadedFile=true&pg=" + pageId + "&image=" + sFileUrl);
    
     
11. In file http://www.burstmode.de:80//App_Code/FCKEditor/FileBrowser/Connector.cs change function "GetUrlFromPath": replace
    return this.Config.TypeConfig[ resourceType ].GetFilesPath().TrimEnd( '/' ) + folderPath;
    by
    string pageId = "{0}";
    return ResolveUrl("http://www.burstmode.de:80//ImageHandler.ashx?UploadedFile=true&pg=" + pageId + "&image=" + this.Config.TypeConfig[resourceType].GetFilesPath().TrimEnd('/') + folderPath);

Ok, this should be it. Again: if you don´t like to make all the changes yourself you can download the complete MWPSKex.#001 solution from my download page.

I hope this was useful to you. If you find any errors with these modifications then please let me know.

When you download current release of MWPSK V1.2.1 from the project´s homepage, you will get a nice and small and simple to use file based cms system. Webpages in this cms are comprised of so called "sections" which you can add to the pages.

Out of the box there are several useful types of sections. A very popular one is the "HTML section". This one allows for editing fragments of HTML code using a very popular online HTML editor: FCKEditor.

When I started to evaluate MWPSK for maybe becoming the new platform for our company´s homepage I soon realized that the included FCKEditor is not from newest builds. It must be something like V2.3.1 - at the time of writing current release is V2.6.2. At first I didn´t bother about that - but this was a thing to change soon...

With our new company homepage we like to be able to use html client side image maps. (See http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.6.1 for further reference.)

With the included version of FCKEditor your only choice would be to switch to source view and edit the HTML fragment around the tags manualy. This works but is not too easy to use for people not so confident with HTML. Furthermore, placing the areas at exact positions can become very cumbersome.

So as many times before: ask Google. Soon I found links to these imgmap websites: http://www.maschek.hu/imagemap and http://martinezdelizarrondo.com/imagemaps/. Installing this plugin should enable anyone to create and maintain image maps with FCKEditor.

I downloaded the plugin, followed the instructions on how to setup, tried to edit a map on one of my pictures ... and failed.

There are quite a few issues that will strike you when trying to get it to work with MWPSK. These ones I figured out so far and in a series of posts I will try to fix them:

1. The included FCKEditor version that ships with MWPSK 1.2.1 is far too outdated. One issue that will hit you when tryin to use it in the context described can be looked up here: http://dev.fckeditor.net/ticket/1496
   
   
2. There seems to be a JavaScript error in the .js files. Firebug and DebugBar both report a "is not an object" error when it comes to loading language modules. Maybe there´s still an error with my setup, but I will investigate that later and show results here.
   
   
3. The imgmap currently uses a litlle trick to prevent images from being cached. The way it is done poses a problem to MWPSK´s image handler. As a result you won´t be able to load an image into the imgmap editor at first. But there are several ways to fix that one.

So there´s some work to do to get everything running: intall new FCKEditor + make necessary customizations, fix imgmap JavaScript error, build workaround for imgmap no-cache trick.

Stay tuned if you´re interested to see if I´ll manage to do that.

At least this should be true if the ASP.NET worker process (w3wp.exe) runs under this account.

First blog post will be kind of a roadmap for what work will focus on these days.

Maybe you´ve read the notes at burstmode.de homepage: Since we´re planning to build our company´s new homepage with MWPSK there have to be some modifications to be done to it´s current release (V1.2.1).

We need to be able to use html image maps with our new homepage and - of course - we want to edit these image maps online inside our little cms.

MWPSK these days ships without the ability to do this. There is however a html section that allows for the placement of images using FCKEditor. One can switch to source code and add the image maps by coding html - but that´s not what we want. There´s a great FCKEditor plugin called "imgmap". This will allow you to draw the maps using your computer´s mouse and edit all the properties through dialogs.

I did run some preliminary tests to simply install the imgmap plugin to FCKEditor that ships with MWPSK. But there are some problems when one tries to do that. So here´s our first roadmap:

1. Description of the errors that will occur when simply trying to install the imgmap plugin. This will also include a description of the steps I have in mind on how to get around these errors.
   
2. Project for getting current release of FCKEditor to work with MWPSK
   
3. Project to install imgmap plugin for FCKEditor to use with MWPSK

These will be first steps of my work with MWPSK. Stay tuned if that is of interest for you too ...

Note: have a look at burstmode.de linkpage for MWPSK tools. There you´ll find some links to open source projects related to this work.