Gentics Portal.Node Changelog Summary

Gentics Portal.Node 4.4.3


Enhancement

It is now possible to change the sorting of the datasourcelistcomponent by setting the component properties “sortby“ and “sortorder“. The readonly property “count“ will return the total number of items in the datasourcelistcomponent. See index term “DatasourceListComponent” in the Reference documentation for more details.


Enhancement RT56997

When prefilling attributes for a multichannelling datasource, the attributes will first be checked in the cache. Attributes will only be prefilled, if more than “prefetchAttribute.threshold“ objects shall be prefetched or if more than “prefetchAttribute.cacheMissThreshold“ values are not found in the cache. See the section “Attribute Prefetching” in the Reference documentation for more details.


Enhancement RT57008

Contentrepository datasources will now support the newest MS SQL JDBC driver 4.0 for connecting to Microsoft‘s SQL Server.


Enhancement

Increase performance of cache warming for multichannelling datasources by optimizing the SQL statements.


Bugfix RT57193

The PortalConnectorFactory now provides access to datasources, that are managed by a Gentics Portal.Node Java Server. This allows sharing datasources (and their caches) between portlets and other components outside of the scope of the portal (e.g. servlets). Additionally, it is possible to register new datasource handles and datasources using the PortalConnectorFactory, which makes them available in the portal as well. See the section “Gentics .Node PortalConnector Java API“ and the “API Reference” in the Reference documentation for more details.


Bugfix RT56997

When prefilling attributes for a multichannelling datasource, sometimes empty attributes were not put in the cache, which caused additional SQL Statements, when those attributes were accessed. This has been fixed now.


Gentics Portal.Node 4.4.2


Bugfix RT56784

When the language fallback changes the current page of a GenticsContentPortlet, the triggered onChange event will now have the contentid of the new page as property.


Bugfix RT56705

The operations “clearcache“ and “load” (by contentid) of the DatasourceAction did not work with multichannelling contentrepositories, and have been fixed now.


Bugfix RT56788

Two issues with redirects were resolved:

  • Using the SendRedirectAction in a callable action, that was executed using the docallableaction() function in a reaction did not work.
  • When the portal parameter portal.response.redirect was set to redirect the request, this setting was not cleared for the next request, so every subsequent request would also be redirected (until portal.response.redirect was manually cleared).

Gentics Portal.Node 4.4.1


Bugfix RT56151

The caching implementation for CNDatasource and MCCRDatasource has been optimized to reduce the memory consumption for cached objects.


Gentics Portal.Node 4.4.0


Enhancement

The DatasourceQueryImp now supports selecting channels when used with a Multichannelling ContentRepository. See index term “DatasourceQueryImp” in the Reference Documentation for more details.


Enhancement

It is now possible to use the meta attributes “channel_id“ and “channelset_id” when filtering Multichannelling ContentRepositories.


Enhancement

The PortalConnectorFactory has a new method prefillAttributes() that can be used to prefill attributes for a given collection of objects fetched from a datasource.


Enhancement

The DatasourceAction now supports selecting channels when used with a Multichannelling ContentRepository. See index term “DatasourceAction” in the Reference Documentation for more details.


Enhancement

The Profiler Webapp file was added to the Portal.Node SDK Updatefile


Enhancement

It is now possible to choose multiple channels when using a Multichannelling ContentRepository (one for each channel structure). Queries will now be done across all currently selected channels. See index term “MCCR” in the Reference Documentation for further details.


Bugfix RT55361

Fixed a bug in the DatasourceQueryImp which caused an exception to be thrown when used with a Multichannelling ContentRepository.


Bugfix RT55379

If the Gentics Portal.Node was started without a Multichannelling ContentRepository configured, numerous errors like ‘No implementation found for AND for {com.gentics.lib.datasource.mccr.MCCRDatasource}‘ where logged. Those errors had no effect on any functionality and are avoided now.


Bugfix RT55592

When reading unset text attributes from a Multichannelling ContentRepository, null will be returned instead of an empty string (identical to the behaviour when reading from a non-Multichannelling ContentRepository).


Bugfix RT55381

Fixed the GenticsContentPortlet to always get the content from the currently selected channel when used with a Multichannelling ContentRepository.


Bugfix RT55593

When reading link attributes from a Multichannelling ContentRepository, where the link target does not exist, null will be returned instead of the linked contentid as string (identical to the behaviour when reading from a non-Multichannelling ContentRepository). Also, before this fix, an exception was logged, that will be omit now.