Skip to main content
Keel Docs Showcase

Limits

What Keel deliberately leaves to Pimcore, and the limits worth knowing.

Fields edited in Pimcore

Keel shows these with their value and (edit in Pimcore):

  • calculated values, tables,
  • advanced many-to-many relations (shown as a table with the number linked),
  • links to Pimcore elements inside a link field,
  • select fields whose options provider fails.

Blocks that forbid adding, removing or reordering are shown read-only.

Object bricks and classification stores are edited in Keel: see Bricks and attributes. Inside them the same list holds, and so do key types Keel has no input for (tables, passwords, relations of another kind). The classic build shows both read-only, a store with at most 200 values.

In the content editor, every editable type is supported except custom ones; those show This field is edited in Pimcore. – run keel:check-editables to check a project's pages.

Field access

Custom layouts and language limits of workspaces are applied: see Field access.

  • A class-wide answer (lists, sort, filters, search, Export, bulk) follows the strictest workspace of the user, not each row's.
  • Limits cover whole fields: a block, field collection, brick field or classification store is hidden or read-only as one, not field by field, brick by brick or key by key inside it.
  • A language filter reads Pimcore's query tables, which hold fallback languages' text where a language is empty. With fallback_languages configured, a filter in an allowed language can match that text.
  • A project's own image provider is skipped for an item with hidden image fields, as it may read them.

Sizes

ListsNo limit: lists over page_threshold (default 150) are paged on the server
Tree listsUp to list_limit (default 1,000) items as a tree; more are shown flat and paged on the server
Linked-item choicesEvery item up to relation_option_limit (default 500); with more, the newest 20, and typing searches all
Asset libraryNo limit
Importimport.max_rows (10,000) and import.max_file_mb (20 MB) per file. Zip parts, unpacked size, packing ratio, shared strings and row size have fixed limits (XlsxReader). The changes of one file are at most 12 MB of JSON
Upload in the Assets areauploads.max_mb per file (default 100 MB)
Image upload in the editoruploads.editor_max_mb (default 25 MB), images only
Download as ZIP in Assetsuploads.zip_max_files (default 500) files, uploads.zip_max_mb (default 500 MB) in total
Asset bulk delete / moveSent in batches of 50 (the server takes at most 500 per request); Select all up to 5,000 files
Classification store30 keys a page, any number of keys; 200 values in the read-only view of the classic build; History lists 50 changes per field and save, Undo this save covers all
List filters12 conditions per list, 50 values per condition, 200 characters per text; only fields with a column of their own (not blocks, bricks or classification stores)
Saved views30 per person and 30 team views per list; 128 KB of saved views per person
Bulk changeUp to 20 items directly; more as a job on the server, at most bulk.max_items (default 200,000) items, bulk.max_active_per_user (default 3) jobs per person. With bulk.server_jobs: false: batches of 20 from the browser (assigning: 500), Select all matching up to 20,000
History of an itemLast 20 saves shown (Pimcore keeps more)
Setup → Historyhistory.keep (default 50) changes kept per person; a revert covers at most the first 5,000 items of a change

The values set in keel.yaml are in the keel.yaml reference; the fixed ones are listed under Fixed in code.

Variants and inheritance

  • A variant can't be emptied on purpose while its parent has a value: empty means inherited, as in Pimcore.
  • At most 200 variants open under a list row; the item's Variants tab pages through all of them.
  • Variants of variants: the list opens one level, the editor's Variants tab the next.
  • The list's search covers variants only with the Variants filter on.
  • A status or workflow marking field inherits like any field, until a change or a step writes the variant's own.
  • A row in a workspace below a parent the user can't read: no search, field filter or sort by field (see variants).
  • Object bricks and classification stores show the marker per brick field, key and language. A brick or group from a parent can't be removed on the child (Pimcore would put it back), only emptied.
  • Field collections don't inherit in Pimcore (supportsInheritance() is false), so they have no marker: a child's collection is its own.
  • The classic build shows none of this. The rules on the server hold there too.

