Work Locations: Virginia, and finally, headed south for the winter with our first stay in Charleston, SC (see my wife's travel log).
More work on security. Ended up spending a lot of time playing around with Apache2 on my Macs. I finally got around to putting Mac OS X Server on a machine (a laptop) just to make it easier to set up a secure site to play with. Used the MacPorts (formerly DarwinPorts) Apache2 install. Easy to set up. Just borrowed some of the SSL config generated by Mac OS X Server's admin program as a starting point, plus OS X Server's default certificate for testing. Very easy to set up once I gave up on the version of Apache that Apple ships and switched to Apache2.
Move session store to MySQL. Logout resets the session to reduce likelihood of "session fixation" attacks on the site.
Add functional tests for user login, etc.
Sick: slow going. I get a bit stupid when I'm ill. Changed pull down lists to grouped lists.
Struggled with navigation issues. Is there an efficient way to jump to a display page containing a particular item when doing paginated display of a result set? The most efficient way of doing it does not work when jumping back from an edit page that modifies a field used in sorting the result set. The way that provides the correct page regardless of edits is much too costly. Should probably think about this when I'm not befuddled by "flu like symptoms".
Users can now view only the publicly available locations and locations that they "own". Previously, all locations could be viewed by anyone.
Reworked search infrastructure to make it easier to specify what search comparators are used for each field. Location search controls no longer permit the use of all comparators on all fields.
Took a break to visit family. Started reading "Beginning Ruby on Rails E-Commerce: From Novice to Professional", by Christian Hellsten and Jarkko Laine. Very good complement to the books I have been using. Somewhat different techniques. Much more oriented toward Test Driven Development (TDD).
Location type can only be changed between public/private types by the creator of the location. This limitation prevents accidentally exposing personal information, and prevents public locations from being made unavailable to the public.
Adding integration tests for user login, location browsing and editing. Reduced the number of actions in user controller.
Added data entry validations to location editing. Using data for Canada and the United States from ZipCodeWorld.com. May add data for Mexico later, but it is WAY too expensive for me to do it now. Why is the data for Mexico more than twice the combined cost of the data for Canada and the United States?
On Monday, 27 Nov: hit the road to head south for the winter. Work on ContinuousTraveler.com will be a bit more sporadic until we are settled in at Destin, FL.
Continue with minor changes to editing of locations. Change the detail page to more closely match format and content of the new location editing page.