Known Bugs

  • After the channel field of a draft version has been set, an empty value can no longer ba assigned to it. (Id: 11030)

  • The error "Lost connection to MySQL server during query" may occur while the CM to which a MySQL database is connected generates a dump. (Id: 11088)

  • If the path of a portlet web applikation is contained in the path of another one, (as with /default/PM-PL and /default/PM-PL-Copy, for example), the portlets of both web applications are no longer displayed. (Id: 10531)

  • The NPSOBJ instruction insertvalue="meta" converts special HTML characters twice. (Id: 10675)

  • If, in version 6.6.0PP1, the GUI is operated with Java 1.4, opening an offline help page causes an error. (Id: 11018)

  • Searching for files using obj where condition {objClasses is objType} does not yield mirror files to whose original file the specified file format has been assigned. (Id: 10553)

  • In version 6.5.x the Microsoft HTML editor and the internal editor cannot be opened from within wizards. (Id: 10704)

  • If a CMS file which opens another file in an iframe is displayed in the preview, the file opened in the iframe shows up in the history as well. (Id: 10758)

  • Searching for files using the GUI but without having integrated the Search Server causes the data of all search results to be fetched. With a large number of hits, this might take a correspondingly long time and use up large amounts of memory. Running such an extensive search several times in parallel will significantly reduce the performance of the system. This problem is not version-specific. (Id: 11197)

  • Under Windows, if CMS Fiona 6.5.1, 6.6.0, or 6.6.1 is run with an Oracle database, a memory access error might occur when the Content Manager (CM) is started. Please contact our Customer Support prior to using an Oracle database under Windows. (Id: 11207)

Bugs Found After the Release

  • When editing content by means of a local application, clicking the Save button In the applet that opened the application causes the temporary file (that contains the content) to be deleted. If the user then again clicks Save or OK, an error message is displayed, stating that the corresponding file does not exist. As a workaround, the user should save the content in the local application prior to using the Save or OK button of the applet.. (Id: 11233)

  • When importing a file into the CMS using Internet Explorer 6 or 7, or Firefox, the CMS uses the path of the imported file as the name of the file created in the CMS (special characters are converted, as usual, to underscore characters). For example, the file with the path C:\Temp\Test.css is named C__Temp_Test. The CMS also uses the path as the title of the new file in the CMS. (Id: 11165)

  • On Microsoft Windows clients, a dot in a folder name causes the CMS to not import a file because the file name extension is determined incorrectly. For example, if you import a file that has the path C:\Temp\firstname.lastname\Image.jpg, the import fails and an error message is displayed, stating that lastname\Image.jpg is no valid file name extension. (Id: 11165)

  • If a CMS content (a blob) contains characters that lead to an ill-formed XML document with respect to the UTF-8 representation of the characters, the Template Engine (TE) may fail to parse the corresponding update record. This causes the incremental export of the corresponding CMS file to be aborted. For the same reason, the Content Manager (CM) may terminate a restore procedure. (Id: 11164)

  • After a file format has been renamed using renameObjClass, its field groups, field presets and obligatory fields are lost. (Id: 11179)