Gentics Portal.Node Changelog Summary

Gentics Portal.Node 4.4.3


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


Enhancement RT#56997

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.


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 RT#57008

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


Bugfix RT#57193

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 RT#56997

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 RT#56705

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


Bugfix RT#56788

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

Bugfix RT#56784

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.



Gentics Portal.Node 4.4.1


Bugfix RT#56151

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


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


Bugfix RT#55361

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


Bugfix RT#55381

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


Bugfix RT#55379

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 RT#55592

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 RT#55593

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.



Gentics Portal.Node 4.3.0


Enhancement

Gentics Portal.Node will now support using multichannelling datasources (for reading). See the reference documentation about details on configuration and channel selection.


Enhancement

The GenticsContentPortlet now supports streaming of binarycontent, if the attribute is stored in the filesystem.


Enhancement RT#54982

The new Portal Page property suppress_gentics_pp will suppress adding the gentics.pp parameter to URLs rendered in a Portal Page, even if that Portal Page is not the current Portal Page and was itself rendered using the gentics.pp parameter.


Bugfix RT#54025

The generation of beautiful URLs did not work when two mapping existed with the only difference that one mapping had an additional parameter mapped. This has been fixed now.


Bugfix RT#54418

It is now possible to use PostProcessors also with the ExpressionEvaluator (using the filter method).


Bugfix RT#54418

The ExpressionEvaluator will now also support the filter() function (using PostProcessors) in the match method.


Bugfix RT#54418

The datasourcetreecomponent will now support the filter() function (using PostProcessors) in the noderule, even if the rule is not transformed into a content repository query, but is evaluated in the program logic.


Bugfix RT#54349

When using a rule like “object.[optimized_attr] CONTAINSONEOF [null]” to query objects from a datasource, the generated SQL statement was invalid. This has been fixed now, this special case will be treated correctly now and the resulting SQL statement will be valid.


Bugfix RT#54510

The GCNAuthenticationManager will read the session secret in a different way after login to the CMS backend to comply with the latest security fixes of Gentics Content.Node.



Gentics Portal.Node 4.2.0


Enhancement RM6440

Added support for configurable RequestDecorators to intercept and modify requests to the GenticsImageStore. See the index term “GenticsImageStore” in the reference documentation and the interface “com.gentics.api.imagestore.RequestDecorator” in the API documentation about details.



Gentics Portal.Node 4.1.1


Bugfix

Some fixes and enhancements from previous releases were missing in the release 4.1, which have now been re-added:

  • Fixed the way, files are located in the File Loader of the Template Manager to avoid Exceptions thrown when Gentics Portal.Node is used in BEA WebLogic.
  • Fixed resizing of images using the GenticsImageStore, that have image/x-png or image/pjpeg as mimetype.
  • Fixed clearing caches for portlets due to modifications when used on WebLogic Application Server.
  • It is now possible to configure the context, under which JNDI DataSources for datasource handles are looked up. This might be useful when running in an environment, that does not bind the datasources under the context java:comp/env, as required by the servlet specification.

Bugfix

Re-added the Profiler.war to the Update Package.


Bugfix RT#51933

Fixed image resizing using the GenticsContentPortlet or GenticsContentModule: When the image could not be resized (e.g. because it was an animated GIF), nothing was returned. This behaviour has been changed now: the original (unresized) image will be returned, but still an error logged on the server.



Gentics Portal.Node 4.1.0


Enhancement

The Portal.Node build process was changed and thus the shared libs were renamed.


Enhancement

The Portal.Node Profiler was moved into an separate war file.


Enhancement

The Portal will now support reading of ContentRepositories that have some binary or long text attributes stored in the filesystem instead of the database. See index term “ContentRepository|Configuration” (configuration parameter “attribute.path”) in the reference documentation and consult the Gentics Content.Node guides pages in the Gentics Infoportal for details about the feature “cr_filesystem_attributes”.


Enhancement

Datasources of type ContentRepository that use caching can now be configured to automatically fill the cache in a background job. See index term “ContentRepository|Configuration” in the reference documentation for details.


Enhancement

The new filter() function allows using instances of the interface PostProcessor to move complex filtering logic from the rule (which would be transformed in possibly slow SQL statements) into Java Code. See index term “Functions|filter()” or “PostProcessor” in the reference documentation. Also see the PostProcessorExample in the SDK (which is described in the SDK Guide).


Enhancement

The GenticsContentPortlet will now render an additional Aloha setting so that Gentics Content.Node can hide the ribbon when the Portlet renders an edit view.