web pages left to code:
=============================================
make sure all 'active' flags are being used for booths, content, tradeshows, etc.

LATER in another version:
(non critical to phase I and II)
=============================================
add an index for Booth_Table for the first 2 characters of the booth name and also first 2 chars of company name for faster display on tradeshow index.phtml pages

I accidentally misspelled _booth_ as _both_ in the content SQL tables. grrr.
I want to go through and fix that. Basically a huge global search and replace. just annoying.

admin/style.phtml should allow the admin to create the directory and upload the files via the web form, then when they delete a style, it should delete the directory.
Since you are the only admin, for now, you just have to do this upload via an ftp program and then use the page to make an entry in the database.

put the textfield character counter on fields that need it if we really are limiting their verbiage. seems like it's not necessary though.

Pretty date format on news story entry (content).

should booths themselves have 'active' flags, like tradeshows and content does? so we can temporarily dissable a booth without removing it.

while the "login" test will pass for a boothmanager on tradeshow pages and vice versa, 
you generally can't do anything b/c the data doesn't match up. however, 
i should check to see the TYPE of login you are and nip it in the bud.

should we auto insert <BR> or <P> in the vrexhibits/boothmanager/content.phtml pages where descriptions are needed?

If the tradeshow is private, it requires registration.
If it is public, no registration required.

allow booths to have 'directory paths' within a tradeshow (use the same dir name)?
http://daevid.com/examples/vrtradeshow/myTradeShow/SomeBoothInMyTradeShow 

http://daevid.com/examples/vrtradeshow/tradeshow/press_detail.phtml?news_id=11
will allow you to see any news story, even ones not in this 'tradeshow'

switch to InnoDB format databases?