![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
A. Dynamic table displaying the stories that are ready to publish. B. Form controls for editing title, priority, and publication status. C. Update button to write changes to the database. Content SourcesPublish Stories uses the Stories table from the Stories database. Because it should only show stories that are ready to publish, the content source uses record filtering to limit the query results. The query is almost identical to the one on the front page, except that it leaves out the ShouldPublish=true filter. It shows all the stories that are ready to publish so that the site editor can pick the ones that should appear. A.The dynamic table is bound to the Stories content source. Notice that the update button is not part of this table; if it were, GoLive would treat it as mock content. The two tables are contained within a single form so that the site editor can update the stories that are ready to publish. You can edit more than one story at a time by making changes to multiple rows in the table. B.The template row contains form controls to edit each story's title, priority, and publication status. These form controls are bound in the same way as ordinary dynamic text. C.The Form Action for the update button is Update Record. When you select a Form Action in the Dynamic Bindings palette, GoLive automatically targets the correct page in the config/actions folder to perform the indicated action. In this case, clicking the update button writes any changes the user has made to the database. The Update Record action can update any number of records at a time. |