![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
A. Dynamic table to display message topics. B. Topic number. C. Topic name. D. Number of messages. E. Date of last post. F. Link to delete topic. G. First, last, and total number of topics. H. Navigation links. Content SourcesThe Manage Topics page is identical to the Topics page, except that it includes a link to delete each topic. The content source is a custom SQL query, with the topics sorted by name. AThe dynamic table displays the available topics. It uses Records per Page to show the topics eight at a time. Notice that the table begins with the row that contains the column labels, since GoLive would treat the row above that as the template row if it were part of the dynamic table. BThe topic number is the same as in the Main View. See the Topics page for more details. CThe topic name is the same as in the Main View. DThe message count is the same as in the Main View. EThe date of the last post is the same as in the Main View. FThe link to delete a topic should use Show Details of Current Record so that the delete confirmation page knows which topic to delete. Unfortunately, MySQL cannot determine the record key to use with this query. This is a limitation of the current version of MySQL. To workaround this, we create a link with the record key information explicitly placed. The link in the inspector looks like this:
This is the format GoLive expects to position the content source on the delete_topic.php page to the specific topic to be deleted. GThe information about which records appear on the page is the same as in the Main View. HThe navigation links are the same as in the Main View. |