Bugfix RT58256
Unnecessary output of WARN messages like “WARN TagPartType not filled, but is still rendered. (TagPartType is null, data inconsistency – invalid link to tag {tagClass:class com.gentics.contentnode.object.ContentTag} {tagId:0} {valueId:47110815})” in the publish log will be omitted now.
Bugfix RT58408
Loading images (path /folder/getFiles/{folderId}) or items (path /folder/getItems/{folderId}) using the Java REST API client failed with some deserialization errors. This has been fixed now. The result for the calls to /folder/getFiles/{folderId} and /folder/getItems/{folderId} will contain an additional property (@class) for each file or item, that specifies the Class to be used for deserialization in the Java REST API client.
Bugfix RT58434
When a published page was republished without any changes, a log entry like “Create Major Version (updated version 9.0 to 9.0)” was written which suggested that a new version should have been created. In fact, when republishing an already published page without any changes will not create a new version and such log entries are incorrect and will not be written any more.
Bugfix RT58139
When uploading a new image/file and then directly clicking the file, editing it‘s object properties did not work (produced an SGB). This has been fixed now.
Bugfix RT58388
The Time Management during a publish process will now be done earlier (before the initialization of the publish process) in it‘s own transaction. This fixes problems, where pages, that are published with “publish at” are possibly not published with the correct contents.
Bugfix RT58448
When starting a Tagtype Migration process, a new background Thread is created, which is never removed. This has been fixed now.
Bugfix RT58422
When using a PostProcessor in a tagtype migration for a template, the template was not migrated although the job finished with success. This has been fixed now.
Bugfix RT58312
In rare cases, the application server for Gentics Content.Node would not start properly due to an unexpectedly terminated initialization job, which the startup routine failed to detect. This has been fixed now. If an initialization job terminates, an exception will be logged and the application server will start normally.
Bugfix RT58437
When uploading new files or changing files, the uniqueness check for the filename (with publish directory) was not done case insensitively. This could cause creation of files for which the publish path only differed in case. This subsequently could cause problems in the frontend. The uniqueness check has been fixed now to be case insensitive.
This Gentics Content.Node version includes the Aloha Editor 0.24.34 – 03.09.2014