Once you set up your environment you can start your work as an administrator. Your most useful tools can be found in Admin Panel.
The System Information panel in the Back Office is sourced in a ibexa/support-tools repository. There you will also find basic system information such as versions of all installed packages.
Sections are used to divide Content items in the tree into groups that are more easily manageable by content editors. Division into Sections allows you, among others, to set permissions for only a part of the tree.
Technically, a Section is a number, a name and an identifier. Content items are placed in Sections by being assigned the Section ID. One item can be in only one Section.
When a new Content item is created, its Section ID is set to the default Section (which is usually Standard). When the item is published it is assigned to the same Section as its parent. Because content must always be in a Section, unassigning happens by choosing a different Section to move it into. If a Content item has multiple Location assignments then it is always the Section ID of the item referenced by the parent of the main Location that will be used. In addition, if the main Location of a Content item with multiple Location assignments is changed then the Section ID of that item will be updated.
When content is moved to a different Location, the item itself and all of its subtree will be assigned to the Section of the new Location. Note that it works only for copy and move; assigning a new Section to a parent Content item does not affect the subtree, meaning that subtree cannot currently be updated this way.
Sections can only be removed if no Content items are assigned to them. Even then, it should be done carefully. When a Section is deleted, it is only its definition itself that will be removed. Other references to the Section will remain and thus the system will most likely lose consistency.
Removing Sections may corrupt permission settings, template output and other things in the system.
Section ID numbers are not recycled. If a Section is removed, its ID number will not be reused when a new Section is created.
Users in Ibexa DXP are treated the same way as Content items. They are organized in groups such as Guests, Editors, Anonymous, which makes it easier to manage them and their permissions. All User Groups and Users can be accessed in the Admin panel by selecting Users.
Be careful not to delete an existing User account. If you do this, content created by this User will be broken and the application can face malfunction.
Registration form for your website is placed under this address:
To give users an access to your website you need to assign them Roles in the Admin Panel.
Each Role consists of:
Rules that give users access to different function in a module. You can restrict what user can do with Limitations. The available Limitations depend on the chosen Policy. When Policy has more than one Limitation, all of them have to apply. See example below.
Limitation specifies what a User can do, not what they can't do.
Location Limitation, for example, gives the User access to content with a specific Location, not prohibits it. See Available Limitations for further information.
After you created all Policies, you can assign the Role to Users and/or User Groups with possible additional Limitations. Every User or User Group can have multiple Roles. A User can also belong to many groups, for example, Administrators, Editors, Subscribers.
Best practice is to avoid assigning Roles to Users directly. Model your content (Content Types, Sections, Locations etc.) in a way that can be accessed by generic Roles. That way system will be more secure and easier to manage. This approach also improves performance. Role assignments and Policies are taken into account during search/load queries.
Ibexa DXP offers the ability to create multiple translations of your website.
Which version is shown to a visitor depends on the way your installation is set up.
A new language version for the website can be added in the Admin Panel in the Languages tab.
Every new language must have a name and a language code, written in the
xxx-XX format, for example
The multilanguage system operates based on a global translation list that contains all languages available in the installation. After adding a language you may have to reload the application to be able to use it. Depending on your set up, additional configuration may be necessary for the new language to work properly, especially with SiteAccesses.
See Languages for further information.
A Content Type is a base for new Content items. It defines what Fields will be available in the Content item.
For example, a new Content Type called Article can have Fields such as title, author, body, image, etc. Based on this Content Type, you can create any number of Content items. Content Types are organized into groups.
You can add your own groups here to keep your Content Types in better order.
Object states are user-defined states that can be assigned to Content items. They are contained in groups.
If a state group contains any states, each Content item is automatically assigned a state from this group.
You can assign states to content in the Back Office in the Content item's Details tab.
By default, Ibexa DXP contains one Object state group: Lock, with states Locked and Not locked.
Object states can be used in conjunction with permissions, in particular with the State Limitation. Their specific use cases depend on your needs and the setup of your permission system.
You can use Segments to display specific content to specific Users. They are used out of the box in the Targeting block in the Page.
Segments are collected in Segment Groups:
Each Segment Group can contain Segments that you can target content for.
You can assign Users to Segments through the API.