All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).
Posts in category WebPartFramework

Making Web Parts Language Independent

If you're using the Web Part Framework or the Flexigrid module you can now have pages on your multilanguage site that show the same web parts for all languages of the same page.

Thomas Haug from Gazette has added a small check in the core of the web part framework for a property on the current page that is called LanguageIndependentWebParts of type Boolean. If the page has such a property, and the value has been set to true, the web parts for this page will be stored independent of language.

You might have landing pages that should be the same regardless of language, or more likely, all your web parts are language sensitive in the first place, so adding them to all languages is a pain. You don't have to anymore (that is - as long as you use the source code with revision 515 or later.) If you want this property to be true by default, set true as default value on the property in the page type in admin mode.

A good example on how you can change the core of an existing module without breaking existing code, but still add a valuable new feature. Thanks Thomas!

Web Part Framework

A template driven CMS with properties for editors to fill in makes wonders for the usability but sets boundaries for the creative mind. The result is often that you got to have templates with multiple properties in order to compensate for the "rigid" way templates work. Well - not any more, introducing an easy to use Web Part Framework - (WPF)! Originally developed for the biggest EPiServer site in Norway, www.regjeringen.no (the Norwegian Government - with 300 000 + pages at launch with 2 000 + pages created every week) the WPF introduces new ways of working with content in EPiServer.

One of the most important aspects when the WPF was developed was to have a high usability level and at the same time give the editors enough freedom to work with content. Many systems have failed this task giving us flexible interfaces but with no thought of the actual usage - so combining a standard template approach with Web Parts seems a good idea. However, introducing this in your first customer meeting will (unless it is a demand) make EPiServer look complicated and hard to use and give the same editorial feeling as other other CMS's (it has nothing to do with the implementation).

The different web parts included with the framework are page list, page, link, banners (pictures) and the WYSIWYG editor! Go to EPiCode and check it out with full source for free.

Want to see what it looks like? Watch the screencast

PS. With the new way of installing modules in CMS 5 you can actually get the Web Part Framework installed without compiling or editing web.config. Get the *.zip