Gentics Portal.Node Changelog Summary
The online version of the changelog can be found hereGentics 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 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.