sensenet Releases Rss Feed

Updated Release: SenseNet 6.0 Beta 4.3 (Sep 16, 2009)

DanielJozsef — Wed, 16 Sep 2009 13:20:11 GMT

Release notes

We have completed the first working version of Microsoft Active Directory synchronization for Sense/Net 6.0. As we beleive this is a key feature that may be interesting to many of our potential users, we have decided to create a release containing this functionality. This is Sense/Net 6.0 Beta 4.3.

Work on Sense/Net 6.0 Beta 5, our next milestone release, is advancing at a rapid pace. Expect breathtaking improvements and new features in early November. :)

Apart from the AD Synch architecture, we have also fixed a few minor bugs since beta 4.2, so an upgrade is highly recommended.

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.3, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1 and 4.2

Upgrading an existing beta 4.1 or 4.2 installation to beta 4.3 requires no special procedures. Be aware though that many bugfixes have been made to the default database structure, thus it is best for development or demo purposes to do a clean Sense/Net beta 4.3 install instead of upgrading.

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Released: SenseNet 6.0 Beta 4.3 (Sep 16, 2009)

Wed, 16 Sep 2009 13:20:11 GMT

Release notes

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.3, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1 and 4.2

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Updated Release: SenseNet 6.0 Beta 4.3 (Sep 16, 2009)

DanielJozsef — Wed, 16 Sep 2009 12:57:07 GMT

Release notes

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.3, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1 and 4.2

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Created Release: SenseNet 6.0 Beta 4.3 (Sep 16, 2009)

DanielJozsef — Wed, 16 Sep 2009 12:56:00 GMT

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.3, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1 and 4.2

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Updated Release: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

alexkiss — Sun, 13 Sep 2009 20:04:09 GMT

Sense/Net 6.0 Beta 4.2 is a final bugfix release before we begin working on our next milestone, Beta 5. We have integrated several fixes from our custom enterprise projects, and wiped out several of the bugs that made it into 4.1.

Upgrading from Sense/Net 6.0 Beta 4

When upgrading an existing beta 4 installation to beta 4.2, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.
Also, remove action definitions from the CTDs beforehand, as their format has changed. Re-add them in the following format after the binary upgrade:
<Actions>
<Action name="Browse" />
<Action name="Edit" />

</Actions>

Upgrading from Sense/Net 6.0 Beta 4.1

Upgrading an existing beta 4.1 installation to beta 4.2 requires no special procedures. Be aware though that many bugfixes have been made to the default database structure, thus it is best for development or demo purposes to do a clean Sense/Net beta 4.2 install instead of upgrading.

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Released: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

Sun, 13 Sep 2009 20:04:09 GMT

Upgrading from Sense/Net 6.0 Beta 4

Upgrading from Sense/Net 6.0 Beta 4.1

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Updated Release: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

DanielJozsef — Tue, 08 Sep 2009 14:42:12 GMT

Upgrading from beta 4

Upgrading from beta 4.1

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Released: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

Tue, 08 Sep 2009 14:42:12 GMT

Upgrading from beta 4

Upgrading from beta 4.1

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Updated Release: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

DanielJozsef — Wed, 02 Sep 2009 12:50:42 GMT

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.2, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Released: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

Wed, 02 Sep 2009 12:50:42 GMT

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.2, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.
The AJAX functionality in the Folder SmartPage seems to fail on certain IIS 6.0 installations. We are looking into the reasons of this problem.

Created Release: SenseNet 6.0 Beta 4.2 (Sep 02, 2009)

DanielJozsef — Wed, 02 Sep 2009 12:48:15 GMT

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.2, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

Upgrading from beta 4.1

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.
Sometimes the Security tab on the Content Explorer shows an empty window. Clicking back to the content view, and opening the Security tab again will fix this problem.

Updated Release: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

DanielJozsef — Thu, 27 Aug 2009 11:28:02 GMT

This is a service release for beta 4.

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.1, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Smart Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.

Important Notes:

We still consider the Smart Application Model experimental technology, and thus namespace changes and other compatibility breaks are to be expected in this area.
We may change namespace names, class names and locations, class interfaces, content handlers, content type names, content type hierarchy, configuration and demo structure paths. Of course, this pertains solely to the namespaces and content types introduced for the Smart Application Model and the Workspace framework

Is it "Smart" or "Web" Applications?!

"Smart". Definitely, permanently. Please forget it was ever called anything else.
We dropped the ambiguous phrase "Web Application Model" entirely, the concept is and will continue to be called the "Smart Application Model".

Released: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

Thu, 27 Aug 2009 11:28:02 GMT

This is a service release for beta 4.

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.1, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Smart Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.

Important Notes:

Is it "Smart" or "Web" Applications?!

Updated Release: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

DanielJozsef — Thu, 27 Aug 2009 11:11:07 GMT

This is a service release for beta 4.

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.1, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Smart Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.

Important Notes:

Is it "Smart" or "Web" Applications?!

Released: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

Thu, 27 Aug 2009 11:11:07 GMT

This is a service release for beta 4.

Upgrading from beta 4

