Commit graph

69 commits

Author SHA1 Message Date
Paul POULAIN
fd10552848 FIX for 1298 : removing hardcoded calls to mySQL, Perl, zebra & yaz-client
Signed-off-by: Chris Cormack <crc@liblime.com>
2007-09-24 15:29:06 -05:00
Paul POULAIN
e2364cbcfa adding Algorithm::CheckDigits dependancy, for barcode printing
Signed-off-by: Chris Cormack <crc@liblime.com>
2007-09-03 03:41:03 -05:00
Joshua Ferraro
7988048ca9 moving sql data to installer directory
Signed-off-by: Chris Cormack <crc@liblime.com>
2007-08-18 22:15:30 -05:00
Paul POULAIN
61c72f8f3e Adding KOHAVERSION management.
The kohaversion is in the code directory (in /kohaversion.pl)
C4::Context now has a new method C4::Context->KOHAVERSION
that returns the koha code version.
The systempreference Version contains the database version.

If the 2 are differents, when the user log in, he is redirected to web installer (new behaviour : before this commit, the check was done on everypage, it's too CPU costly I think)

In the web installer, we check now if we do a new setup or an upgrade and show only the appropriate link.

The updatedatabase contains a lot of new things :
* SetVersion($kohaversion), that set the kohaversion after each update
* TransformToNum($kohaversion) that returns a number (3.0000001 from 3.00.00.001 for example) for a given koha version
* DropAllForeignKeys($table) that does what is written : drop all foreign keys. A shame it's not possible directly in mySQL...
* for each database update, just :
add the following lines :
=item
    Describe what it does for other developpers
=cut

$DBversion = "your.koha.version.dbnumber";
if (C4::Context->preference("Version") < TransformToNum($DBversion)) {
	#
	# DO YOUR UPDATE STUFF
	#
        print "Upgrade to $DBversion done (specify what it does if you want)\n";
        SetVersion ($DBversion);
}

IMPORTANT NOTES :
in koha 2.2, a new install was done through installing a 2.2.0 database, then updating it to the installed version.
in Koha 3.0, /installer/kohaversion.sql MUST contain an uptodate version, as the installer set the DB version to kohaversion after uploading kohaversion.sql. It does NOT run updatedatabase.

The update from Koha 2.2 to Koha 3.0 must NOT be done through the webinstaller : updatedatabase is very very long to run and you'll reach Apache timeout for sure. See http://wiki.koha.org/doku.php?id=22_to_30 that contains my notes for upgrading (with some/few UNIMARC specific stuff)


Note For RM, please eyeball this change

Signed-off-by: Chris Cormack <crc@liblime.com>
2007-08-16 06:58:32 -05:00
Joshua Ferraro
836b9857ed content-type was incorrectly set in InstallAuth.pm
Adding 'wizard' and 'login' detection

Signed-off-by: Joshua Ferraro <jmf@liblime.com>
2007-08-15 21:22:21 -05:00
Chris Cormack
24d5e31dae Changing InstallAuth to use CGI::Session and fixing install.pl which broke
with the kohastruture.sql clean up

Signed-off-by: Joshua Ferraro <jmf@liblime.com>
2007-08-10 10:55:53 -05:00
tipaul
3ea77fd6a0 adding XML::RSS as mandatory package (to have RSS working) 2007-08-02 08:45:10 +00:00
hdl
73613b712b bug fixing install.pl
It is to be mentioned that error came from the use of DBI.
Indeed, we read sql file OK.
But the last command came with no order => error.

Next time we should be more careful.
2007-07-11 10:27:11 +00:00
kados
d585d5a2bc This is a language commit. I've gone through most of the templates and
based on user feedback I've made the following changes:

Borrower, Member => Patron
Debarred => Restricted
Issues => Checkouts
Reserves => Holds
2007-07-03 18:19:49 +00:00
tipaul
8767b123c4 improving installer : now the database Version is compared to the Koha version (defined by <kohaversion>XXX</kohaversion> in koha.xml file. If the Version systempref does not exist or is lower than kohaversion, you're redirected to installer. If there is no Version, you're redirected to the 1st step of the installer (full install). If Version < kohaversion, you're redirected to step 3 (updatedatabase). check that you have <kohaversion> in you koha.xml, otherwise, you'l loop forever to the installer... 2007-07-03 13:50:20 +00:00
slef
5579abe1fc Use DBI not mysql command-line to load the database tables 2007-07-01 18:43:57 +00:00
tipaul
8581fe4bbd updating web installer : going to step1 if needed and fixing sql 2007-06-26 14:30:22 +00:00
tipaul
23427c51b9 some fixes (and only fixes) 2007-06-15 13:44:44 +00:00
hdl
100e6a9808 functions that were in C4::Interface::CGI::Output are now in C4::Output.
So this implies quite a change for files.
Sorry about conflicts which will be caused.
directory Interface::CGI should now be dropped.
I noticed that many scripts (reports ones, but also some circ/stats.pl or opac-topissues) still use Date::Manip.
2007-04-24 13:54:28 +00:00
hdl
11fa5f5a2f Loading FrameworksLoaded for update before modifying. 2007-04-13 16:33:54 +00:00
hdl
b28590fdff Automatically adding a new syspref called FrameworksLoaded which is updated via webinstaller.
It stores and lists loaded frameworks for management.
2007-04-13 16:30:00 +00:00
hdl
66232241c1 Adding Check for a systempreference Version Variable
skips third party software check and mysql check to go to updatedatabase.

Adding similar check to intranet and opac.

BEWARE !!!!!
You may be linked to install if you donot have Version variable set in your systempreferences table.
If so, simply updatedatabase OR add Version 3.0  record to your systempreferences table.
2007-04-06 15:53:18 +00:00
rych
19d20b008b sort frameworks 2007-03-17 21:43:40 +00:00
tipaul
f8e9fb6445 rel_3_0 moved to HEAD (introducing new files) 2007-03-09 15:34:17 +00:00