Skip to content

Back Office configuration

Copy subtree limit

Copying large subtrees can cause performance issues, so you can limit the number of Content items that can be copied at once using ezpublish.system.<SiteAccess>.subtree_operations.copy_subtree.limit in parameters.yml.

The default value is 100. You can set it to -1 for no limit, or to 0 to completely disable copying subtrees.

You can copy subtree from CLI using the command: bin/console ezplatform:copy-subtree <sourceLocationId> <targetLocationId>.

Pagination limits

Default pagination limits for different sections of the Back Office can be defined through respective settings in ezplatform_default_settings.yml

Default Locations

Default Location IDs for Content structure, Media and Users in the menu are configured using the following settings:

1
2
3
4
5
6
7
ezpublish:
    system:
        default:
            location_ids:
                content_structure: 2
                media: 43
                users: 5

Notification timeout

To define the timeout for hiding Back-Office notification bars, per notification type, use the following configuration (times are provided in milliseconds):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
ezpublish:
    system:
        admin:
            notifications:
                error:
                    timeout: 0
                warning:
                    timeout: 0
                success:
                    timeout: 5000
                info:
                    timeout: 0

The values shown above are the defaults. 0 means the notification does not hide automatically.

Location for Form-uploaded files

You can use Forms to enable the user to upload files. The default Location for files uploaded in this way is /Media/Files/Form Uploads. You can change it with the following configuration:

1
2
3
4
5
ezpublish:
    system:
        default:
            form_builder:
                upload_location_id: 54

This applies only if no specific Location is defined in the Form itself.

Date and time formats

Users can set their preferred date and time formats in the User settings menu. This format is used throughout the Back Office.

You can set the list of available formats with the following configuration:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
ezpublish:
    system:
        <siteaccess>:
            user_preferences:
                allowed_short_date_formats:
                    'label for dd/MM/yyyy': 'dd/MM/yyyy'
                    'label for MM/dd/yyyy': 'MM/dd/yyyy'
                allowed_short_time_formats:
                    'label for HH:mm' : 'HH:mm'
                    'label for hh:mm a' : 'hh:mm a'
                allowed_full_date_formats:
                    'label for dd/MM/yyyy': 'dd/MM/yyyy'
                    'label for MM/dd/yyyy': 'MM/dd/yyyy'
                allowed_full_time_formats:
                    'label for HH:mm': 'HH:mm'
                    'label for hh:mm a': 'hh:mm a'

The default date and time format is set using:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
ezpublish:
    system:
        <siteaccess>:
            user_preferences:
                short_datetime_format:
                    date_format: 'dd/MM/yyyy'
                    time_format: 'hh:mm'
                full_datetime_format:
                    date_format: 'dd/MM/yyyy'
                    time_format: 'hh:mm'

You can also format date and time by using Twig filters and PHP services.

Allowed formats

The following subset of the ICU date and time formats is allowed:

Symbol Meaning
y, yy, yyyy, Y, YY, YYYY year
q, Q quarter
M, MM, MMM, MMMM, L, LL, LLL, LLLL month
w, WW week
d, dd day of the month
D, DDD day of the year
E, EE, EEE, EEEE, EEEEEE, e, ee, eee, eeee, eeeeee, c, cc, ccc, cccc, cccccc weekday
a AM or PM
h, hh, H, HH, k, kk hour
m, mm minute
s, ss, S... second
Z, ZZ, ZZZ, ZZZZZ timezone

Content Tree

With this configuration you can:

  • define configuration for a SiteAccess or a SiteAccess group
  • decide how many Content items are displayed in the tree
  • set maximum depth of expanded tree
  • hide Content Types
  • set a tree root Location
  • override Content Tree's root for specific Locations
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
ezpublish:
    system:
        # any SiteAccess or SiteAccess group
        admin_group:
            content_tree_module:
                # defines how many children will be shown after expanding parent
                load_more_limit: 15
                # users won't be able to load more children than that
                children_load_max_limit: 200
                # maximum depth of expanded tree
                tree_max_depth: 10
                # Content Types to display in Content Tree, value of '*' allows all CTs to be displayed
                allowed_content_types: '*'
                # Content Tree won't display these Content Types, can be used only when 'allowed_content_types' is set to '*'
                ignored_content_types:
                   - post
                   - article
                # ID of Location to use as tree root. If omitted - content.tree_root.location_id setting is used.
                tree_root_location_id: 2
                # list of Location IDs for which Content Tree's root Location will be changed
                contextual_tree_root_location_ids:
                   - 2 # Home (Content structure)
                   - 5 # Users
                   - 43 # Media

Universal Discovery Widget (UDW) configuration

The Universal Discovery Widget module (UDW) can be found in Extending modules.