Workflows

Workflow steps run through Pimcore's workflow manager, as in Studio. Keel leaves these to Studio:

  • Global actions of a workflow are not offered.
  • Custom HTML in a step's form and required additional fields of type user: the step is greyed out, with a hint to run it in Studio. An optional user field is left empty.
  • objectLayout of a place or step is not applied: Keel shows its own form.
  • The workflow graph and Studio's workflow details tab are not shown.
  • Data objects only. Pages and assets keep Pimcore's workflow actions.
  • Lists need a select field. Only a marking field that is a select becomes the list's pill and filter. Items with an empty field show as No status in lists, though the editor shows the workflow's initial place.
  • Bulk steps offer every step of the workflow. Which items it fits is checked per item when it runs, so skipped items only show afterwards.
  • A step cannot be reverted in Setup → History; run another step. The list's message has no Undo for the same reason.
  • A step whose save fails still leaves its note. Pimcore writes the note before it saves the item. If the save fails (for example a mandatory field is empty on a step that publishes), Pimcore puts the place back and Keel shows the error, but the note stays in Activity. Studio behaves the same.
  • Activity shows notes of the note types the workflows use. Pimcore stores no workflow name on a note, so other notes of the same type (default Status update) show there too.

Scheduled publishing

Scheduled publishing uses Pimcore's scheduled tasks (schedule_tasks), the same as Pimcore's Schedule tab:

  • It needs Pimcore's maintenance. Changes happen when bin/console pimcore:maintenance runs after the set time, through the pimcore_scheduled_tasks queue. Run it every 5 minutes; see Install.
  • Data objects only. Keel offers it in the object editor; pages and assets keep Pimcore's own Schedule tab. Keel sets publish, unpublish and publish version; delete tasks made in Pimcore are shown and can be cancelled.
  • Runs as the person who planned it, with their rights when it runs. A deleted user's tasks are switched off by Pimcore. The saves Pimcore makes are recorded without a user (Pimcore's behaviour), and are not in Setup → History.
  • Pimcore's classic editor may undo a schedule made in Keel. If an item is open in the classic admin's editor while a schedule is set in Keel, saving there writes the classic editor's Schedule tab as it was loaded. Reopen the item there first. Pimcore Studio's Schedule tab is not affected.
  • A saved version replaces the live item when it goes live: changes saved to the live item after the version was prepared are overwritten (the editor warns while one is waiting).
  • At most 20 planned changes per item. Lists show the clock and the Scheduled filter for up to 20,000 planned changes site-wide.
  • Times are stored as Unix timestamps; the browser shows and enters them in the user's time zone.

Completeness

  • Every required field counts the same: no weights.
  • A required checkbox counts when it was ever set, yes or no. "Must be ticked" cannot be expressed.
  • The editor's badge counts the last save, not what is being typed.
  • A rule is per class, also where a class has several lists.
  • Deleting an item or asset that items link to does not change their scores until they are saved or recalculated.
  • A rule naming a block, field collection, brick or classification store recalculates about 100 times slower than one naming only fields with a column in the query table.
  • A required field inside a block or brick cannot be named: only the block or brick as a whole.

Interface

  • The interface is in English, Croatian and German (admins set the default and the choice in Customize → Language, each user picks in My view; see Interface languages). Content can be in any language. keel:setup in the console is English only.
  • Bulk jobs of list items run on the server. Bulk actions in Assets and Pages still run from the browser: closing the tab stops them (the items already done stay saved).
  • Site check runs in the user's browser tab, one page at a time; closing the tab pauses it. Each page is built on the server by the site's own code, as a visit would be (what that means). Nothing limits who may start one or how often, apart from the page rights and page_check.enabled.
  • The import preview of a re-imported file runs in the request (about 2 minutes for 10,000 rows); long exports and History reverts of more than 100 items run as jobs on the server.
  • A worker killed in the middle of a bulk job can repeat the item in hand, and the History entry can miss the items of that one batch (each item keeps its own versions).