PHP and MySQL Web Development 4th Ed-tqw-_darksiderg

Defining the Script Architecture
701
In the final section of the index.php script, you send an HTML footer using the
do_html_footer() function from output_fns.php.
Let’s look briefly at an overview of the possible actions in the system.These actions
are shown in Table 30.2.
Table 30.2 Possible Actions in the Mailing List Manager Application
Action Usable By Description
log-in Anyone Gives a user a login form
log-out Anyone Ends a session
new-account Anyone Creates a new account for a user
store-account Anyone Stores account details
show-all-lists Anyone Shows a list of available mailing lists
show-archive Anyone Displays archived newsletters for a particular list
information Anyone Shows basic information about a particular list
account-settings Logged-in users Displays user account settings
show-other-lists Logged-in users Displays mailing lists to which the user is not subscribed
show-my-lists Logged-in users Displays mailing lists to which the user is subscribed
subscribe Logged-in users Subscribes a user to a particular list
unsubscribe Logged-in users Unsubscribes a user from a particular list
change-password Logged-in users Displays the change of password form
store-change- Logged-in users Updates a user’s password in the database
password
create-mail Administrators Displays a form to allow upload of newsletters
create-list Administrators Displays a form to allow new mailing lists to be
created
store-list Administrators Stores mailing list details in the database
view-mail Administrators Displays newsletters that have been uploaded but
not yet sent
send Administrators Sends newsletters to subscribers
One noticeable omission from Table 30.2 is an option along the lines of store-mail—
that is, an action that actually uploads the newsletters entered via create-mail by
administrators.This single piece of functionality is actually in a different file, upload.php.
We put this functionality in a separate file because it makes keeping track of security
issues a little easier on us, the programmers.
Next, we discuss the implementation of the actions in the three groups listed
in Table 30.2—that is, actions for people who are not logged in, actions for logged-in
users, and actions for administrators.