OpenWGA 7.0 - Updating to OpenWGA 7.0
Updating from OpenWGA 6.0 » To consider before updating » Changed behaviourBehaviour changes in OpenWGA Content Manager
In OpenWGA Content Manager 7.0 we have changed some behaviours to improve consistency and make the interface more intuitive and usable.
Page Properties moved to separate dialog
The page properties for each page (unique name, position, edit and read permissions) were served for editing on the content properties tab (Menu "Edit > Properties...") up until OpenWGA 6.0, shown there in a separate section.
However this was problematic as these properties have a different scope than those of the content document. They are effective for the whole page immediately while the content properties are stored on the current draft copy and will not get effective until the draft is released. This is also why the page properties are always editable while the content properties are readonly on non-draft documents.
To better illustrate this difference we removed the page properties from the content properties tab. Instead there is now a button on the explorer panel which opens a separate page properties dialog:
The dialog looks like this: It has the same settings that it had before:
Changed Drag&Drop behaviour for files and images
In OpenWGA 6.1 we streamlined the behaviour to drag&drop file attachments from the content management panel into Richtext fields. The type of element created - link or embedded image - is now mainly dependent on the list control you drag it from:
- When you drag it from the file list of the attachments section you always create a link:
- When you drag it from the images list of the attachments section you normally create an embedded image:
- You can also create a link from the image list when you hold the shift key while dropping. So holding the shift key while dropping will always create a link, no matter what source list you have.
ACL level "editor" no longer allowed to specify unique names in Content Manager
In order to better prevent technically dangerous operations on lower access levels we removed the ability to specify unique names on pages or individual contents from access level "editor". Unique names have often integral meaning for a websites functionality, as they denote special pages that need to be referenced by that name. Changing such a name may break important functionality and should not be available on that level. Instead it is now reserved for ACL level "manager".
Users of ACL level "manager" start working with level "chief editor" in Content Manager
A user of access level "manager" that logs in to OpenWGA Content Manager will start his session in the lower level "chief editor". This level should be preferred when doing normal work, because it provides better guidance about normal operations and prevents dangerous operations.
To actually use his manager level the user can switch the access level to use. For this he should click in Content Manager on his user name on the top right:
In the appearing dialog there is a select box showing his currently active level:
On this checkbox he can switch to "manager". This will close the dialog and reload the complete Content Manager UI with him being "manager":
The user now has all access rights that are connected to this level.
As you could see in the dialog the user also had the choice of using a lower access level of "editor" or "author". In fact all users in OpenWGA 6.2 have the ability to freely choose a lower access level than they actually own, for example to view a the site in Content Manager from a perspective of a user with lower access.