.NET Forge Blogs: New Posts

6.0.8 Updates for your system

Ann Slyshkina — Tue, 13 Sep 2011 08:45:33 UT

We finished our work on some important updates for 6.0.8. They include bug fixes and new functionality:

New features:

Customized Information block element creation forms
Collaborative blogs
Support of authentication and authroization via Active Directory / LDAP

6.0.7 Updates for your system

Ann Slyshkina — Mon, 29 Aug 2011 13:01:23 UT

Update 6.0.7 for Bitrix .NET Forge is now available. It includes fixes in the Main and Information Blocks modules.

Updates description:

Insert include area (bitrix:includeArea) component: fixed bug in path handling;
Catalog (bitrix:catalogue) component: filtering items by custom properties values;
Control Panel: fixed the link for Live ID key request.

Integration with Active Directory and collective blogs will be available in the upcoming updates.

How to add syntax highlighting to .NET Forge CMS forum

Alexander Buynyachenko — Wed, 17 Aug 2011 07:21:54 UT

In this article I will show how to add syntax highlighting feature to .NET Forge CMS forum, by writing about 50 lines of code.

.NET Forge CMS forum post editor allows you to insert code snippets to you post, but when you add post you’ll see gray text like this:

Unfortunately, our system do not have code highlighting feature in forums, but on sites such as ours or gotdotnet.ru highlighting do exists. It is made as a custom feature, using third-party free highlighting javascript plugin. It could be easily integrated in any our site. So, let’s begin.

First of all, to make an example integration I installed “Community site” solution from the list of available fast to deploy sites in CMS installation wizard. I have chosen that solution because it have forum with some posts ready to work with. Of course, our intergration won’t depend on this particular solution.

Now we have a forum, let’s get highlighting plugin itself. It is called Syntax Highlighter, and can be downloaded on product download page on site of it’s developer. The product archive contains quite a lot of files, basically we need these:

/scripts/shCore.js – plugin core script
/styles/shCore.css – common styles
/styles/shCoreDefault.css – default color scheme styles
Js files from brushes folder – we need to select highlighting brushes for needed languages, in this example we will use files for C# and SQL - shBrushCSarp.js, shBrushSql.js

Then we put these scripts to /js folder in our site, and style – to /css folder. Now, we have to incude references to them in our template.master, between and tags:

<<%= "link" %> rel="stylesheet" type="text/css" href="<%= SitePath %>/css/shcore.css" /> 
<<%= "link" %> rel="stylesheet" type="text/css" href="<%= SitePath %>/css/shcoredefault.css" />

Now we need to write some code on our own, the code that will find all blocks that have to be highlighted and will call highlight method of our plugin on all them. Let’s create main.js file in /js folder in fill it with the following code:

if (typeof (MySite) == "undefined")
	MySite = new Object();
//helper method, searches brush from collection by name
MySite.findBrush = function (brushName, brushes) {

	for (var brush in brushes) {
		if (!brushes.hasOwnProperty(brush))
			continue;
		var br = brushes[brush];
		if (!br.aliases)
			continue;
		for (var i = 0; i < br.aliases.length; i++)
			if (br.aliases[i] == brushName)
				return true;
	}
	return false;
}
//find all blocks of code that requires highlighting and calls SyntaxHighlighter.highlight for all of them
MySite.HighlightCode = function () {

	var element = document.getElementById('content');
	if (!element)
		return;

	var tagss = element.getElementsByTagName('PRE');
	if (!tagss || !tagss.length)
		return;

	var tags = [];
	for (var i = 0; i < tagss.length; ++i)
		tags.push(tagss[i]);

	for (var i = 0; i < tags.length; ++i) {
		var tag = tags[i];
		var parentNode = tag.parentNode; if (!parentNode || parentNode.tagName != 'DIV' || (parentNode.className != 'forum-code-box' && parentNode.className != 'blog-code-box'))
			continue;

		var brush = tag.className;
		if (MySite.findBrush(brush, SyntaxHighlighter.brushes))
			SyntaxHighlighter.highlight({ brush: brush }, tag);
		else
			SyntaxHighlighter.highlight({ brush: "c#" }, tag);
	}
}
//Creates forum quotation processor for right displaying code when qouting, this code executes
//when user click on "quote" link and returnes code text without makrup added by syntax highlighter. Next this text will
//become quote text 

