Tickets :: Comment on [#9986] Database migration triggered on non-database setup

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .___\ /.__. \|__\|[ __[__ >< [__] \| \|[_./\| / \\| \|
Comment	> Hello, > > I've updated my Kolab devel box to Horde4. The box is running without > a database server. I selected SQL type "none" in the horde prefs. > > conf.php contained a "$conf['sql']['phptype'] = 'false' line IIRC. > > Later on the LoginTasks for the admin try to trigger a DB upgrade > because of this code in horde/lib/LoginTasks/Task/AdminCheck.php: > > if (!empty($GLOBALS['conf']['sql'])) { > /* Check for outdated DB schemas. */ > $migration = new Horde_Core_Db_Migration(); > foreach ($migration->apps as $app) { > $migrator = $migration->getMigrator($app); > if ($migrator->getTargetVersion() > > $migrator->getCurrentVersion()) { > $GLOBALS['notification']->push(_("At least one > database schema is outdated."), 'horde.warning'); > Horde::url('admin/config', true, array('app' => 'horde')) > ->redirect(); > } > } > > Should the [none] SQL database type completely remove > the $conf['sql'] key or does the code above need to handle the "false" case? > > Cheers, > Thomas >
Attachment
Watch this ticket