We switched update.php from a front controller to a route so that it has a full environment to run in.
This however means that inbound path processors relying on a database table that has a schema change will not be able to update themselves - because they'd break update.php which is required to run the updates.
Move update.php back to a front controller, so that it doesn't have a direct dependency on inbound path processing or routing.
Additionally document systems that update.php relies on and the fact that they should only make backwards compatible schema changes, at least untilis resolved.
User interface changes
Data model changes
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 102,840 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.5 MySQL] 102,842 pass(es). View