if (typeof (Bitrix) == "undefined")
	Bitrix = new Object();
if (typeof (Bitrix.ForumQuotationProcessors) == "undefined")
 Bitrix["ForumQuotationProcessors"] = new Object();

Bitrix.ForumQuotationProcessors["SyntaxHighlighter"] = function (html) {

	var m = null;
	if (typeof (window.SyntaxHighlighter) != "undefined"){
		var m = (/\]*?class=\"syntaxhighlighter[^\"]*\"[^\>]*?\>/i).exec(html);
		if(m!=null){
			m = (/\]*?id=\"?(\w+)\"?[^\>]*?\>/i).exec(m[0]);

			if(m!=null && m[1] in window.SyntaxHighlighter.vars.highlighters)
				return window.SyntaxHighlighter.vars.highlighters[m[1]].code;
			}
		}
	return null;
}

Adding another reference to main.js to template.master between and :

And the last thing – we have to register a call to our HighlightCode method as startup script, so it will be executed after a page is successfully loaded. Let’s use RegisterStartupScript of Page.ClientScript object to achieve this. We can put this code in template.master or just in forum page:

protected override void OnLoad(EventArgs e)
{
   base.OnLoad(e);		    
Page.ClientScript.RegisterStartupScript(Page.GetType(), "highlightcode", "MySite.HighlightCode();", true);
}

Now, if everything was done right, we’ll see our code highlighted after page reload:

6.0.6 Updates for your system

Ann Slyshkina — Tue, 12 Jul 2011 08:26:52 UT

Update 6.0.6 for Bitrix .NET Forge is now available. It includes fixes in the Main and Information Blocks modules.

Updates description:

site template editing page (~/bitrix/admin/TemplateEdit.aspx): fixed bugs occurring when a new template is saved – saving of a template name, its description and path;
Insert include area (bitrix:includeArea) component: fixed bug occurring when creating a new included area in a non-existent folder;
Main module: fixed bug when reading a cache file with links to inaccessible dynamic assemblies;
Main module: optimization of users authentication mechanism;
photogallery components: fixed bugs in templates.

Authentication against Active Directory + .NET Forge

Grigoriy Zavodov — Tue, 12 Jul 2011 06:19:29 UT

How can one authenticate against Active Directory? This question recently came up in our forum. I answered that the ActiveDirectoryMembershipProvider class is a full-service provider for authentication for Active Directory. But that lead to other questions: how does one 'register' the provider correctly? Can 2 providers be active at the same time? How can users from different domains be authenticated? Realizing that this was only the beginning, and that the forum would not be the best position to fend off the barrage, I retired, promising to cover the matter(s) in my blog. Here is the keeping of that promise.

So, our task is to authenticate users of a site through Active Directory. Usually, this issue comes up when a website is being created for an organization that has Active Directory deployed.

So, let’s get to it. We launch .NET Forge Community. In the configuration wizard, we mark 'Do not install a site solution' – we’ll start from a clean slate.

Note: ActiveDirectoryMembershipProvider requires the Full Trust level settings.

Strict security policy is required for сorporate a corporate website. We’ll disable access to anonymous users. We choose the 'Section(Folder) Access' point in the 'Edit Section' menu and revoke the 'Execute executable files' from the 'All Users' and grant that only to the 'Registered Users'.

To authenticate users in the site root, we create an entry page (login.aspx), setting only the Authentication on it (system.auth) with the default settings. We open this page to anonymous users by choosing 'Access' in the 'Edit Page' menu and grant the 'Execute executable files' to the 'All Users'. Now 'strangers' will not be permitted beyond the opening page of the site.

Now we’ll activate the authentication provider for Active Directory. This requires editing the web.config. Add a connection string to Active Directory in the connectionStrings.

Determining the connectionString parameter may present some difficulties, so we will spend some time on this. The format of a connection string is LDAP://server/dn. As you see, it’s in URI format, starting with the definition of the protocol name LDAP (in all-caps). Then server – this is the name of the server, domain or IP address. In the documentation, there is a strong recommendation to use the fully qualified domain name or FQDN. The next item, dc.netforge.loc, is the server dc in the domain netforge.loc. The connection is usually set on port 389. If your Active Directory server is set on a different port, you will need to enter the point number (for example: dc.netforge.loc:377). Lastly, we have dn – the distinguished name of the object, which is comprised of a list of 'relative distinguished names', separated by commas. A relative distinguished name has the form NameAttribute=Value. CN=User,DC=netforge,DC=loc – the group Users (attribute CN – container), domain netforge.loc (attributer DC – domain component).

