TOPIC: Upgrade error....

The latest upgrade results in the following error when installing:


JInstaller: :Installeren: Fout SQL DB functie is mislukt met het volgende foutnummer 1060
Duplicate column name 'email_exam_results' SQL=ALTER TABLE `j25_lk_lessons_configure` ADD `email_exam_results` TINYINT( 1 ) NOT NULL DEFAULT '0';
SQL =

ALTER TABLE `#__lk_lessons_configure` ADD `email_exam_results` TINYINT( 1 ) NOT NULL DEFAULT '0';

Component updaten: SQL fout bestand DB functie is mislukt met het volgende foutnummer 1060
Duplicate column name 'email_exam_results' SQL=ALTER TABLE `j25_lk_lessons_configure` ADD `email_exam_results` TINYINT( 1 ) NOT NULL DEFAULT '0';
SQL =

ALTER TABLE `#__lk_lessons_configure` ADD `email_exam_results` TINYINT( 1 ) NOT NULL DEFAULT '0';

Pakket Installeren: Er deed zich een fout voor tijdens het installeren van een extensie: com_lmsking_professional.zip


Tom

Hi Tom,
can you please email me admin and ftp access details. I'll login and upgrade it for you.

I'm having he same problem, but am unable to provide admin access. Is there a workable solution that I can do on my own? Thanks!

The following is the method to use when you have this problem.
on your site go to /administrator/components/com_lmsking/sql/updates/mysql and delete the sql files there.
Then open the zip file that contains the lms_king component and go to the same directory and find the sql file that contains your query that is causing the error.
Put a # character at the start of the line to comment it.
Then save the changes to the archive and try the installation again.
If the error changes, you may need to comment the next command in the sql update files. It only takes a few minutes to do.

For me it was that the max_upload_size needed to be adjusted in the .htaccess file for the site. Even though the server php.ini file had 48M, it would not work until I put the larger amount explicitly within the .htaccess file.

All of these errors with sql are related to how the component was developed and released with bug fixes.
We did it wrong. I admit it.
But in the latest version 3.2.3.16 we took all the update sql files and removed them. We added to the installer, some sql validations and update the tables if the change hasn't been found.
So now there should be no more errors when upgrading the lms component.