Path

ez.no / documentation / ez publish / user manual / 4.6 / the administration interface


Caution: This documentation is for eZ Publish legacy, from version 3.x to 5.x.
For 5.x documentation covering Platform see eZ Documentation Center, for difference between legacy and Platform see 5.x Architecture overview.

The administration interface

The purpose of this chapter is to present a walk-through of the most commonly used parts of the administration interface that comes with eZ Publish. Please note that the administration interface consists of many parts. This chapter does not cover advanced topics, instead it focuses on the parts that are most likely to be used by people who simply want to manage content.

Introduction

eZ Publish comes with a web based administration interface that makes the everyday tasks of site and content management an easy matter. The interface can be reached and used regardless of location and/or operating environment as long the following requirements are fulfilled:

  •  The client must be able to reach the eZ Publish server through a network
  •  The client must be equipped with a modern/supported web browser

The administration interface is implemented using the XHTML 1.0 Transitional standard combined with Cascading Stylesheets. In addition, JavaScript (a technology that goes beyond the limitations of (X)HTML) is used in order to create a more friendly environment. However, support for JavaScript on the client side is not required. If JavaScript is unavailable, the administration interface will automatically fallback to static HTML pages with alternate solutions and thus it will function correctly in non-JavaScript browsers.

Supported browsers

eZ Publish is developed to work properly and support the following browser configurations:

  • Firefox 7+
  • Internet Explorer 8 & 9
  • Google Chrome 9+
  • Safari 4.0.+ on Mac OSX 10.5

Please note that the interface should work in any browser that is capable of rendering XHTML 1.0 Transitional and supports CSS. If CSS is not supported, the system will appear without design/layout but will still be accessible through standard/default HTML elements. Also note that issues with browsers caused by to restrictive or experimental settings enabled, typically affecting javascript based parts, will not be viewed as product issues.

Balazs Halasy (07/05/2010 8:53 am)

André R. (02/02/2015 2:15 pm)

Geir Arne Waaler, Ricardo Correia, André R.


Comments

There are no comments.