Selecting your UI

Ara
Experience Manager 6.2 Sites İçerik Oluşturma Kullanıcı Kılavuzu
Şunun için geçerlidir: Experience Manager 6.2 Sites

某些 Creative Cloud 应用程序、服务和功能在中国不可用。

Şu sürüme ilişkin yardım içeriğini görüntülüyorsunuz:

There are various locations where you can define which UI is to be used:

Not:

Instances upgraded from a previous version will retain the classic UI for page authoring.

After upgrade, page authoring will not be automatically switched to the touch-optimized UI, but you can configure this using the the OSGi configuration of the WCM Authoring UI Mode Service (AuthoringUIMode service). See UI Overrides for the Editor.

Configuring the Default UI for Your Instance

A system administrator can configure the UI that is seen at startup and login by using Root Mapping.

This can be overridden by user defaults or session settings.

Setting the Default Authoring UI for Your Account

When using the touch-optimized UI each user can access their user preferences to define the Authoring Mode (default UI) they want to use when editing a page:

  • Touch-optimized (Default)
  • Classic

This can be overridden by session settings.

Switching to Classic UI for the Current Session

When using the touch-optimized UI desktop users might want to revert to the classic (desktop only) UI. There are several methods to switch to the classic UI for the current session:

  • Navigation Links

    When appropriate, icons in the global navigation of the touch-optimized UI provide access to the classic UI.

    When you use mouseover for the appropriate console, an icon appears (symbol of a monitor), tapping/clicking this will open the appropriate location in the classic UI.

    For examples, the links from Sites to siteadmin:

    chlImage_1

  • URL

    The classic UI can be accessed using the URL for the welcome screen at welcome.html; for example:

    http://localhost:4502/welcome.html

    Not:

    The touch-optimized UI can be accessed via sites.html; for example:

        http://localhost:4502/sites.html

Switching to Classic UI when Editing a Page

When editing a page using the touch-optimized UI desktop users can Open the Classic UI from the Page Information dialog:

chlImage_1

UI Overrides for the Editor

The settings defined by a user or system administrator can be overriden by the system in the case of page authoring.

  • When authoring pages:
    • Use of the classic editor is forced when accessing the page using cf# in the URL. For example:
      http://localhost:4502/cf#/content/geometrixx/en/products/triangle.html
    • Use of the touch-optimized editor is forced when using /editor.html in the URL or when using a touch device. For example:
      http://localhost:4502/editor.html/content/geometrixx/en/products/triangle.html
  • Any forcing is temporary and only valid for the browser session
    • A cookie set will be set dependent on whether touch-optimized (editor.html) or classic (cf#) is used.
  • When opening pages through siteadmin, checks will be made for the existence of:
    • The cookie.
    • A user preference.
    • If neither exist, it will default to the definitions set in the OSGi configuration of the WCM Authoring UI Mode Service (AuthoringUIMode service).

Not:

If a user has already defined a preference for page authoring, that will not be overridden by changing the OSGi property.

Dikkat:

Due to the use of cookies, as above, it is not recommended to either:

  • Manually edit the URL; a non-standard URL could result in an unknown situation and lack of functionality.
  • Have both editors open at the same time; for example, in separate windows.