On 30 April 2013 12:06, Mason James <mtj@kohaaloha.com> wrote:

On 2013-04-30, at 11:16 AM, Mason James wrote:

On 2013-04-30, at 9:38 AM, Paul wrote:

...

Hi Jared,

At 10:41 AM 4/28/2013 -0400, you wrote:

...

Paul,

I've looked at the code in cleanup_database.pl (and search.pl), and can't see any obvious reason to "redirect to Installer."

So -- what has happened? Â Can I dump the cleaned db back into production? What are the specific changes 3.8.5 to 3.8.10 that required "updating"?

The redirect is because you had a newer version of the code than the database was run on.

Thanks for your reply, but this is worrisome. I had at {server}/ a tarred 3.8.10. I had at {server}/home/paul/ an untarred 3.8.10 (for .dif purposes.)

...

Koha doesn't have any support for automatic upgrades, so I guess you must have untarred 3.8.10 at some point.

[see above] O.K. it's not "automatic" but it did in fact run automatically without my permission. I ran:

for the record Paul, Koha is *designed* to do this very thing

it forces the web-update page, if the database is older than the codebase (as yours is)

this is a 'feature' to stop stupid humans from corrupting their Koha databases, when attempting to run mismatched codebases and db versions

But as Jared says it will not do this without you entering your database user and password, and explicitly clicking to tell it to upgrade. It will give you the page, but it won't upgrade until you tell it. The only automatic thing is it telling you you need to upgrade your database Chris