Restrictions in WebEdit
At the present time (07-2010), the following restrictions must be noted in WebEdit mode:
General
- "New Window" projects: When new windows are opened, there is no WebEdit bar there.
- WebEdit 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.
- Despite extensive optimisations within the scope of implementation of WebEdit, very large projects and/or slow network connections sometimes result in substantial delays (see below).
- Tree view: The "Locked" state is not displayed in the tree view of the stores. On the other hand, the coloured marking for the status of a workflow on an object is shown.
- Support is not implemented for move operations within the tree. However, it is possible to change the order of the sections below a page (or the order of the menu levels in the Site Store).
- The following functions for increasing the usability of FirstSpirit JavaClient are not available in WebClient (see also FirstSpirit Release Notes 4.2):
- Multi-Tabbing (horizontal tabs for convenient editing of several workspaces)
- Breadcrumb navigation (display of the path from the Store root up to the current element above the form area)
- Individual display of the stores (tree view reduced to one Store)
- Integrated (inline) preview
- Content highlighting
- Restore settings on restart
- For remote projects the following restrictions apply:
- The definition of more than one remote project (<REMOTE...>) and the definition of categories (<CATEGORY...>) is supported for WebEdit only for the input components CMS_INPUT_FILE and CMS_INPUT_PICTURE.
- If more than one remote project is configured for an input component each with the parameter uploadFolder only the first uploadFolder is taken into account in WebEdit. Further uploadFolder of other remote projects are ignored in WebEdit.
- In addition, the following functions which were implemented as new functions in Version 4.2 of FirstSpirit JavaClient, are not available in WebEdit:
- Multi-lingualism of content areas: Instead of the language-dependent display names which are displayed in JavaClient, the reference name is displayed in WebClient.
- Media galleries
- Importing MS Word documents
- Drag & Drop FirstSpirit objects (e.g. from the local file system into the JavaClient and vice versa, between two workspaces, from the search dialog)
- Status display for objects
- Quick text search
- Project homepage
- New start dialog
- The following are not planned for WebEdit:
- Changes in the Template Store (i.e. all types of templates, workflows and schemata CANNOT be edited via WebEdit.)
- Support for variables in the Site Store.
- Resolutions in the Media Store.
- Support for permission assignment.
- Support for document groups.
- CMS_INPUT_DOMTABLE: No joining (merging) and splitting of cells.
Stores
The following stores are not displayed in WebEdit:
- Template Store (including page, section, format and link templates, scripts, database schemes and workflows)
- Global settings (including Global content area, Project and User settings)
Elements of these stores can not be edited in WebEdit or selected by input components (e. g. FS_REFERENCE).
Store | Restrictions |
---|---|
Content Store | "Advanced Search" and full text search are not available. |
Tables can not be sorted by a click on the column heading and the number of displayed data sets can only be limited by the search function. | |
Saved queries can only have parameters of the type "String". (Boolean, integer, double and date types are also supported in JavaClient.) | |
Multi-line display of data sets is not supported. | |
Up to FirstSpirit version 4.2.442 filterings on data sources are ignored in WebEdit, i.e. data source which are filtered in the JavaClient by means of the context menu entry "Set filter", are displayed without any filtering in WebEdit. | |
Media Store | From FirstSpirit Version 4.1, uploading media into the Media Store of FirstSpirit JavaClient and FirstSpirit WebClient can be limited to specific file sizes and formats (Media Restrictions). As the file selection dialog available in the browser for uploading media is not an independent implementation of FirstSpirit, but instead is permanently integrated in each browser (e.g. Firefox, Mozilla, Internet Explorer, Opera), filtering (as in JavaClient) is technically not possible in WebClient. The files are therefore not filtered until after the upload and any error message on exceeding the media restrictions define din the project configuration is issued to the user. |
Site Store | No complete support for page groups. All page references created using the Quick Edit bar are located in the "Default" page group. |
There is no access to structure variables, i.e. structure variables can not be set, modified or deleted in WebEdit. | |
Input components
The following input components are not supported by WebEdit:
- CMS_INPUT_CONTENTLIST
- CMS_INPUT_IMAGEMAP
- CMS_INPUT_TABLIST
- FS_BUTTON
Input component | Restrictions |
---|---|
General information | Default selection for input components is supported in individual cases only. |
CMS_INPUT_COMBOBOX | Individual values can not be entered into the input component (parameter editable="YES" ). |
CMS_INPUT_CONTENTAREALIST | If
are used, it should be paid attention that sections in the input component can not be edited directly but that only the input component itself can be edited.
|
CMS_INPUT_DOM | No support for links to custom link editors. |
Limited support for lists, nesting within a list is not possible. | |
No length restriction (parameter maxCharacters ). | |
Limited support for so-called inline tables (table parameter): It is not possible to edit cell properties (see also FirstSpirit Release Notes 4.2 and FirstSpirit Manual for Developers (basics)). | |
CMS_INPUT_DOMTABLE | No support for cell formatting (format templates are possible, however, no cell-specific attributes). |
CMS_INPUT_OBJECTCHOOSER | Unlike in the JavaClient, for using the ObjectChoosers in WebEdit a data source, basing on the table template which is defined by the table parameter, must exist in the Content Store. |
The option of switching to the Content Store with the click of a button in order to edit the selected data set ("Jump to...") is not available in WebEdit. | |
Further uses of a referenced data set cannot be displayed in WebClient. | |
The structure of the component and the logic of the buttons for saving and editing input differ in WebEdit: In order to accept the changed content in the referenced data set, the data set change must be explicitly saved in the WebEdit input component. Simply saving the change using the form ("Save changes and close dialog") as in FirstSpirit JavaClient is not sufficient in WebEdit. | |
Nested use of the CMS_INPUT_OBJECTCHOOSER and FS_DATASET input components is not supported in WebEdit. This means "Object Chooser-in-Object Chooser", "Dataset-in-Object Chooser", "Object chooser-in-Dataset" and "Dataset-in-Dataset" cannot be used. | |
CMS_INPUT_TEXTAREA | The length restriction has no effect. |
FS_DATASET | Hierarchical structures of the Content Store cannot be displayed in WebEdit, if the selection options have been limited using the |
Nested use of the CMS_INPUT_OBJECTCHOOSER and FS_DATASET input components is not supported in WebEdit. This means "Object Chooser-in-Object Chooser", "Dataset-in-Object Chooser", "Object chooser-in-Dataset" and "Dataset-in-Dataset" cannot be used. | |
FS_LIST | The functional scope of the FS_LIST input component corresponds to the CMS_INPUT_CONTENTAREALIST input component in WebEdit (see also restrictions above), i.e. type INLINE with source="sectiontemplates". Additional functions can be obtained when activating the so-called "Applet mode". |
FS_REFERENCE | Unlike in the JavaClient the selection dialogue in WebEdit only has one column for navigating through a project. For this reason, if using the tag HIDE please take into account that folders must not be hidden in stores from which the editor should select references if you want to enable navigation throughout this store. Furthermore, using <HIDE type="all"> is mostly unsuitably in projects with several folder levels. |
A selection option exists in WebEdit for the following Stores only: Page Store, Media Store, Content Store and Site Store. | |
Only data sources can be selected from the Content Store. | |
No document groups can be selected, because the document group function is not supported in WebEdit. | |
Uploading new objects is not supported in WebEdit. | |