Start page / WebClient 5.0 / Restrictions

Restrictions in the WebClient

At the present time (11-2012), the following restrictions must be noted in the WebClient mode:

General

"New Window" projects: When new windows are opened, there is no WebClient bar there.
WebClient preview: It is possible that the preview is not up-to-date, for example, if changes are made to the templates. In this case, a current preview can be requested manually.
Releases: The WebClient 5.0 will not support projects that do not use releases (so-called “auto release projects”, server and project configuration application, "Options", deactivated option "Use Release function").
Default values: WebClient 5.0 supports working with Default values only to a very limited extent.
A (not persistently stored) default value can be provided for an input component in FirstSpirit JavaClient in the form area of a template. This default values are displayed to the JavaClient editor when opening the form, the respective input component is highlighted in color. The editor can decide if he wants to take over the default value (the default value will be stored persistently), if he wants to overwrite it by another value or if he wants to keep the default value (the default value is not persistent).
Note: When opening a form with default values for the first time in WebClient these (not persistently stored) default values are displayed initially. When saving the form the default values will then be stored persistently. WebClient does not provide any option to reset stored values within an input component to the default value or to prevent the storing previously.
Tree view: Content can not be displayed in a tree view like in the FirstSpirit JavaClient. This leads amongst others in the fact that no objects can be moved, for example media from one folder to another (except for: page references and menu levels in the Site Store) and that no folders can be created, deleted or renamed (except for: folders in the Site Store / menu levels).
No reference names can be assigned, but they are created and assigned automatically by the system.
For creating sections on empty pages a project-specific solution is required, for example the use of an appropriate icon (FS_BUTTON).
Due to varying implementations, current web browsers may have functional differences in some aspects and provide different feature sets. Generally, FirstSpirit WebClient can be used in all supported web browsers. However, certain advanced functionality or functional alternatives may not be available in all browsers. For example, drag and drop of files from external sources into the WebClient is currently not available in Microsoft Internet Explorer.
In addition, the following functions which are provided by the JavaClient are not available in the WebClient:
- Importing MS Word documents
- Project homepage
The following are not planned for the WebClient:
- Changes in the Template Store (i.e. all types of templates, workflows and schemata CANNOT be edited via the WebClient.)
- Support for variables in the Site Store.
- Resolutions in the Media Store.
- Support for permission assignment.
- Support for document groups (reading access is possible)

Stores

Objects of the following stores cannot be edited but they are displayed and can be selected by input components (e. g. FS_REFERENCE) in the WebClient:

Template Store (including page, section, format and link templates, scripts, database schemes and workflows)

The following objects are not displayed in the WebClient:

Project and User settings (Global settings)

Store	Restrictions
Page Store	Sections basing on table templates ("Content projection") can not be created via WebClient. They must be created in JavaClient.
Content Store	No content sources can be created. This means that a content source must have been already created by means of the JavaClient to be able to select data sets from this content source.
	Content sources are not displayed in table form.
	"Advanced Search" is not available.
	Saved queries are not supported.
	Content sources are displayed with filtering and searches are executed on the filtered content source, but this is not a guaranteed product feature of FirstSpirit.
Media Store	Only language-independent media can be uploaded and edited.
Site Store	There is no access to structure variables, i.e. structure variables can not be set, modified or deleted in the WebClient.

Input components

The following input components are not supported by the WebClient:

Input component	Alternative
CMS_INPUT_CONTENTAREALIST	FS_LIST (Type INLINE)
CMS_INPUT_CONTENTLIST	FS_LIST (Type DATABASE)
CMS_INPUT_FILE	FS_REFERENCE
CMS_INPUT_IMAGEMAP	--
CMS_INPUT_LINKLIST	FS_LIST (Type INLINE)
CMS_INPUT_OBJECTCHOOSER	FS_DATASET
CMS_INPUT_PAGEREF	FS_REFERENCE
CMS_INPUT_PICTURE	FS_REFERENCE
CMS_INPUT_SECTIONLIST	FS_LIST (Type PAGE)
CMS_INPUT_TABLIST	FS_LIST (Type DATABASE)

Restrictions / differences:

Input component	Restrictions
CMS_INPUT_DATE	Manual entries are not possible (parameter allowInput)
	The formatting symbols w, W, D and F (parameter format) are not supported by the WebClient. Linguistic values (z, M, E) conform with the language of the client which is selected via the FirstSpirit start page.
CMS_INPUT_DOM	Only generic link editors are supported, but no "static" or custom link editors.
CMS_INPUT_DOM	No length restriction (parameter maxCharacters).
CMS_INPUT_DOMTABLE	No support for cell formatting (format templates are possible, however, no cell-specific attributes).
FS_DATASET	Data records can not be deleted via this input component (parameter allowDelete), only the reference to a data record can be removed.
FS_LIST	FS_LIST in the WebClient does not provide all functions as in the JavaClient, for example concerning the layout and embedded forms can not be displayed.
FS_REFERENCE	The parameter imagePreview does not have any effects in the WebClient. A thumbnail of the selected image will be displayed in any case. Unlike in JavaClient, new pages can be created in FS_REFERENCE in WebClient, depending on the configuration.

Print version | Page start