![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
A. Username and date of message to delete. B. Delete and cancel buttons. Content SourcesThe Delete Message page uses the Messages table. When the user arrives at this page by clicking on a delete link, the content source automatically selects the message he has clicked. AThe username and date provide information about the message the user is about to delete. BThe delete button uses the Delete Record Form Action. Clicking it deletes the indicated message from the database. The success and failure pages are both set to messages_admin.php, so regardless of whether the delete action is successful, the user returns to the Manage Messages page. A better design would show a different page on failure to give a useful error message. The cancel button works differently. Instead of a Form Action, it uses client side javascript to implement the cancel behavior:
When the user clicks this button, he returns to the Manage Messages page without making any changes to the database. Note that the cancel button is a normal button, not a submit button. |