Uninstalled "Photos" Module but.....

It's still showing in the "installed" section and when I click uninstall again it gives me an error:

It will need to be manually uninstalled.

To do that you need to paste the contents of the uninstall sql file into the SQL section in phpMyAdmin to run it by hand. The uninstall.sql file for the photos module is in modules/boonex/photos/install/sql

Than the dolphin cache will need to be cleared.

If you are unable to do that yourself you will need to hire someone to do it. It is not a procedure that is easy to explain.

I can do that, I will give it a go. Thanks!

ok, ran the .sql file and it was still in the list of installed modules, so i went into sys_modules and deleted Photos from there, it then was gone from installed modules.

But now it's giving me the exact same error when I try to reinstall the Photos module :/

That's because removing it from the sys_modules table does not actually remove it.

Run the sql file again. This time pay close attention to any errors that occur when phpMyAdmin tries to run it. If it does not complete successfully, it will not be complete. You will need to deal with any error that comes up.

And don't forget to clear dolphins cache.

Also make sure cache folder is writable.

And use phpMyAdmin to check and repair if necessary the sys_permalinks table.

Done it, removed all entries in the database to do with the photos module and it reinstalled fine :D

the uninstall.sql cannot fail, there's a "if exists delete" in there.

I used the error dolphin gave me to find the tables I needed to delete :D

Thanks for your help again Dean!

It's actually DROP TABLE IF EXISTS not if exists delete. Anyhow. Thats not all there is to a uninstall file. Some can contain code such as ALTER TABLE. And those WILL INDEED fail under certain circumstances. Do not assume all entries are just delete if exists type entries.

In fact that specific uninstall has a line that looks like this.
SET @iTMParentId = (SELECT `ID` FROM `sys_menu_top` WHERE `Name` = 'Photos' AND `Parent` = 0 LIMIT 1);

That one can also fail to set the @iTMParentId which in turn will cause the next line that uses it to fail.

There is also another set line as well for something else.

So you are incorrect. There indeed can be conditions where the uninstall.sql can fail.