Now we create a new authentication provider, which will be a user created using the connection string to Active Directory.

Note: connectionUsername and connectionPassword have to be supplied in plain text. If domain admin account is specified, you should encrypt this configuration section along with the connectionStrings section.

Please note that the BXSqlMembershipProvider hasn't been removed. It is done to allow the built-in administrator to log in. The Authentication system will perform authentication against each provider sequentially. It will stop on success or at end of the sequence. That is why order is important. In our example, ActiveDirectoryMembershipProvider goes after BXSqlMembershipProvider due to performance considerations. In my test environment BXSqlMembershipProvider responds much faster than ActiveDirectoryMembershipProvider.

Let’s test our solution. We open the site and try to enter as a user zg of the netforge.loc domain . The user name is in the format zg@netforge.loc – is the UPS (User Principal Name).

Login has been successful. But where did the user whose name is now displayed in the Authorization Form component (system.login) come from? We, of course, did not create it.

We enter the site under a built-in administrator user account (it was important to leave the SQL provider untouched) and check the list of site users (~/bitrix/admin/AuthUsersList.aspx). Indeed, there is a new user with a name that coincides with the domain account. So it is clear that it was created automatically after successful authentication by the Active Directory provider.

So what advantages have we got here? The source code requires no changes and will work normally after membership provider change. A call to BXIdentity.User property will return an instance of BXUser as before.

'Savvy', a reader asks: 'What if I want handle user names in the form DOMAIN\user, that is, in SAM (Security Account Manager) format?' By default, the Active Directory provider works with names in the UPN (User Principal Name) format. To use SAM format, simply add the attributeMapUserName attribute in the provider definition tag with the value SAMAccountName. our case, you can then enter the system under the name NETFORGE\zg.

There’s one last question: how to authenticate users from several domains? Do you already know the answer? Probably so – you simply add the needed providers as in our example. But remember that receiving a response from an Active Directory provider takes a certain amount of time. If the provider which confirms the identity of the user is at the end of a long list of Active Directory providers, the authentication process will be noticeably long. Of course, this is true only for the first login – afterward the binding to the provider will be saved.

So that’s all. Now we know how to authenticate users through Active Directory. In this article the only thing left is the issue of authentication by role. The site features user roles, but does not know anything about Active Directory groups. I intend to address this topic in one of the next articles.

Was the time spent reading this article well-spent? In any case, please leave commentary and ask questions. I’ll be happy to get feedback.

Topic links:

Excellent B2B Cargo Web Application built with .NET Forge CMS

Alex Reznor — Mon, 27 Jun 2011 16:35:01 UT

Company and Implementer

A ground-breaking project on the .NET Forge CMS platform is slated to be launched by long-time Bitrix partner GALS Soft in August 2011. The project is being developed on order from ground transportation services specializing in oversized shipments and working in the European and Russian markets. The company serves about 200 regular clients and manages a network that includes 7 warehouses and about 500 factories which will be the main users of the system.

Project Goals

The project goal is to create a system which unites a large number of logistics services companies in Europe and Russia. Small companies have an advantageous, individual approach to work with clients, but at the same time they can be united to solve organizational issues more effectively and expand their client base.

The Solution

GALS Soft designed and developed a B2B system on the .NET Forge CMS platform. The system manages all the interaction between clients and services providers from the moment of order placement to the confirmation of delivery. The system is accessible to users through a web interface.

"The basic tasks at hand were to determine the shipping route for a given shipment, including determining what warehouse or warehouses would be involved; optimizing the loading of transport vehicles, monitoring of the shipment's condition at all points along the route, and management of warehousing logistics, etc. Because of the supreme quality, flexibility and ease of use we've decided to built this elaborate project with .NET Forge CMS. We did the right thing because the services offered on this web resource required a lot of custom changes and integration with business-specific solution, and the .NET Forge CMS was easy and fun to work with." - said Vadim Mityakin, CEO of GALS Soft.

The resulting system has a payment system integrated with a business process which enables the handling of various phases of the process by the service provider who controls that particular phase.

Accessing the Cargo B2B Service Online

Each user is provided with a personal area and access to the sections and data which correspond to his or her role in the system. Shipment tracking and other options are provided, as well.

