doom4

i ve installed one component twice and now i cant delet them only one of them so i ve 2 entries in the compontes list
in the new version i want that mambo is blocking a twice installation or the possibility of deleting it.

THX

keliix06

The only way to delete it is to go in through your database. Mambo can only follow the directions in the uninstall file and delete the hard files. If the uninstall file doesn't say to drop anything from the database, there is no way for Mambo to know to.

You can go through phpMyAdmin to mos_components and delete the rows that point to the component there.

doom4

so i wish that mambo blocks twice installtions of components

Edi

I wish that too !!!

__________________
Edi Online powered by Mambo... soon...

keliix06

That works

jomaco1

More on this subject: Installed Component twice - how do I remove the second entry

__________________
Mark

Arthur...congrats on the rebuild! Hope it stays clean.

Click HERE to view signature. (If nothing happens at first...keep clicking)

mmx

I cheat.

Before attempting to delete a duplicate component, I copy a set of the component directories elsewhere (both the frontend and backend directories), then delete the first instance of the component, then move the earlier copy back under the two components directories before deleting the second instance.

Mambo does a search to check if the directories exist. If they don't exist, you can't delete the second copy. Or something along those lines.

coke

nice thought

doom4

Good morning mambers!


Thats a possibility but now i am using this component and it sucks that its twice in the rollout menu. if i am doing it like u all saved informations are lost .

So i hope i the next version there will be a prompt "u ve allready installed this component chose another dir oder cancle"

mmx

In cases like that, you do not want to delete the component.

Instead, you want to find the second set of records in mos_components, delete them, and do nothing else. These will be exact duplicates of the first set of records with different record ids.

The problem has existed since the first alpha development release last summer and I'm not sure why it was never fixed. The solution is for the installer to query the mos_components table for the existance of a option field value of the same name and to use a conditional statement to display an error message. Maybe there is more to it than that, but I doubt it.