Getting rid of stubborn extensions.

[jamie]

I need to upgrade from version 9.1.9 to 9.2.5. Before doing so, I want to clear out some old extensions. Whether I try to remove them via the CLI or the GUI, I can't seem to get rid of the following—and likely others as well. Since I’m not receiving any errors in the CLI or logs, I’m not sure what to do:

• Name: eSignature Documents for EspoCRM
  ID: 62ac8dc7437add710
  Version: 3.0.9
• Name: Dav Integration
  ID: 65a68de72a7a17846
  Version: 1.0.1
• Name: Dubas Google Fonts
  ID: 6356a12b70bf11599
  Version: 1.0.0

I did have to increase my PHP memory limit to 8GB, but at least the CLI process now completes successfully.

[victor]

You can try to remove via CLI using the ID of each extension.
This is the recommended method.

bin/command extension -l

and after

bin/command extension -u --id="extension-ID"

If that doesn't work, physically delete each of the unnecessary folders in /espo_root_folder/custom/Espo/Modules/ --> Make Rebuild via CLI.
This is the not recommended method.

[shalmaxb]

In addition, somtimes there maybe rests of extensions in the database -> table extensions. You can delete the respective rows.

[jamie]

You can try to remove via CLI using the ID of each extension.
This is the recommended method.

bin/command extension -l

and after

bin/command extension -u --id="extension-ID"

If that doesn't work, physically delete each of the unnecessary folders in /espo_root_folder/custom/Espo/Modules/ --> Make Rebuild via CLI.
This is not the recommended method.

yeah it was via the CLI I was doing it, and still didn't, and as shalmaxb said, likely random database stuffs is hanging around Thankful I had another install i use to demo stuffs where the uninstall worked and i moved around the databases

[shalmaxb]

There could be another reason for errors after deleting custom extensions. If such extension for example creates a custom field, you might have to delete any of those fields you created. If not, the persisting field cause espoCRM to try to connect with the javascript file of that deleted extension, which obviously are not available anymore.

Took me a few hours to find that cause.

[jamie]

There could be another reason for errors after deleting custom extensions. If such extension for example creates a custom field, you might have to delete any of those fields you created. If not, the persisting field cause espoCRM to try to connect with the javascript file of that deleted extension, which obviously are not available anymore.

Took me a few hours to find that cause.

dam i feel that pain! It would be great if all extensions had a migration file so you knew what it did