Problems with QuickUpdates installation

[Reesy]

Thank you for your suggestion but I dont want to add another configuration somehow.

[whocaresanyway]

that is where your error is,
300 has been used by another module.

so by adding it as '' it will auto increment.

you will need this to have the module work.

[DrByte]

A. BE SURE TO DO A DATABASE BACKUP FIRST !!!

1. Find out what id#300 is:

SELECT configuration_group_title FROM configuration_group where configuration_group_id = 300;

2. if the result from the statement above is "Quick Updates", then you can run the following to remove it:

DELETE from configuration_group where configuration_title = 'Quick Updates';
DELETE from configuration where configuration_key like 'QUICKUPDATES_%';

3. If the result from step 1 is NOT "Quick Updates", then you have some other mod using that group id, and removing it may cause you other grief.

[Reesy]

A. BE SURE TO DO A DATABASE BACKUP FIRST !!!

1. Find out what id#300 is:

SELECT configuration_group_title FROM configuration_group where configuration_group_id = 300;

2. if the result from the statement above is "Quick Updates", then you can run the following to remove it:

DELETE from configuration_group where configuration_title = 'Quick Updates';
DELETE from configuration where configuration_key like 'QUICKUPDATES_%';

3. If the result from step 1 is NOT "Quick Updates", then you have some other mod using that group id, and removing it may cause you other grief.

Database is backed up :)

Hi Chris,
Thanks for the above. It is definately quick updates and it definately has a config id of 300 as I can see it in the task bar but when I tried your code I received...

1054 Unknown column 'configuration_title' in 'where clause'

[Reesy]

I THINK that should have read...
configuration_group_title not configuration_title
Can anyone confirm please?

DELETE from configuration_group where configuration_group_title = 'Quick Updates';
DELETE from configuration where configuration_key like 'QUICKUPDATES_%';

[Reesy]

Well the database is backed up and the sql errors suggested to me the above was correct so I tried it and it worked!

Thanks to all those that helped!!!!!!!!!!!!!!!

[DrByte]

yup - correct ... sorry for the typo.

[Reesy]

No need to apologise Dr.
Without your help I wouldnt have had much of an idea.

[Reesy]

Sorry, I re-read the above and I forgot to add.
Id like to drop the changes first before applying the fix above for the sql.
Thanks for the fix.

Can anyone help with removing it first?
Thanks