# Removing old plugins - Correct way - upgrading to 4.3 with legacy conflicts

**URL:** <https://forum.mautic.org/t/removing-old-plugins-correct-way-upgrading-to-4-3-with-legacy-conflicts/24263>\
**Category:** Mautic 4 Install/Upgrade Support\
**Created:** [May 29, 2022, 1:23am UTC](https://forum.mautic.org/t/removing-old-plugins-correct-way-upgrading-to-4-3-with-legacy-conflicts/24263 "2022-05-29T01:23:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [May 29, 2022, 1:23am UTC](https://forum.mautic.org/t/removing-old-plugins-correct-way-upgrading-to-4-3-with-legacy-conflicts/24263/1 "2022-05-29T01:23:16Z")

</div>

**Your software**  
My Mautic version is: 4.3.1  
My PHP version is: 7.4

What is the best method for cleaning up old plugins from mautic?

With 4.3 we had a heap of plugin conflicts and I am just not using them.

Specifically SQL conditions bundle

> **[GitHub - mtcextendee/mautic-sql-conditions-bundle: Custom SQL condition for...](https://github.com/mtcextendee/mautic-sql-conditions-bundle)**
>
> Custom SQL condition for campaigns. Contribute to mtcextendee/mautic-sql-conditions-bundle development by creating an account on GitHub.

Getting the following error when I remove the plugin directory

```auto
In MappingException.php line 63:

  File mapping drivers must have a valid directory path, however the given path [/home/domain.com.au/public_html/plugins/MauticSqlConditionsBundle/Entity]
  seems to be incorrect!

```

I have also gone into the db and changed the plugin table to is\_missing = 1

I believe this is preventing me from migrating to the latest version, I have 4.3 files but the database is out of sync

Screenshot of my cli with the attempts

 ![image](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/d/dc6698d2801cfc1aa97bffc927499ca3d8625eca.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/mautic/original/2X/4/479fe6264c4eb21333e8f06b8efb02823f756c90.png)

---

<div class="post-metadata">

**Author:** ![tornmarketing](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/tornmarketing/32/11603_2.png) [@tornmarketing](https://forum.mautic.org/u/tornmarketing)\
**Post date:** [May 30, 2022, 4:47am UTC](https://forum.mautic.org/t/removing-old-plugins-correct-way-upgrading-to-4-3-with-legacy-conflicts/24263/2 "2022-05-30T04:47:36Z")

</div>

Gave up and did a root file update from a fresh download which resolved this headache

There must be other files other than local affecting the plugin management I dont have visibility over.

Now onto the new headaches of non existent indexes for upgrades 🙂  
Feels very sloppy this upgrade haha