Gentics Content.Node 5.13.2
Bugfix RT55127
Fixed possible DB locks during a publish process that caused problems when editing pages. This also fixes possible errors at the start of a publish process (because a lock could not be acquired).
Bugfix RT55299
When starting a multithreaded publish run, all tables were locked while connections were started, in order to get a 100% consistent state among those connections.
When some other SQL Statement was already running at the same time, this could lead to DB locks, and could subsequently freeze the whole CMS.
Therefore the tables will no longer be locked while starting the connections for a multithreaded publish run.
Bugfix RT55260
When using instant publishing, this possibly caused DB deadlocks while accessing the ContentRepository DB during a publish process.
This has been fixed now.
Bugfix RT55143
When getting pages from a folder via the REST API with the inSync parameter set,
an exception was thrown if pages were synchronized with another page that could
no longer be found on the system (i.e. was deleted).
Bugfix RT55134
When using the Gentics Content.Node Javascript API and node.js to upload a File into a Channel, the File was uploaded into the Master Node instead.
This has been fixed now, uploading files into channels is now possible using node.js.
Bugfix RT55211
Aloha Editor – GCN linkbrowser plugin: Fixed href not being updated after selecting a page/file from the link browser.
Now the href will be set to a # when a GCN page or file is selected. This also fixes the link-plugin targetRegex setting not correctly working.
Bugfix RT54731
Fixed a minor bug that sometimes caused flag icons not to be shown for start pages set in a folder.
Bugfix RT55065
When exporting, export warnings were generated for excluded objects. This is fixed now, export warnings are generated only
for non-excluded object types.
Bugfix RT53937
Dependent pages were previously not dirted when a tag type was overwritten by an import. The new behaviour is to dirt all dependent
pages whenever a tag type is changed.
Bugfix RT53746
Links tags will have their anchor text cleaned before saving. This will ensure
that wai-lang attributes will be cleaned up from GCN magic link tag anchor text
before they are saved.
Gentics Content.Node 5.13.1
Enhancement
Added guide about migrating from Live Editor to Aloha Editor
Bugfix RT54935
Tag-fill: Fixed the object name not being displayed (eg.: pages, ...) in a tag URL-part under certain (rare) circumstances when using multichannelling.
This only happened when the page was created in a channel and was localized again in a subchannel of this channel.
Bugfix RT54771
GCN Rest API: Fixed /folder/getImages/ method returning images as type “file”.
This also broke displaying the image width & height in the repository Browser thumbnail preview.
Bugfix RT53175
When a local page inside a channel was translated and the language version did not exist yet,
a new page in the target language was created in the master node. This was not intended and
caused incorrect behaviour, and has been fixed now: the translation of a local page is now
local as well.
Bugfix
Fix the inability to set the startpage for new created folders over the page context menu.
Setting the startpage could duplicate the object tags of the folder, which could also lead to subsequent errors.
Bugfix RT54911
Pages were previously not dirted when only a template tag inside their template was changed,
but the template itself was unchanged. Now, a change in a tag or its values also properly triggers dirting.
Bugfix RT54078
Fix possible (but rare) NPE while finishing a multithreaded publish process.
Bugfix RT54954
Instant publishing: Fixed error messages being shown for none-critical problems like Velocity rendering errors.
Also fixed a Javascript error when the message included linebreaks.
Bugfix RT54620
When using instant publishing for a content repository, the (regular) publish process used to create a new connection for every published object.
This has been changed now, so that the publish process will open a single connection for every content repository, that is kept open while publishing, and only open a new transaction for every object, if instant publishing is used.
Bugfix RT54882
Previously it was not possible to create two pages with the same name in different channels of the same master node.
The same problem also appeared when creating two folders with the same name in different channels of the same master node.
Now, you can create pages or folders with the same name in different channels, as long as one channel is not a master of the other.
Bugfix RT54493
Corrected a previous fix for a NullPointerException in the publish process due to a synchronization problem.
Bugfix RT54509
Improved permission checks for error log, workflow administration and inbox messages.
Bugfix RM9990
Fixes an error that occurred during template migration when linking the target template with the folders linked with the source template.
Gentics Content.Node 5.13.0
Manual Change
A potential security issue has been fixed.
Important: If you are using Gentics Portal.Node Java with the GCNAuthenticationManager (e.g. for frontend editing), you have to update it first, before updating Gentics Content.Node.
If you pass the session secret in the ?do=100 URL now, you will be redirected to the same URL without the session secret in the sid= parameter.
If your system setup is relying on this information in the URL (which it shouldn‘t) in any way, please enable the following feature in your GCN configuration:
$FEATURE[‘disable_sessionsecretredirect‘] = true;
This will keep the old behavior like in the previous GCN versions.
However, we don‘t recommend enabling this, use it at your own risk!
Manual Change
This release of Gentics Content.Node contains all bugfixes from 5.12.12 and below.
This release of Gentics Content.Node contains all bugfixes from 5.12.12 and below.
Enhancement RM2239
The internal dirting mechanism has been changed. The new mechanism offers the following advantages:
- It is now possible to dirt inherited objects for specific channels only. The old mechanism could only dirt the objects as a whole, so that the object would be re published for channels, which inherit it.
- It is now possible to dirt online pages, even if they are currently edited (have status 0).
- Dirting of objects of all types (pages, images, files, olders) now works the same way.
- During the publish run, it is no longer necessary to access the (ever growing) logcmd table, which improves the performance.
- The new mechanism is less prone to problems with changes that happen during a publish run.
After the update, the system will have one additional maintenance task scheduled (that will be performed before the next publish run). This maintenance task will migrate the currently dirted objects to the new mechanism.
Additionally, the maintenance dialog has been improved:
- It will now also show the number of currently dirted files and folders (per node/channel).
- It will show the number of currently dirted objects also per channel and it is possible to use any of the maintenance tools for objects of a channel.
- The controls have been slightly improved to show more compact information.
See Content Maintenance for more information about the maintenance tools.
Enhancement RM8177
It is now possible to create multichanneling Content.Repositories.
See Multichannelling aware content repository for more information about this feature and on information about configuration and further settings.
Enhancement RT54240
We no longer load all constructs that are available across en entire system when
editing a page with Aloha Editor becuase this can result in large payloads that
slow down page load times. We now only load constructs that are either in the
same node as the page being edited, or are used by tags in that page.
Enhancement
The list of nodes in the backend will now show with icons, which nodes have publishing disabled, which nodes will be published into the filesystem and which nodes will be published into a content repository.
Enhancement RM6440
Added support for configurable RequestDecorators to intercept and modify requests to the GenticsImageStore.
Enhancement
Improved documentation by adding a list of discontinued features.
Enhancement
GCN JS API‘s pubsub message channels and guides have been improved.
Although still available for backwards compatibility, the following channels
are deprecated with this change:
- content-inserted
- content-rendered
- authentication-required
- authenticated
- session-set
The following message are new:
- session.authentication-required
- session.authenticated
- session.sid-set
- tag.inserted
- tag.rendered
- tag.rendered-for-editing
- tag.before-deleted
- page.before-saved
- page.before-published
- folder.before-saved
Enhancement RT53533
The new optional feature “move_perm_with_edit“ will modify the necessary permission for moving pages, images and files.
If the feature is off, users will need to have the “delete“ permission in the source folder, which is the same behavior as before this enhancement.
If the feature is on, users will need to have the “edit“ permission in the source folder for moving objects to other folders.
In all cases, users will need to have the “create” permission in the target folder.
Enhancement
The minified version of the Gentics Content.Node Javascript API will now be used within Gentics Content.Node. Previously only a concatenated version was used.
Enhancement
The template and tagtype migration feature was added to Gentics Content.Node. This feature allow the node administrator to migrate pages using a predefined mapping. More information about the feature can be found within the guides.
Bugfix
The internal storage of objects, that can be localized (using multichannelling) has been modified.
Before this fix, objects (pages, folders, templates, files and images) were initially created with channelset_id = 0. When the objects were localized, a new channelset_id was assigned.
This caused some additional overhead in handling channelset_ids and could cause some problems. Therefore, when objects are created, they will immediately get a non-zero channelset_id.
Also this update will change all existing objects to have a non-zero channelset_id.