Gentics Portal.Node 4.6.2
Gentics Portal.Node 4.6.1
Bugfix RT58409
When using the DatasourceQueryImp, sorting by multiple columns did not work. This has been fixed now.
Bugfix RT58428
When the GenticsContentPortlet returned binary data, the Cache-Control: max-age response header was always set to a value of 5184000, which allowed the content to be cached for 60 days in the browser. This was not always appropriate. It is now possible to set the Cache-Control:max-age to a different value by using the pnode Parameter “max-age”. It is even possible to use Expressions to set the max-age depending on attributes of the returned content object. For details, see the pnode parameter list of the GenticsContentPortlet in the Reference Documentation.
Gentics Portal.Node 4.6.0
Manual Change
Java Compiler Update
The compiler settings for the shipped java libraries were changed. It is now mandatory to use at least JDK 1.7.
Manual Change
Product structure changes
- Various deprecated internal non-api classes were removed. (e.g: GenticsContentModule2)
- Various classes for Gentics Content.Node and Gentics Portal.Node were moved from node-lib to either contentnode-lib and portalnode-lib.
Enhancement
Gentics Portal.Node 4.6.0 now supports Apache Tomcat 7.0.23. Take a look at our compatibility list for more details
Enhancement
The runtime profiler servlet configuration root path can now be configured using the profiler.config.rootpath system property.
Enhancement
Datasources used in a Gentics Portal.Node Server will now be checked with autorepair2 instead of autorepair by default.
Bugfix RT58150
The error behaviour of the GenticsImageStore web application has been changed: There are now minimalistic error pages for the most common errors defined, that will not give away any server specific information. When the image to be resized cannot be found, the GenticsImageStore servlet will return a 404 (Not Found) response. If the path to the image to be resized does not match the configured pattern, the GenticsImageStore servlet will return a 400 (Bad Request) response.