hi, thanks for the reply. I am less concerned with accessing a request via get and/or post, and more interested in how the model should be represented along with it's own form to edit or delete the row represented by the model.
For instance, say a recordset of 3 users is returned, with the respective ID's of 1, 5, and 10. This means that each table row will need a form with a hidden element containing that ID to post to the edit or delete action. For example, a list of users with edit/delete buttons: id | action ------------------- 1 | edit (form; action = edit, hidden element set to ID =1) | Delete (form; action = delete, hidden element set to ID = 1) ------------------- 5 | edit (form; action = edit, hidden element set to ID =5) | Delete (form; action = delete, hidden element set to ID = 5) ------------------- 10 | edit (form; action = edit, hidden element set to ID =10) | Delete (form; action = delete, hidden element set to ID = 10) ------------------- So if a user mapper returns an array of user objects, how would i incorporate the "individuality" of each form so it can be associated with each record and rendered appropriately in the view? If i were to make the edit/delete action accessible via GET it would be simple, as i would only have to the use the view's url helper, but seeing as any requests that change data should be made via POST, i'm unsure how to proceed :? -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Creating-edit-delete-forms-when-displaying-tabular-data-structure-in-controller-tp3331368p3332255.html Sent from the Zend Framework mailing list archive at Nabble.com.
