| |
FatWire documentation |
|
| |
Mar 28, 2007 |
Copyright © 2002-2007 FatWire Corporation All rights reserved. |
Welcome to the release notes for Content Server V7.0. For the latest release notes, check the FatWire e-docs web site. The release notes contain descriptions of new features, changes in functionality, known problems, and other last-minute information about Content Server 7.0.
For additional information, contact FatWire technical support.
Document history:
The Content Server product CD includes a zip file (named DOC700.zip or DOC700.tar) of all the CS 7.0 documentation, including the installation guides. Unzip this file and begin reading the installation guide appropriate for your configuration. These guides explain how to install Content Server and the underlying DBMS, application server, portal server (optional), and JDBC driver.
The CS 7.0 document set provides documentation for different kinds of users. Updates to product documentation, as they are made, are posted to the following URL: http://e-docs.fatwire.com/CSEE/7.0.0. For a description of the documents please refer to the Documentation Notes link on the site. Check the site regularly for the latest set.
|
CS7 includes three different interfaces for creating and managing your content. Each interface is developed to support a different type of user. The Advanced interface provides the functions, power, and flexibility that administrators and technical users expect. The Dash interface provides a simplified interface designed to let business users quickly accomplish their regular tasks. Dash incorporates new CS7 features such as full-text search across all your content, tagging, and multi-lingual support. The InSite interface provides an intuitive way for designers and marketers to interact with the content management system. With InSite, content can be created, managed, and repositioned in-context, that is, directly from a web page. Furthermore, InSite's Page Builder allows users to design and build web pages quickly by dragging and dropping content: No direct knowledge of the content management system is required.
The benefits of CS7's three interfaces include
- An effective mapping between the power of CS7.and the diverse needs of your content management team.
- Reduced learning curves and increased productivity.
- Reduction of costly IT and resource constraints, empowering all types of users to put content to work
.
Dash interface - CS7's new Dash interface provides the cutting-edge experience that your business users expect. Build upon Java Server Faces' stable foundation, Dash provides quick, intuitive access to the tools for creating and managing content. Its design is user-friendly, making easy things easy, simplifying tasks, and facilitating access to information. Full-text search is provided, letting users search for content in the way they're comfortable. Plus, Dash incorporates Web 2.0 features, such as tagging, to let your business users work with content in a way that best matches their needs. Combined with the abilities to customize the interface, Dash provides the complete business user solution. Screen panels can be resized, shown or hidden according to user preferences. Users can now Create, compare, and translate content for different locales and languages. And a good WYSIWYG text editor simplifies formatting within text fields
CS7's Advanced interface gives sophisticated users, administrators, and seasoned Content Server professionals access to all the power and flexibility that CS7 provides. Create and manage content, data models, and publishing templates. Design workflows. Create business rules, marketing campaigns, and content recommendations to dynamically deliver personalized content. This interface gives power users the tools they need to get content under control and then put it to work.
InSite is CS7's unified framework for both working with content and designing web pages through an easy-to-use visual interface. The Insite Editor lets users create, edit, and arrange content in-context, that is, directly from the web page. No training in a content management system is required. The user simply navigates to a web page and then clicks on the content to edit. Any changes made are immediately viewable and can be put through traditional workflows.
The Insite Page Builder lets designers quickly build a web page. After searching for content, the designer simply drags and drops it into a slot on a structured canvas. In this way, content can be easily added and rearranged. Again, no formal knowledge of a content management is required, simply your existing content and a smart sense of design.
CS7 Dash interface now supports full-text search all your content in the CS7 repository. The immediate result is faster access to your content. No longer will you have to remember the location of content in a complex hierarchy, what web page it's on, or some obscure database name. Content can be fully searched using familiar keywords and metadata. The included search engine is available out of the box and pluggable, giving you the control to change search engines as your business needs change.
The benefits of CS7's full-text search include
- Faster access to your content
- Pluggable, out-of-the-box search engine
- Full-text search across all content in the CS7 repository (including uploaded documents)
- Ability to query content using familiar keywords and metadata.
Multi-Lingual Assets (MLA)LA
Today's global businesses require their content in multiple languages. FatWire's Content Server 7 has multi-lingual support built directly into the data model: As a result, any content—article, press release, catalog entry—can be translated into multiple languages, including double-byte languages such as Chinese or Korean. Furthermore, you can translate content directly in CS7 using a convenient language-to-language comparison display or export it to a third-party translation service. Language versions of the same content can go through workflow independently, when publishing needs are unique, or together, when they need to be published at the same time.
The benefits of CS7's multi-lingual support include
- Multi-lingual capabilities built into the data model
- Language-to Language comparisons directly from the interface
- Translation into double-byte languages (such as Chinese)
- Exporting for translation by a third-party provider
- Workflow of language versions as a group or independently
Content Server 7 also introduces a new Asset API that defines primary interfaces for:
- Session objects
- AssetDataManager: A manager for reading asset data.
- AssetTypeDefManager: A manager for reading asset type’s definition (structure of an asset type).
- AssetData: Asset’s data, basically a collection of AttributeData instances and some more information about the asset itself.
Dash UI is not supported on portal server installs of CS.
Verity search engine is not supported.
|
See the SPD on FatWire e-docs web site for the list of J2EE components (web servers, application servers, DBMSs, JDBC drivers, and so on) that CS 7.0 supports. You should also check with FatWire Support to see if there are any known issues with the configuration you wish to use.
Also, refer to the vendor release notes for all J2EE components to find the latest e-fixes, patches, and service packs required to run your component.
Content Server 7.0 works in application servers running J2SDK/J2RE 1.5 and above. Please make sure that appropriate version of JRE in installed and configured before installing Content Server.
Please also make sure that older versions of the JDK or JRE are not present in the PATH or CLASSPATH environment variables, especially if you plan to run Content Server in an environment that relies on these entries to be correct (resin, for example).
Another common problem encountered is a type of JSPException with a message like the following: "The major.minor version '48.0' is too recent for this tool to understand". This error is related to the incorrect version of tools.jar in the class path. Make sure tools.jar loaded belongs to the correct JRE by launching JVM with a -verbose option.
Windows install fails if there is a space in the path to CS home directory
In Application/Portal server jvm options, include the settting -Djava.awt.headless=true
Content Server contains a modified version of the Microsoft XML Parser in the MSXML.jar file, which can cause conflicts if another version is in use. If you have Microsoft's version of MSXML.jar installed on your machine and this file is referenced in the CLASSPATH environment variable, you must change the path to the Content Server version; otherwise, Content Server fails when parsing XML.
After installation a restart of the domain is necessary for the Dash UI to work.
If an installation of CS fails then do the following before retrying the installation:
Drop the database tables
Undeploy the .ear/.war file
Delete the CS installation folder
Restart the application/webservers
Running the installer on top of a failed install corrupts SatelliteServer.properties file. The workaround is to manually set the properties correctly or run the installation after cleaning up the failed install.
ft.sync is automatically unset during upgrades. so note down the value before the upgrade
For security reasons, we recommend that you allow only internal access to the following servlets:
Install
HelloCS
CatalogManager
TreeManager
DebugServer
CacheServer
Inventory
For BEA application and portal servers, select the Sun JDK while creating the domains. CS will not work if JRockit JDK is selected.
Increase the value of the maximum number of WebLogic JDBC Connection Pools to at least 100 on both publish source and target machines.
Set cs.jspresponsewrapper=false in futuretense.ini
On IE, the Tools > Internet Options > Settings > Every Visit to the page must be set to true.
To change the character set for Internet Explorer 6.0, click View > Encoding > Unicode (UTF-8).
Notes:
Dash, Advanced and Insite - buttons on the top bar work correctly if they popup in different browser windows. It wont work if the popup is configured to be a tab
Tree applet conflicts if you have both CS 6.3 and 7.0 running on the same machine on the same port, so make sure to avoid such a situation. To resolve Java applet issue
1) Right-click the JVM icon in the system tray.
2) Select 'Open Control Panel'.
3) In the JVM Control Panel...a. Navigate to the General tab.
b. Click the 'Delete Files...' button in the Temporary Internet Files section.
c. Click OK to delete the temporary Java internet files.4) Right-click the JVM icon in the system tray again.
5) Select 'Open Console'.
6) Within the Console, type 'x'. This will clear the classloader cache.
7) Restart your browser.
Within Content Server, Ektron eWebEditPro and RealObjects ship with an evaluation license. At the end of the evaluation period, customers interested in purchasing a license for eWebEditPro/RealObjects should contact their FatWire sales representative.
|
Javascript doesn't work on BEA managed server set up in Production mode. To use the portal defined from Weblogic Administration Tools Portal (the WebUI, not the WorkShop), contact BEA to obtain patch CR 131778. Install the patch.
This is fixed by Sun in JES 2005 Q4 release
|
When the oracle database user has access to multiple schemas, all these schemas are read when CatalogManager tries to find the table structure of tables. This issue was specific to Oracle 8.1. Alloy supports Oracle 9 and 10, and this issue is not observed on those.
|
|
|
|
|
|
|
Workaround is to use the satellite:blob tag and specify the parentid attribute with a value set to "asset-cid:c" where c and cid are replaced with the actual values.
|
|
Error during deserialization of history attribute on an upgrade from 5.5.1 to 6.2 The user to edit all visitor attributes and history attributes that have constraints, and basically respecify the constraints in the UI.
|
|
The known issues in release 7.0 are described in this section and are sorted by feature set.
If an editorial user is added to the UI and that user is not given SiteGod privileges, the user cannot edit Recommendation assets if they are more than static list recommendations. The following error appears on the screen: Error -3 encountered while saving. Error: errno=-3 on call to catalog manager for table 'RuleSetDef'
|
If an editorial user is added to the UI and that user is not given SiteGod privileges, the user cannot edit Recommendation assets if they are more than static list recommendations. The following error appears on the screen: Error -3 encountered while saving. Error: errno=-3 on call to catalog manager for table 'RuleSetDef'
|
|
This includes hard spaces between lines of code and indenting. When there are additional white spaces, the attribute editor does not work properly when a user attempts to add a value for the flex attribute that uses the editor.
|
|
|
If you have enabled revision tracking for an object table, and then you delete the table using CatalogManager, Content Server still thinks that the table is being revision tracked.
Content Server allows the value in the tablename column in the SystemSQL table to be null. However, for result set caching to work properly, this value must be specified.
You cannot log into Content Server if the username you are using to log in has the same "id" value of a different user in the SystemUsers table. For example, DefaultReader has an ID value of 2. If you create a user with the username "2," that user cannot log in.
|
For example, a table is created with a column using the data type specified by the property cc.blob. An image is uploaded to the table. When CatalogMover exports the row, the image is not written out to the export data.
|
When using Oracle, LONG and LONG RAW columns cannot be mirrored. Use a URL column rather than a LONG or LONG RAW.
Microsoft SQL Server 2000 database allows a maximum size of 8000 characters in a varchar type column. Using JDBC, however, it is possible to insert/update data of only 4000 characters or less using prepared statement technique (Content Server users this technique). Attempts to insert/update data larger than that size fail with an error. As a result of this anomaly, Content Server’s insert/updates fail with the following message in the logs “Disallowed implicit conversion from data type ntext to data type varchar”.
It is therefore advised that that the varchar column be created with capacity less than 4000. If size requirement for this column is greater than 4000, please consider using a ‘URL type’ field.
e.g. The maximum length of asset's name is 64 characters in html form (input type="text" maxlength="64"). If I enter 64 ä-letters into the text field, SQLException occurs. That happens because the name field is VARCHAR(64), which is 64 bytes which is incorrect for UTF-8.
|
CS-Direct does not stop users from embedding links inside other embedded links. If this happens, the links may not be resolved on the page that displays the asset (that is, they are broken links).
The Insite.Edit tag should have the ewebeditpro=true attribute removed when displaying an embedded pagelet.
Include Image Marker not appearing on Ektron/RealObject/FCKEditor. Important: The visual marker for Include is not appearing in Ektron/RealObject/FCK Editor, but the include is being added.
|
Setting the MAXLENGTH attribute in the
eWebEditPro does not allow an asset to be saved. This requires a manual edit in an eWebEditPro file. Edit ewep.js and search for "var
editorEstimateContentSize=". Change whole to body e.g.
var
editorEstimateContentSize="whole";
to
var editorEstimateContentSize="body";
|
FSII: preview does not switch to current locale (i.e. previewing Home(fr) leads to Home / en_US) This is because FSII doesn't care about the locale of the incoming asset - if no locale session variable exists, FSII templates will always default to English.
|
When the treeview is toggled off and you click "List All Flex Family Asset Types," the list returned are not all flex assets.
The UI should prohibit this change if there is any multivalue data for the attribute in the system.
If 2 attributes exist with same name but case is different, e.g., Name and name, and one has external editing and storage, we do not do the right thing when creating an asset which has both or either one of the attributes. Existing data is overwritten with incorrect data or data is lost.
When user deleting all the ratings from one asset from CS-Direct UI, CS Direct UI just ignores the command and behaves like nothing happened. However, if the user did delete through other ways, by setting ruleset to null/"" in loaded asset before save or through new UI (we allow people to do that), CS only delete the entry created in AssetType_Extension table and left RuleSetDef and RuleMap untouched. The leaves the asset into a stage that no more ratings could be added anymore. (You would see an unique id violation when trying to set ratings again).
|
When a user views an asset in the InSite Editor, the InSite Editor checks to make sure the asset is not locked and it displays the most recent version. However, it does not lock the asset until the user clicks the pencil icon.
At that point, when it does lock the asset, the InSite Editor should check the version one more time. It does not. Because the asset was not locked, it is possible that another user could have opened, edited, and saved it while the first user was viewing it. This means that the original user could now be working on an out-of-date version of the asset.
If an assignment link is selected from InSite Editor and the link points to an asset that is unsupported for editing by ISE, then ISE will close.
To keep up with the performance, insite content is designed to be cached with other part of the pagelet. The current implementation keeps track of all direct dependencies, including access permission and workflow state, which are all direct related to the asset instance. The workaround is to flush CS and SS cache and the pencil icons will start showing correctly.
When you add a link to an anchor tag in eWebEditPro during in-site editing and save it the link gets prefixed with the current URL.
This behavior is also inconsistent. If user 'logs out' and 'logs in' into Advanced UI, then it working properly. But, in many cases user have to clear the cache and proceed.
Delete is not working properly from 'insite' for multiple valued attribute editors. This is using insite:addvalue tag
If you time out in the Insite Framework, then you are being redirected to the session timeout page. But when you re login, you are getting logged into the Advanced UI rather than into the Insite Franework.
This happens when Document is not enabled for CS-Doclink and in the template dmv="true".
|
|
|
Its recommended not to use muti-byte characters in the following:
· UserNames
· ACLNames
· RoleNames
· Template Names
· AssetType Names and FieldNames
|
When implementing an IList, Content Server requires that column names be returned in length order, especially when one column name is a prefix of another column name (i.e., order and order_id). This can affect performance if the implementing IList class wants to maintain a column order.
ics.CommitBatchedCommands() does not return the correct status or set the errno variable properly in every situation.
Take an xml page that wraps code that streams a document back to the user -- this allows for checking the user creds before the doc is streamed. If we try to call out the a jsp to do the validation the stream fails - it actually spits the bytes into the browser since something IS coming before the header. The jsp the I called was completely on 1 line so it should not have 'preserved' any white space
Message exception sending mail Sending failed; nested exception is: javax.mail.SendFailedException: Invalid Addresses; nested exception is: javax.mail.SendFailedException: 530 Authentication Required The only solution is to roll your own javax.mail client
When using asset:export / asset.export tags on an asset that isn't a page or collection, the output XML doesn't contain info about the unnamed associations.
In flex Asset, getCompleAttribute method always assumes that there is a parent for the passing in asset type + definition, if there is none, a CS.DB exception would be thrown relating to getting "assetid" from ResultSet while the resultset is empty.
|
Basically if you try to access the filter XML followed by HTML or HTML followed by XML the JVM crashes (we are talking about a register dump here). This occurs if there are 2 filters on the same page each with a different type or if 2 filets are used in serial. The Text filter is not affected. This behavour has been seen on Linux (JBOSS) and HPUX (WEBSPHERE).
|
For example, if you have a Content Server event that is scheduled to occur every minute and one of the events took 70 seconds to execute, the next event is ignored.
Changing the value of the cc.contentkey property to something other than the default value causes problems with CS tables that depend on this property. FatWire recommends that you do not change this property.
Mirroring fails to set errno if it fails to write a file to the folder specified by defdir in the SystemInfo table.
If there is a un-recognized rendermode passed, the system will cache the page and not log the dependencies. This will cause the page not being flushed in anyway since there dependencies are not there. The correct behavior should be 1. cache the page and log the dependencies anyway or 2. if the dependencies are not logged, do not cache the page.
This is an isolated case where the client was trying to use an embedded link with an invalid type of "image". However even if the attribute is incorrect and invalid, when saved, it should not leave the attribute empty. It seems that when the attribute is saved, the original data is removed and the attribute is emptied. It then tries to load the attribute with the new data but throws an exception due to the invalid embedded link. Instead of it saving the attribute now as empty, it should retrieve the original data and repopulate it so it doesn't lose the attribute. This can most likely happen to attributes regardless of what the error or exception is.
When xml debug is turned on PreView does not work anymore. Reason is that the xml element is validated against the dtd when xml debug is turned on , but the validation fails. This is the code piece that CS barks about (in ShowPreviewFrames) <if COND="IsVariable.target=true"> <then> <ARGUMENT NAME="target" VALUE="Variables.target"/> </then> </if> Best to check all xml elements against the DTD, at CS build time.
In CS 6.3 we used to allow a construct like this: <PROPERTY NAME="checkbox" DESCRIPTION="checkbox"> <STORAGE TYPE="CHAR" LENGTH= "36"/> <INPUTFORM TYPE="CHECKBOX" SOURCETYPE="STRING" CBDESCRIPTIONS="A, B, C" CBVALUES="0, 1, 2" DEFAULT="" INSTRUCTION="A check box field" HIDDEN="NO"/> </PROPERTY> in an Asset Descriptor File. This would allow users to select or deselect multiple values for a checkbox attribute. The saved attribute will be stored as a comma sparated string in the database. This is the only way we allowed multiple values for an AssetMaker asset attribute. In Alloy we will not allow this behavior thru the new UI. Checkboxes will always show up as RadioButtons for AssetMaker assets.
If the event engine is executing an event, and this event takes a while (let's say 5 mins), then during those 5 minutes not other events will be run. Not even events with other names. In other words, the event engine is single threaded, whereby each event should run in it's own thread (or adopt a worker model)
|
|
Because the publish process does not parse the code in attribute editors, it cannot determine whether an attribute editor uses a query asset. To work around this problem, explicitly publish the query assets that you are using with your attribute editors.
It is recommended that only 1 user runs bulk approval at any given time. If you do need multiple users to run bulk approvals, please schedule accordingly.
When a publish operation fails midway, it does not clean up entries in AssetPublication table on target.
If you don't have all flex family members enabled in your site and you initialize the publish destination, only those enabled members get created on the destination site. This causes all kinds of problems on the destination server. For instance, editing the Start Menu items won't work. Editing assets won't work. Etc.
1. We have one Template called "T" 2. We have two sites called "A" and "B" 3. We have one Page asset per site: P1 is on A and P2 is on B 4. The "T" Template is shared to both sites 5. The "T" Template has two mappings: Homepage for A has a value of Page:P1, and Homepage for B has a value of Page:P2 6. When we attempt to approve the T Template to publish the A site, it requires us to approve BOTH P1 and P2. 7. However, we only want to approve P1 since the B site is not ready to be published 8.
For a site that uses static publishing when you change the template on an asset and save it, and publish, then the asset remains in the publish list with the old template and also shows in the new one. Changing to a 3rd template on the asset and publishing added it to the publish list 3 times (one for each template it had been saved and published with). This is a problem because the template the user want is higher in the list than the other ones, and so the html output is overwritten with one of the template choices the user doesn't want.
With revision tracking turned on, and if you were to publish over an asset that have been checked out on the source machine, it is still marked as locked in the destination until the publish ends. However, if the publish fails, this lock cannot be removed and future publishes of this asset will fail since this asset is locked on the destination machine.
|
The tracker table created by the revision tracking feature for a tracked table is always wider than the source table. This means that you cannot track tables that are close to the maximum row size supported by the database.
The data stored in revision history is correct but links in Inspect screen of the revisions are not pointing to the correct uploaded revision files. The data links are all pointing to the latest uploaded revision file which is is wrong.
|
If you use the Content Server REMOTE_ADDR variable to return the IP address of a site visitor, the value returned contains the IP address of the Satellite Server machine instead of the IP address of the visitor. Workaround is using a cookie to set the remote IP address.
Workaround: Solution set the co-resident SS as the second in the list using ContentServer Explorer
|
|
Any approved assets which are shared when a site is replicated with Site Launcher will need to be re-approved in the source site after site replication.
|
The POST tag works incorrectly when USERNAME, PASSWORD or LOGOUT attributes are passed to it. Login and logout requests are sent to the URL being posted to instead of CatalogManager. One workaround is to perform login before this tag is executed. Alternatively, FormPoster API can be directly used to perform the post operation.
|
Do not use the tag <throwexception> in the code of a template asset. <throwexception> effectively kills execution in CS for itself and any nested or parent CS engine. This breaks template execution and streaming of data to the client. In addition, when a user approves a template for export publish, a <throwexception> terminates the execution of the approval page and the user gets no feedback.
Element logic which expects to be passed an argument may generate an error (-10004) when called during approval for export publish if that argument is not present. The error code is displayed in an information box after approval. The template writer should decide whether the error can be safely ignored, i.e. if the error occurs because the template or element is being called out of context and does not affect the approval dependencies.
Workaround is to restart the cluster members once publish is complete
|
For an installation of Content Server that uses Active Directory for User Management, the jndi user specified should only have read permissions. We do not guarantee what will happen if he has write permission.
The dir:replaceattrs tag, which is part of the CS-Direct application that Content Server uses for user management, does not throw an exception when it is trying to replace the user attribute value of a nonexistent user attribute or for a nonexistent user.
When a user is deleted at the Content Server level through Content Server Management Tools, that user is not deleted from CS-Direct sites.
If a CS Administrator wants to remove a user from the LDAP, he should first remove all the user’s roles in the CS-Direct interface. If this step is not completed, the user can have dangling rows in UserPublication table when LDAP is used to store users (& ACLs) and CS database (UserPublication table) is used to store user roles.
If the updates are made using CS User Admin Screen, they are reflected immediately. However, if ACLs are updated directly in LDAP server, then we recommend that you
1. Restart your portal/Application server for the changes to take effect or
2.
Flush ACL cache using the url
http://localhost:7001/spark/CatalogManager?ftcmd=flushcatalog&tablename=SystemUsers&authusername=admin&authpassword=xceladmin
If a user without any ACL logs in to CS, CS allows user to perform only those operations that a user with Browser ACL can perform.
If a user is enabled for a site and you delete the user from ContentServer Management Tools interface or from SystemUsers in Content Server Explorer, AdvanceSearch UI screen will not render. The workaround is to delete the corresponding user entry from UserPublication table
A call stack is seen in futuretense.txt on Weblogic 81 portal installations (See below). This is a debug message and does not indicate any problem with the LDAP integration.
May 13, 2005 3:30:05 PM][CS.AUTH][INFO] Print Call stack. Delete Role WorkflowAdmin
from database and from ldap. Page name is
OpenMarket/Xcelerate/Installation/AddRole
java.lang.Exception: Inside delete
method of FlatLDAPRoleManager.
at
com.openmarket.xcelerate.roles.FlatLDAPRoleManager.delete(DashoA14174)
at
com.openmarket.xcelerate.roles.RoleManager.save(DashoA14174)
at
com.openmarket.xcelerate.roles.FlatLDAPRoleManager.save(DashoA14174)
at
com.openmarket.xcelerate.commands.RoleManagerDispatcher.Save(DashoA14174)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
com.openmarket.framework.commands.Dispatcher.Execute(DashoA14174)
....
This is an inconsistency between database and LDAP user management. You need DefaultReader in database (SystemUsers) in case of native user management but you don't need this user in any system in case of external/LDAP user management.
|
Login to Dash. Click on Advanced. Close Dash Windows. Click on Dash in Advanced Windows, you get a javascript error
Dash UI - Copy keeps referenced by incorrectly 1). Create a product asset - say A - (this is the master) 2). Create a translation - say B 3). Go back to asset 'A' and click on copy (dont click on save) Observe - In the Relation tab - the Referenced by shows 'B'. (this is because its copying everything from A - which is incorrect) On saving - the referenced by is refreshed correctly
|
The default debug listener port of 1025 for the Page Debugger may have a conflict on Windows 2000. This can be changed to some other port number.
Page debugger fails when trying to debug JSP pages.
|
If you select a workflow for an asset, then go to the Set Participants form, then click the Cancel button, the workflow is set to all participants, as if you had selected the Select All button.
|
|
This means that flex assets that have a required attribute of type asset should not be enabled for CS-Desktop.
In such a case, when a CS-Desktop user opens a flex asset that was created with the original definition, there are no parents marked for the asset. To work around this issue, be sure that you do not enable flex asset types for CS-Desktop until you are completely finished configuring their definitions.
If Outlook is already open, CS-Desktop toolbar will not be displayed when MSWord is opened to connect with ContentServer. This only occurs if MSWord is configured to be the default email editor for Outlook and Outlook has been opened first. Outlook maybe closed and MSWord reopened as a workaround.
Workaround: CS-Desktop is a word Add-in and not just a template. There is a very subtle difference between the two of them. Especially in the way they are loaded and run. The workaround for this bug is to move the CS-Desktop.dot from the word's startup folder out to somewhere safe for example in c:\Program Files\FatWire\. Now when you start Word or Outlook, the Content Server toolbar add-in won't be loaded. If you need to load it, Click on Tools --> Templates and Add-Ins -> Click Add and browse to the CS-Desktop.dot, when you add it and click okay, it will load our CS-Desktop add-in.
During file conversion by CS-Desktop (implemented by Verity KeyView), CS-Desktop writes image files to the folder specified by property keyview.imagedir in futuretense_xcel.ini. There are two requirements for the folder keyview.imagedir:
1. It must be a web-accessible folder that matches the URL prefix specified in keyview.imgurl. This ensures that CS can preview the CS-Desktop images.
2. The folder must exist before CS-Desktop is used. This ensures that the KeyView file conversion completes successfully and saves the images.
Note that after installing CS, keyview.imagedir is set to $SHARE-directory/remoteimages and keyview.imgurl is set to /futuretense_cs/remoteimages/. You may edit these value to point to an appropriate folder, or you may keep these values and create a folder named remoteimages.
When data is saved using CS-Desktop in the form of table content then entire data is not saved hence not previewed.
|
The help file is present in the installed folder but not registered correctly.
|
If your
Content Server system is using the UTF-8 or Shift-JIS character sets, please be
aware of the following problem with exporting tables in the ZIP format from CSE.
File names (such as an element's url file) containing non-English characters
will cause the export to fail. As a workaround you can export those
records
or the table using the CSE format. There is no problem with the content of the
files (any valid UTF-8 or Shift-JIS characters will work), only the file names
are an issue.
Workaround is to make sure that all the catalogs in a project have at least one record
|
To contact FatWire Corporation about technical support for your product:
|
|
|
FatWire documentation |
|
| |
Mar 28, 2007 |
Copyright © 2002-2007 FatWire Corporation All rights reserved. |