Thanks for the detailed responses. The updated wireframes for this feature are
on this link: http://ezxjqv.axshare.com/?Page=Related_data__custom_field_
My feedback on your comments is below:
@Daniel: I confirm that the example you provide in your post will be met. We are planning to
cover Pages but at this point it is not 100% that they will make it for the 7.0 release. If not, they will be released one month later, in April. As to the content selectors, once these are done we can distribute them in a custom build here in this thread.
2) content deletion cleanup of linked items was included in the specs, thanks for the note.
3) On the user picker, this option is also in the plans, but not 100% for the release in March. It will be included in the next iteration.
4) a relate content "Forms" widget was logged as a request for future
iterations as well . Thanks, it seems very usable.
Permissions will be taken into account when displaying related items in the
Question: What about the backend? If a user cannot view “news1” should he be able to see it as related item under “event1” in the backend or should it be hidden?
As to hierarchical relationships, related fields will not be appropriate to use for such purposes. Hierarchies are special in that relationships there are two sided (item1 and item 2 are related in way that item 1 is parent to item 2, and item 2 is a child to item1). Very often in hierarchies you want a deletion of a parent to delete all children. Also you want permissions set per parent to be inherited by all children. This is why we prefer to treat hierarchies as a separate feature from related data. The major restriction of the current hierarchies seems to be that one parent content type can have only one child content type. We can remove this restriction and allow for multiple children
Here are sample wireframe for this feature: http://v24ub3.axshare.com/?Page=Module_page
I confirm that there will be interface for picking custom content type data in the interface.
On the question if “the user will still be able to edit them through their own
content item page”: I confirm that Presenters will be edited in the Backend Screens for Presenters and users will not have to go through “Sessions”. Later this week, we will present the
wireframes and you will be able to see the exact user flow.
The comments on your requirements are with >> below:
“1) make sure you can relate to the same
content in a hierarchical fashion”
>> This feature was added to the plan. It will be included in some of the
releases after 7.0.
2) Limiting the amount of items a user can relate to a content item
>> Admins will be able to if one or many items can be related.
3) ensuring that this related data information works when you export a dynamic
>> this was included in the spec, thanks!
4) media selector field to a custom module
>> I confirm that this will be possible.
>> This will be possible.
6) Well tested.
>> We are not planning to rush on this feature.
We will try to insert those so called automatic relations for the 7.0 release. Users will have to insert those widgets on the widget templates of the content widgets and specify the parameters based on which to display them. Steve, we will make sure random content can be generated as well.
@ gregory hernandez – I confirm that duplicating forms will be included in 7.0.
I have some additional questions for you:
>> Related items will be shown in a section of the
edit screen: http://ezxjqv.axshare.com/?Page=Item_related_data
We were discussing internally that this placement might not be very suitable when
dealing with a big number of related items. What is your opinion on this placement?
Thanks for your feedback,