LOGIN Infoportal

» Noch nicht registriert?

GENTICS News

» Newsletter bestellen
» RSS-Feed abonnieren

Known Issues (English only)

A list of known issues of specific Content.Node.

Publishing of many nodes into one contentrepository has serious performance issues. Another sideeffect is that the database transactions of publishing (not syncing through crsync!) might fail with OutOfMemory failures.

First appeared in Gentics Content.Node 4.1 20091216c
Fixed in update 20100120

Using context menus of Gentics Content.Node is currently not possible with version 10 of the Opera browser.
As a workaround you can enable context: Ctrl+F12 -> Advanced -> Content -> JavaScript Options -> Allow scripts to detect context menu events.

First appeared in Gentics Content.Node 4.1

Not yet fixed.

Using special characters when naming table-tagtypes causes the formatting options to fail and the assistant to disappear.

As a workaround do not use special characters at the moment.

First appeared in Gentics Content.Node 4.1
Not yet fixed.

When pages, templates or tagtypes are exported while they are locked for editing, the edit lock will be transferred onto the target system by the import, and those edit locks cannot be lifted over the UI.
As a workaround, it would be possible to repeat the export with no objects locked, or perform the following statements in the backend database of the target system:
```
UPDATE content SET locked = 0 WHERE locked_by = 0
```
```
UPDATE template SET locked = 0 WHERE locked_by = 0
```
```
UPDATE construct SET locked = 0 WHERE locked_by = 0
```
First appeared in Gentics Content.Node 4.1
Not yet fixed.

When the hostname or publishing directory of a Node is modified, eventually not all published pages in this Node will be written into the new folder structure in the next publish run (when the Node is published into the filesystem).
As a workaround it is possible to let all pages be republished for the Node (via the maintenance dialogue).

First appeared in Gentics Content.Node 4
Not yet fixed.

Export - depending on the project size might fail due to high memory usage.

In extreme cases memory usage of up to 1MB for each page, folder, image or file might be encountered.

Fixed in Update 2009-02-03

Import and Node copy - depending on the project size these features might fail due to high memory usage.
In extreme cases memory usage of up to 1MB for each page, folder, image or file might be encountered. For more informations on this issue read the reference pages of 'NodeCopy' and 'Import' feature.

You can partially avoid this Problem by changing the value of Xmx (Java memory limit) to 1500m (see » FAQ).

32bit JVM (such as the one delivered with Gentics Content.Node) are only capable of allocating 1.5GB of memory. If this is not enough to fit your needs, and you are using a 64bit operating system, you can work around this problem by creating a symlink /Node/java that points to a 64bit JVM. This allows you to set even higher Xmx values than 1500m.

We are currently working hard on a new version of Node copy and Import that will reduce the memory usage.

Not yet fixed.
If you synchronize the Content Repository to a engine based on » HSQLDB, you have to use the undocumented feature -disableloboptimization for the CRSync or you'll get a message like
```
java.lang.RuntimeException: Error while synchronizing data
at com.gentics.api.portalnode.connector.CRSync.syncCRData(CRSync.java:1406)
at com.gentics.api.portalnode.connector.CRSync.doSync(CRSync.java:834)
at com.gentics.api.portalnode.connector.CRSync.main(CRSync.java:296)
Caused by: java.sql.SQLException: This function is not supported
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
```
Furthermore there is not supported datasource-versioning as HSQL doesn't support subselects. For this reason there are also available limited queryrules.

Further informations about HSQLDB you'll find on » Hsqldb User Guide

Not yet fixed.

The live editor does not support inline editable tags inside of absolute positioned HTML elements. For example the following will not work:
```
<table style="position:absolute; left: 195px; top: 240px; ">
  <tr><td>
      <node text_inlineeditable>
  </td></tr>
</table>
```
In cases where this is needed use a tag which is not inline editable or only output the "position:absolute" if not in edit mode.

Fixed in Update 2008-08-20

The desktop integration (open folder) will not work with Windows Vista without SP1. The WebDAV client integration in Windows Vista without Service Pack 1 » is known to be unstable and non functional. You can resolve this issue by updating to SP1 or using a 3^rd party WebDAV client.

Fixed in Microsoft Windows Vista SP1

Some users have reported problems closing the RealEditor when working with » Firefox 3. We have not yet been able to verify this problem. If you experience this problem, please close the window manually by clicking on the 'X'. Your feedback to track down this issue is welcome.

Fixed in Update 2008-08-12

Using the all-new Firefox 3 you may experience problems when editing a page. While being able to edit the page in live edit mode, the whole page content will be lost on saving. Our versioning system may help restore page contents, if appropriate versions are available. If you are using Gentics Content.Node prior to Update 2008-06-18, we strongly suggest you not to use Firefox 3. When using Gentics Content.Node 4.1 please check the startpage for you current version information, to make sure your system is already updated to 2008-06-18.

Gentics Content.Node 3.6 Users are highly suggested to stick to Firefox 2.

Fixed in Update 2008-06-18

Distributed SSH keys for maintenance are insecure due to a Debian security issue, see » Security Notice for further info.

Fixed in Update 2008-05-28

Depending on your screen resolution the "languages" top menu entry might fill up more space than the standard Gentics Content.Node content viewport provides, thus detaining you from selecting some of the lower language entries. This issue is encountered rarely as using 20+ languages is quite uncommon, and may be workarounded by using the language links from the page list.

First appeared in Gentics Content.Node 4

Since Content.Node is using InnoDB tables some issues with data file size may be encountered, as InnoDB won't shrink the file when rows are deleted. Currently the only way to handle those filesize issues is to dump the whole database, drop it, delete the data file, recreate the database and import the data afterwards. This issue is also documented at http://forums.mysql.com/read.php?35,121880,121886. Altering tables with heavy usage and no transactions to MyISAM is a possible workaround, as well as truncating tables like import_page over night, to keep the data file from growing.

First appeared in Gentics Content.Node 4 Update 2007-07-05

When using IE7 the onBeforePaste Event is triggered when clicking on the "Tools" menu entry. Therefore clipboard contents are pasted into the active area. This issue is known in relation with Internet Explorer 7.0.5730.11. as the onBeforePaste event is used as specified in http://msdn.microsoft.com/workshop/author/dhtml/reference/events/onbeforepaste.asp. The problem can be reproduced using the following code snipplet:
<div contenteditable="true" onbeforepaste="alert('before');">my content here</div>

Not yet fixed.

Downloads & Links

top