Artifacts in the code

[Kent Multer]

The reference to phpMyAdmin must be a clue. In my own work, I often find myself logging into phpMyAdmin repeatedly during a long work session. If that data string is phpMyAdmin's equivalent to a session ID, I suppose it could be used to keep a session alive at times when I'm not clicking any buttons in that browser tab. That could be handy, although putting the field into every form in the store seems kind of extreme.

[lesliekirk]

The reference to phpMyAdmin must be a clue. In my own work, I often find myself logging into phpMyAdmin repeatedly during a long work session. If that data string is phpMyAdmin's equivalent to a session ID, I suppose it could be used to keep a session alive at times when I'm not clicking any buttons in that browser tab. That could be handy, although putting the field into every form in the store seems kind of extreme.

It may have to do with the use of phpMyAdmin to export the MySQL database to install on a new server. Since I know that I didn't work in phpMyAdmin I know it wasn't me but perhaps it could have happened during the dump process? Perhaps the gaining host had to do something in the database to prep it for a move? I do seem to recall needing to supply access to it as part of a move from one host to another back when.