Bricks and attributes
Some classes hold product attributes in two of Pimcore's field types: object bricks and the classification store. Both can be edited in Keel, and a class without them looks as it always did.
Keel doesn't change what a brick or attribute is. That stays in Pimcore: a developer defines the bricks, an administrator defines the store with its groups and keys. Keel edits the values.
Object bricks
A brick is a set of fields that an item can have or not have, like Dimensions or Technical data. The field shows a card for each brick on the item.
- Add … under the cards adds a brick. Only the bricks the class allows are offered, and each one once.
- Click a card's title to open or close it.
- Remove takes the brick off the item. It stays until you press Save, and Undo or Ctrl Z brings it back.
A required field in a brick must be filled before you can save. Fields with a language use the language buttons in the editor's header, like any other field.
Attributes (classification store)
A store holds attributes in groups, and it can have thousands of them. So the field is a panel with a page of 30 rows at a time.
| Control | What it does |
|---|---|
| Search attributes | Finds attributes by name, title or description, in all groups on the item |
| All groups | Shows one group |
| All attributes | Shows only Filled or Empty attributes. Unsaved lists what you have changed, on any page. To fix lists what a save refused |
| Language | On a store with languages: the language in the editor's header, or All languages for a value that holds for every language |
| Add group | Search the groups this field allows and add one. Its attributes show at once |
| Remove group | On a group's heading. The group and its values go when you press Save, and Undo brings them back |
| Previous, Next | The pages |
What you type stays when you search or change the page. Nothing is written until you press Save, and a save writes only what you changed. Everything else on the item stays as it is, also what the panel doesn't show.
A required attribute must be filled when its group is on the item. If a save refuses a value on another page, a line above the rows says so, with Show to list those attributes.
Text, numbers, choices, yes/no, dates and quantities with a unit can be edited here. Other kinds of attribute show (edit in Pimcore).
A value for all languages
On a store with languages, a value under All languages shows in every language that has no value of its own. It can be changed only by someone who may edit all languages.
On variants
An item with a parent shows what it takes from the parent, for each brick field and attribute, with the same lines as other fields: Inherited from, Overrides the value of, and Use parent value. See Variants.
- A brick or group the parent has also shows on the variant. Saving the variant copies nothing of it: only what you type becomes the variant's own.
- A brick the parent has can't be removed from a variant. Its button says Use parent values, which empties what the variant holds in that brick.
- A group the parent has has no Remove on the variant. Its heading says which item it comes from.
Reading only
If you may only read these fields, you see their values as text. Search, the filters and the pages still work.
History
The History tab lists these changes one by one: a brick or group added or removed, and each field or attribute with its language. Restore previous value puts back that one change. Undo this save puts back all of them, and removes a brick or group the save added. After 50 changes in one field the list stops, and Undo this save still covers them all.
What is not here
- Lists have no columns or filters for bricks and attributes, and Set field on many items doesn't offer them.
- The classic admin shows them read-only, with at most 200 attributes.