Example of personal area

Each new order initiates a new business process. When an order is placed, the system determines which of the possible shipping routes will be most efficient with respect to available warehousing and vehicles and formulates an estimated shipping time. The system also monitors the transportation process, creating lists of incoming and outgoing orders for all intermediate storage facilities, accounting for the order as part of the load in all vehicles involved in the shipping process, and ensuring the integrity of the order if the order contains packages originating or shipped by different routes.

Interface of the web application

The implementation is in full swing now, and we wish both the developer's and the client's team a smooth and successful start.

Down the Rabbit Hole!

Dmitry Pyalov [Дмитрий Пялов] — Mon, 27 Jun 2011 09:55:00 UT

New technology is always a bit of a black box at first. We can operate the GUI, even write a little code. But it’s very easy to make serious errors in a project if one does not have an understanding of how it works inside or how to use the product’s capabilities the right way. That’s why it’s important to learn the basics of the product architecture.

For example, you need to understand how movie clips work and how the scene is built when you’re writing in Adobe Flash. You should know what Activities and Intents are when developing in Android – Google has a great article, describing these basics.

So, the main intent of this post is to give developers the fundamentals of the .NET Forge structure and to familiarize them with the core tools the CMS provides and gradually getting deeper down the rabbit hole.

Website Structure

.NET Forge CMS is built on top of Web Forms. It’s not true to say that we totally rely on web forms – many problems were solved with custom solutions, but technically, a website built with .NET Forge CMS is still a Web Forms application. That’s why ASP.NET developers can use their legacy code and easily convert their skills to develop in .NET Forge CMS. We don’t prevent using the standard ASP.NET techniques, but still we propose different, easier and clearer way to build websites.

The site structure is defined by the physical location of files and folders. There are also ways to create a virtual site structure, e. g. to organize a catalog or news feed.

Pages

So the website is made of ASPX-pages, derived from BXPublicPage class(the descendant of System.Web.UI.Page), which can be overridden (there is an option in the product settings to define the base class for pages newly created through the web interface).

BXPublicPage performs the following core tasks:

Assigns the correct site template based on the current site settings. This is done in the PreInit phase.
Provides the API to link CSS- and JavaScript-files.
Stores the page properties (string values), specific for every page.
Performs anti-CSRF token validation.
Solves different infrastructure problems, e. g. setting the correct “action” attribute to the “form” tag.

Quote
All page content should be placed inside the content areas (). This is required because the page is displayed within the site template (master page).

Site templates

A site template is a MASTER-page (in Web Forms terms) and all the required resources (stylesheets, scripts, images etc.). All site templates are located in separate folders inside the ~/bitrix/templates/ folder. The master page must be named as template.master. There are also files which have special meaning for the template: template_styles.css and styles.css – both files are included in every page automatically. The first file is the main CSS stylesheet of the template. The styles.css file is also included in the WYSIWYG-editor and contains styles, which can be used to decorate the text – it should contain styles that are meaningful for the content editors.

The site template master page should be derived from BXMasterPage and contain one required control: . TemplateRequisite is a special control, which provides infrastructure for the core services to access the page. It is in charge of rendering the top administrative panel on the page, linking the required scripts and controls. TemplateRequisite must be the first control on the form. The top panel can be detached from the form and placed separately with the help of control. It will be created automatically by the TemplateRequisite in case you don’t declare it yourself.

Quote
It just happens, that Web Forms allow only one server form. .NET Forge requires this server form to be on every page and the TemplateRequisite to be placed inside (so we define the form in the master page). We are constantly improving the product and reducing the CMS’s dependence on Web Forms. For example, the top panel (BXHermitageFrontEndPanel) now can work outside the form, making the template layout simpler.

Quote

It just happens, that Web Forms allow only one server form. .NET Forge requires this server form to be on every page and the TemplateRequisite to be placed inside (so we define the form in the master page). We are constantly improving the product and reducing the CMS’s dependence on Web Forms. For example, the top panel (BXHermitageFrontEndPanel) now can work outside the form, making the template layout simpler.

Sites

Actually, this term has already been mentioned above in the text. Site in the scope of .NET Forge is a separate business layer entity. This entity is defined when any public page code executes. The current site from the defined list is determined by the current host name and the current executing file path. Other business entities can be linked to one site or another, e.g. information blocks, blogs, forums. The current site can be identified by the call to BXSite.Current.