When upgrading an existing beta 4 installation to beta 4.1, you will need to move the /Root/System/Apps folder to /Root/Apps for Smart Applications to continue working properly.

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Smart Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer).
Permission handling is still unreliable under portals using the SmartApplication model. Pleas refrain from using this technology for production, mission-critical purposes.
The SiteMenu portlet fails to respect Index values in certain cases.
Two users cannot use the same e-mail address, even if the unique e-mail check is disabled.
The e-mail notification for administrators about new users seem to be unreliable.

Important Notes:

Is it "Smart" or "Web" Applications?!

Updated Release: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

DanielJozsef — Thu, 27 Aug 2009 10:22:42 GMT

Beta 4.1 is a bugfix release for Beta 4.

These Release Notes give you brief information about the Beta 4 release of Sense/Net 6.0 Content Repository and contain quick links which are useful for getting detailed information about usage and installation.

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Web Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

What is a Workspace?

In our terminology the workspace is a small portal area allocated for users to work in, share their ideas, documents, whatever can be stored in the ContentRepository. Sense/Net Workspaces are very similar to SharePoint or Alfresco Sites. The Workspace concept is based on the Smart Application model implemented in Beta 4.
For additional information, check out our wiki about Workspaces.

What is Sense/Net Smart Application Model?

The Smart Application model is a new feature of Sense/Net 6.0 for defining frontend templates to display and manipulate data in the Repository. Amongst a truckload of fantastic possibilities, it enables portal builders to create classes of Pages instead of Pages, and leave the task of linking Pages with Contents to be displayed to a smart automatism.

You can read detailed information about Smart Application Model in our wiki.

Requirements

Before installing, make sure your computer meets the software prerequisites and hardware requirements.

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer). This is an intrinsic limitation of context-sensitive queries.

Important Notes:

According to our promise in Beta3, we strive to avoid breaking existing functionality in future releases. However, we still consider the Smart Application Model experimental technology, and thus namespace changes and other compatibility breaks are to be expected in this area.
We may change namespace names, class names and locations, class interfaces, content handlers, content type names, content type hierarchy, configuration and demo structure paths. Of course, this pertains solely to the namespaces and content types introduced for the Smart Application Model and the Workspace framework

Created Release: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

DanielJozsef — Wed, 26 Aug 2009 16:54:21 GMT

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Web Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

What is a Workspace?

What is Sense/Net Smart Application Model?

Requirements

Before installing, make sure your computer meets the software prerequisites and hardware requirements.

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer). This is an intrinsic limitation of context-sensitive queries.

Important Notes:

Released: SenseNet 6.0 Beta 4.1 (Aug 26, 2009)

Wed, 26 Aug 2009 16:54:21 GMT

What was new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Web Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

What is a Workspace?

What is Sense/Net Smart Application Model?

Requirements

Before installing, make sure your computer meets the software prerequisites and hardware requirements.

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer). This is an intrinsic limitation of context-sensitive queries.

Important Notes:

Updated Release: SenseNet 6.0 Beta 4 (Jul 24, 2009)

alexkiss — Sun, 23 Aug 2009 09:17:07 GMT

These Release Notes give you brief information about the Beta 4 release of Sense/Net 6.0 Content Repository and contain quick links which are useful for getting detailed information about usage and installation.

What's new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Web Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

What is a Workspace?

What is Sense/Net Smart Application Model?

Requirements

Before installing, make sure your computer meets the software prerequisites and hardware requirements.

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer). This is an intrinsic limitation of context-sensitive queries.

Important Notes:

Released: SenseNet 6.0 Beta 4 (Jul 24, 2009)

Sun, 23 Aug 2009 09:17:07 GMT

What's new in Sense/Net 6.0 Enterprise Portal & ECMS Beta 4?

Sense/Net Web Application Model: refined and improved
WebDAV functionality moved to SenseNet.Portal Layer
Sense/Net 6.0 now uses ExtJS 3.0 instead of ExtJS 2.2
Ext-base changed to jQuery
New Context-based portlets introduced for Workspaces and the Web Application Model
The binary fieldcontrol now has an „upload to binary property” feature

What is a Workspace?

What is Sense/Net Smart Application Model?

Requirements

Before installing, make sure your computer meets the software prerequisites and hardware requirements.

Installing

There are several installation guides available. Choose the one appropriate to the distribution you wish to use.

Start page for Binary Installation Guides
Source distribution installation guide

Forum

For additional information, check out our forum.

Known issues

The generic „properties” or „edit” SmartPage found under /Root/System/Apps/GenericContent/Edit throws an exception („multiple controls of the same id...”) on postback events if the Content being edited is a Page. This includes the scenario when the SmartPage is requested through its own URL.
When creating a new Content through the Workspace „Add new Content” wizard, one needs to explicitly enter both the desired Name and DisplayName properties of the new Content, otherwise it will be created and will show up in collections with the default DisplayName.
SmartFolders containing queries that use context-sensitive parameters such as "CurrentWorkspace" will display unexpected (erroneous) results when viewed from outside normal portal context (eg. from the Content Explorer). This is an intrinsic limitation of context-sensitive queries.