StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2072311
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-15T14:41:35.067
FavoriteCount
0
LastActivityDate
2010-01-15T14:41:35.067
LastEditDate
LastEditorUserId
0
OwnerUserId
233002
ParentId
2064735
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
i did this last week and was also a bit lost at first. I can tell you what i did, and you adapt to your solution. In my solution i had a module called Notifications, with the following fields: id, content, state, sent_at, instance, created_at. In my problem notifications could be sent to a list of users, so the users are foreing data, not saved in the notification table (1 to n relation). So when you Edit o create a notification i only show a few fields of the notification (like it content, and the instance) the other fields like the date are not editable (my choice). So in the creation i show only 2 of the 6 fields of the class. And also i want to see a list of users to multi-select, so i use a partial located in the template folder called "_get_all_users_list.php" that has a criteria and returns a multi-select tag. _get_all_users_list.php file <pre><code><?php echo select_tag('users', objects_for_select( UserPeer::doSelect(new Criteria),"getId","getUsername") ,array( "multiple"=>1, "size"=>15) ); ?> </code></pre> And to be able to show the list of users in the generator.yml i do this: <pre><code>generator: </code></pre> class: sfPropelAdminGenerator param: model_class: Notification theme: default <pre><code>list: title: Notificaciones max_per_page: 20 display: [ id, content, state, sent_at, sknow_instance, created_at] object_actions: _edit: ~ _delete: ~ batch_actions: _delete: ~ edit: title: Modificar notificacion: display: [content, sknow_instance, _getAllUsersList ] fields: content: { name: Notification content, type: textarea_tag, params: size=80x5 } get_all_users_list: { name: Select one or more users to be notified} </code></pre> as you see in the "display:" area of the generator.yml on edit, you can declare the fields you want to be editable/enabled on creation, and if you want to include a partial, you must declare it with a _ in the begining and in the camelCase format, and the name of the partial must start with a _ and the name must be separated by _ . I found very useful this chapter of symfony's book <a href="http://www.symfony-project.org/book/1_2/14-Generators" rel="nofollow noreferrer">Admin Generator</a> i hope it help, and sorry for my english.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSymfony admin generator: Filtering the display columns
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USLuciano
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.