The current site template is determined by the current site settings and can be set up through the web interface.

Components

A component, in terms of .NET Forge, is a separate block on the page, performing some business task. Technically, a component is an ASP.NET user control. All components are placed in the ~/bitrix/components/ folder, followed by grouping folder (namespace folder), where each component lies in separate folder, e. g. ~/bitrix/components/bitrix/news.list/, where bitrix (the second one in the path) is the namespace and news.list is the component folder. All the components in the bitrix namespace are supported by our company and must not be modified – you will lose your changes while updating the product to a newer version. You can copy the component to your own namespace, modify it and use it as the default (updates will be accessible in the bitrix namespace).

In fact, component names consist of the namespace folder and the component folder names, e. g. bitrix:iblock.element.webform, where bitrix is the namespace and iblock.element.webform is the component folder name.

A component performs business logic – it processes input and prepares the resulting data. All the logic is concentrated in the component.ascx file. In spite of the fact, that this is technically a user control, it doesn’t output anything. Components are declared as ASCX controls only because this is the simplest way to create a dynamically compiled object with native source code editing support by Visual Studio.

Quote
A good habit is to set the proper names to component and template classes. In our components we place the classes in the <CompanyName>..Components namespace and name the component and template classes Component and Template correspondingly. Taking the bitrix:iblock.element.webform component as example, we’ll get the IBlockElementWebformComponent and IBlockElementWebformTemplate classes in the Bitrix.IBlock.Components namespace.

Quote

A good habit is to set the proper names to component and template classes. In our components we place the classes in the <CompanyName>..Components namespace and name the component and template classes Component and Template correspondingly.

Taking the bitrix:iblock.element.webform component as example, we’ll get the IBlockElementWebformComponent and IBlockElementWebformTemplate classes in the Bitrix.IBlock.Components namespace.

Component templates

Components don’t render output – they process and prepare data. To form the HTML, component attaches template. A template is a simple ASCX file, derived from BXComponentTemplate. Component chooses a template from the various templates available depending on it’s settings and the template file location. The template file is named template.ascx and can be located in the following places:

