Ahh, nevermind about the .conf upgrade biz. I see what happened: I used the status html pages during the first run and triggered a bug in config_handler() that clobbered the .conf file.
What I did was:
1. access status.html
2. click ‘rescan’
3. strip the ‘?rescan’ from the url and reload the page
This was dumb, since the resulting url was ‘/config-update.html’ and not ‘/status.html’. I wasn’t paying attention. This causes the code to redisplay the status.html page (correct), but also fall through a case where the config file gets rewritten (with (null)) (incorrect). Dumb user mistake on my part. Not even really worth fixing, but I’ll take a stab and send Ron a patch.
These aren’t the droids you’re looking for.