> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.weltpixel.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to resolve conflicts between the WeltPixel and Amasty Color Picker functionalities

If you're using any of our extensions, you'll notice it comes with a Backend module as a dependency which is required to centralise settings and ensure proper core functionality. If you're also using an Amasty extension that comes with a color picker feature attached to its settings, you might run into a conflict that looks something like this:

![Screenshot_at_Jan_05_14-44-14.png](https://storage.crisp.chat/users/helpdesk/website/-/1/0/3/f/103f26b8405d7f00/4ac929da-bb3c-4bd9-b222-aebe52_9kktz2.png)

This happens because the Backend extension includes its own color picker which kicks in whenever a color needs to be selected. Fortunately, the resolution to this conflict is quite a simple one, so let's go over it below:

1. Connect to your store via FTP/SFTP and access the root of your Magento 2 project
2. Navigate to **app/code/WeltPixel/Backend/view/adminhtml/layout**
3. Delete the **adminhtml_system_config_edit.xml** file
4. Flush all your available caches
5. Re-check the settings that require the use of a color picker

After following the steps above, you should only see the Amasty color picker being displayed. This will apply to all settings that require the use of a color picker.