Changes with Gentics Portal.Node 4.4.0


Enhancement

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


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

The DatasourceAction now supports selecting channels when used with a Multichannelling ContentRepository. See index term “DatasourceAction” 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

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.


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.


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 RT55361

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


Bugfix RT55381

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


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 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.