> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/integration-and-extensions/plugin-conflict.md).

# Plugin conflict

### Will the AppMySite plugin conflict with other plugins on my WordPress website?

The AppMySite WordPress plugin is designed to operate independently and should not conflict with other plugins installed on your website. We prioritize compatibility, ensuring that our plugin seamlessly integrates with a wide range of WordPress and WooCommerce plugins without causing disruptions or conflicts.

However, if you encounter any issues or notice a conflict with another plugin, our support team is readily available to assist you in promptly resolving the matter. Feel free to [**reach out to us for any help or guidance**](https://app.appmysite.com/email-support)**.**

Follow our troubleshooting guide for detailed instructions on resolving website and app connectivity:

{% content-ref url="/pages/8fWHPvqMnE2oE8cBdzja" %}
[Troubleshoot connectivity](/app/connectivity/wordpress-connectivity/troubleshoot-connectivity.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/frequently-asked-questions/integration-and-extensions/plugin-conflict.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.