For all details about LOVD, see our LOVD flyer! (last updated February 24th, 2010)

• What has changed in LOVD v.2.0?
• Will the software requirements change for LOVD v.2.0?
• Will you implement ..., too?
• Can I upgrade from my 1.1.0 installation?
• How much hard drive space does LOVD require?
• How do I upgrade my 2.0 installation to a new build?
• I get the error "Error 500 - Internal Server Error"
• I get the error "Can't find config.ini"
• I get the error "Can't read config.ini" or "Can't open config.ini"
• I get the error "Your configuration file is NOT protected!"
• I get a blue error table which says "Error: Init"
• I get a blue error table which says "Error: Query"

Please go through the LOVD proposal document to see the changes between 1.1.0 and 2.0. The most important changes are mentioned there.
For an in-depth list of changes since the very first 2.0 releases, see the Changelog.

Yes, you now need PHP 4.2.0 and up (1.1.0 required 4.0.3). Also, we plan to drop support for the MySQL server versions older than MySQL 4.0 in a later release. MySQL Server 4.0 has been available for general release since 2003, so we predict no problems with this change. If you feel differently, please let us know.
See the software requirements.

If you have a feature request, please add it to our bug tracking system.

Implementing such an upgrade script was not a priority at first, although it was planned for a long time. However, since many of the remaining 1.1.0 installations are already manually transferred to 2.0, the need for it has decreased. We do have a script that can copy and convert all submitters from a 1.1.0 installation to a 2.0 install. If you would like to have a copy of this script, please contact us.

A LOVD installation itself takes very little space on the hard drive. Only 2.0 MB for the application files, and our biggest database (32 genes, 21.000 variants) takes only 4 MB of MySQL (MyISAM) table space.
The LOVD Local install CD that we have available for Windows, requires 200 MB of free space on your C: drive, but also installs all software required by LOVD.

Upgrading your 2.0 installation to a new build is as simple as downloading the new build, unpacking the downloaded file and overwriting all old files. Logging in to LOVD will then finish the upgrade automatically.

Apache found the .htaccess file, that should hide the config.ini and set a PHP option. Apache is currently set to disallow either Limit or Options for the AllowOverride directive. Make sure AllowOverride has at least "Limit" and "Options" set.

Please rename the config.ini-lovd file to config.ini and edit it's contents. For more information, please see the installation instructions contained in the INSTALL file, included in the package.

Please check the permissions of the config.ini file. LOVD cannot read it or open it's contents.

Please see the installation instructions contained in the INSTALL file, included in the package. In short: you will need to configure your webserver to block access to the config.ini file, preferably using the .htaccess file included in the LOVD package. Make sure you have the .htaccess file into your LOVD directory, on Unix and Linux systems it's a hidden file so it can be missed easily. When using Apache, make sure to have "Limit" and "Options" enabled in Apache's "AllowOverride" setting.

LOVD made a serious hiccup while communicating with the MySQL database. This is most likely a problem in your config.ini file.

Error connecting to database - Check the "username" and "password" fields of your config.ini.
Error selecting database - Check the "database" field of your config.ini.

LOVD made a serious hiccup while communicating with the MySQL database. This is most likely a bug in LOVD, but it may be prevented by changing a setting in MySQL. There are a lot of possible errors, so the list below is not complete.

Error : Column count doesn't match value count at row X - This is a bug in LOVD. File a bug report in our bug tracking system.

Error : Incorrect integer value: X for column Y at row Z - This is a problem with the strict setting in MySQL that LOVD currently does not apply to. You can fix it by editing your MySQL settings. There's a setting in your my.ini or my.cnf file, that's called "sql-mode". It has an option enabled called "STRICT_TRANS_TABLES" or "STRICT_ALL_TABLES". You need to remove those from the list, and restart the MySQL server.

Error : You have an error in your SQL syntax - This is a bug in LOVD. File a bug report in our bug tracking system.