Composer and predefined attributes

Permalink
I think if I add attribute-values to Page type, it should use these attribute-values as predefined values if same attributes are also composer-editable.

It would be somekind of "default" -value. Now the values are "empty" in Composer.

Temposaur
View Replies:
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi Temposaur,

Can you please rephrase your question, including specific details of what issue you are having and what you are trying to accomplish.
Temposaur replied on at Permalink Reply 2 Attachments
Temposaur
When I set values to attributes for the Composer, the Composer should use these values as default values. Now it doesn't use them at all if Composer form has the same attributes.

See my attachments.
MrKDilkington replied on at Permalink Reply 4 Attachments
MrKDilkington
@Temposaur

I believe I can confirm this.

- create a new page type
- add the Composer form controls (including the Skills Select attribute)
- select default Skills attribute items
- create a new page of that page type

The page created will display the Skills attribute list, but without the default selected items.

Please see attached screenshots.
MrKDilkington replied on at Permalink Reply 4 Attachments
MrKDilkington
@Temposaur

This does work if the Skills Select attribute is not added to the Composer form.

- create a new page type
- add the Composer form controls (WITHOUT the Skills Select attribute)
- select default Skills attribute items
- create a new page of that page type

The page created will display the Skills attribute list WITH the default selected items.

Please see attached screenshots.
Temposaur replied on at Permalink Reply
Temposaur
I know it works WITHOUT attributes attached to Composer form, but the main idea was to use Composer to add and edit pages with predefined values (not just with select attributes, but with text area -attributes etc.)

I'm not sure if it's a real bug, but it would be a very nice feature to use Page type's default values in Composer.
MrKDilkington replied on at Permalink Reply
MrKDilkington
@Temposaur

This is definitely a behavior that needs to be documented.
http://documentation.concrete5.org/editors/dashboard/pages-and-them...