In the component folder (~/bitrix/components///templates//). These templates are called system templates. You should not place custom templates for the standard components here because they can be rewritten by the update system.
In the site template folder (~/bitrix/templates//components////)
In the composite component template folder (%template_folder_path%////)

As with site templates, component templates can contain files that are automatically included in the page. These are style.css and script.js for CSS and JavaScript correspondingly.

Component parameters

Components may have parameters, which are editable through the web interface. The parameters are defined by overriding the PreLoadComponentDefinition and LoadComponentDefinition methods. All parameters with their default values are declared inside PreLoadComponentDefinition – this method is called each time the component executes. You can provide an extended description, like a set of predefined values in the LoadComponentDefinition override. These operations can be heavily loaded and connected with database queries – that’s why this method is only called when you open the component setup GUI.

Composite components

A composite component is a component whose templates contain other components. Composite component templates may contain multiple ASCX files, e.g. index.ascx, items.ascx, edit.ascx etc. Those files are called composite component template pages. In this case the composite component does no serious processing – its task is to choose the right template page and set up the parameters for the components on this page depending on the current request context.

So, a composite component is a kind of controller, and its template pages are views that are switched by the component. A composite component is usually the only component on the page and provides the functionality of a whole section of the site.

Composite component parameters are automatically assigned to its nested components.

Why components?

It may seem that components add significant overhead and complexity to the development process. This is only partly true. I’ll describe what benefits you’ll get using the component model:

Components create a standard – this means, that they are easy to transfer between projects and between people. Components are can be easily packaged into modules.
Components are easy to configure through the web interface.
Components are supported by the site administration GUI (“Amber” interface, WYSIWYG editor)
Components are reusable – no need to duplicate logic for another task – customizing the template is usually enough.
Components are easy to support - your client can do the task without your involvement, thus reducing the cost of support.

Event if you just need to output simple dynamic information it is better to wrap it in a component without parameters and logic – it will be correctly displayed in the WYSIWYG editor as a separate block, thus making the page structure more consistent.

Development levels (“down the hole”)

Wrapping up this lengthy post, .NET Forge offers the following 4-level site development model (separated by the complexity of work to be done):

Site pages – this is where we place and set up our components and content
Site and component templates – here we make an HTML layout, almost no code required
Components – written, when we require custom business logic on our site
Modules, DLL assemblies – this is the lowest (deepest) development level, where we create APIs to use in components, using the .NET Forge core API. I would require more than one post to describe this functionality.

New version 6.0.5

Alexander Buynyachenko — Mon, 27 Jun 2011 05:38:20 UT

We just finished our work on update 6.0.5. It contains fixes for System Core, Infoblock and Blog modules and some interface improvements.
What we've done:

Ratings ( Core module ) : logic of counters fixed
Ratings ( Blog module ) : the "BloggingActivity" component logic was fixed
Interface: "Copy component template" dialog is fixed, "undo" feature added for "copy component template" operation.
Components blog.personal, iblock.hierarchy, news.line, media.gallery, media.player - fixed working of components in cached mode.
Control AdminUserLink - fixed bug with displaying user without a Display Name.
"Amber" interface - minor fixes.

Citycelebrity.ru: A nationwide social network built with Bitrix .NET Forge CMS

Alex Reznor — Thu, 16 Jun 2011 11:48:37 UT

Hello Everyone!

As my very first blog post, I'd like to publish a brand new case study on how Bitrix .NET Forge CMS was implemented by Galssoft, a Bitrix Gold Partner, for developing a nationwide social network for creative and active people. I really liked the project from the very beginning, and now it got really big and successful.

Company Profile
COPY & COPY, the first Russian copyright bureau. COPY & COPY was founded in 2002 as the first Russian copyright bureau. Today, COPY & COPY offers services in the sphere of product development – both as it concerns new products and re-branding or repositioning of existing products and services. Project objective.

The main page of the Citycelebrity.Ru portal

Project Goals

CITYCELEBRITY is a nationwide network for active and creative people – from artists to entrepreneurs, scientists to artisans. It is a communications platform where future stars can promote themselves and their activities in the context of their own city. Citycelebrity.ru is a network of city portals for famous people, and those who want to become famous. Specific goals:

give users a tool for self-promotion and for the demonstration of their potential and accomplishments;
attract people and entities which could use their services or otherwise be interested in them: galleries, museums, institutes, foundations, advertisers, governmental organizations, as well as partners and other creative people;
provide convenient and effective communications between users and exchange of opinions and experience among collaborators.

The Solution

Citycelebrity.ru is a portal which automatically generates for any city in Russia with a population of more than 300,000 people, with plans to move to the level of 100,000. The portal begins working as soon as the first user registers. All residents of Russia can become members by choosing the city nearest to them from the list.

Elements and sections displayed on the Citycelebrity.Ru portal

The community created by the portal is a social network. The portal structure is organized in a system of posts of various types: article, event, master class, photo gallery, video presentation, or tele-conference. Depending on the type of post, there are various additional fields. When any post is opened on the portal, related posts, selected by topic, section, and title are displayed on the right-hand side of the screen.

The portal is built on the Bitrix .NET Forge CMS platform. An internet resource of this type has a high level of traffic, so high performance capability of the platform was an essential feature. Aside from the social networking functionality, the portal has radio and video broadcasting capabilities, which required special configuration of the server.

In development, the platform components which were used were blogs, search, user fields, banners, and advertising areas. Additional services were created in the framework of the product’s unique architecture, allowing uniform processes of development and support. The project is unusual in its orientation to an extremely wide regional audience. Support for the resource is performed by active users and an editing team. Convenience support of user groups is executed via a specially designed administrative interface.

New User Register form on the Citycelebrity.Ru portal

Personal User Page / User Profile at Citycelebrity.Ru

The Result

Today, Citycelebrity.ru is a completely functional portal serving the Russian market. There are 14385 registered users and in more than 70 cities. There are about 100 organization-type users.

Galssoft keeps developing and maintaining the project. It is being dynamically improved, also thanks to the development of new modules and expanded functionality that become available with each new product version of Bitrix .NET Forge CMS.

New release 6.0.4 is out!

Alexander Buynyachenko — Wed, 15 Jun 2011 10:58:19 UT

We have just released new update 6.0.4, that includes fixes of modules and components. Kernel, Communication Utility, Blog and Infoblock modules were updated. Also, components "news" and "catalogue" were fixed, and we improved "Create Page" and "Edit Page" dialogs. Thanks to all who helped us to found this bugs.