> For the complete documentation index, see [llms.txt](https://wplake.gitbook.io/advanced-views/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wplake.gitbook.io/advanced-views/troubleshooting/compatibility.md).

# Compatibility

{% hint style="success" %}
**Enhanced compatible mode**

Enable this mode when you're stuck at the *Layouts* and *Post Selections* loading screen.\
Advanced Views, by default, reduces unused scripts to speed up the editor loading, and this may cause issues in some rare cases.\
Visit the **Settings > General** tab to turn on 'Optimize Layout and Post Selection admin screen performance'.
{% endhint %}

## List of supported Third-party Plugins

These plugins work well with Advanced Views.

[Filter Everything](https://wordpress.org/plugins/filter-everything/) - Product Filter & WordPress Filter

[ACF: Google Maps Field](https://wordpress.org/plugins/acf-google-map-field-multiple-markers/) (Multiple Markers)

[ACF OpenStreetMap Field](https://wordpress.org/plugins/acf-openstreetmap-field/)

[Advanced Custom Fields (ACF)](https://wordpress.org/plugins/advanced-custom-fields/) - Custom fields, post types and taxonomies.

[Meta Box](https://wordpress.org/plugins/meta-box/) - WordPress Custom Fields Framework

[Pods ](https://wordpress.org/plugins/pods/)- Custom Content Types and Fields

## Conflicts

Below we've listed known issues. If you have any compatibility issues please [contact us](https://advanced-views.com/support).

### 1. Hosting

Although the Advanced Views works well with any default hosting setup, some hosting providers may have some settings that they consider as default.

#### 1.1 ***Opcache*** with an option to remove comments

Websites hosted on a Linux server with the *opcache* php module enabled, with the setting to remove comments from code (which is not default behavior) will experience issues with the *Layout* and/or *Post Selection* user interface.

#### How to fix it

Contact you hosting provider and ask support to disable this option on your account. 

OR

Do it yourself by opening your ***php.ini*** file and modifying the line with *opcache.save\_comments* changing the value to "**1**".

### 2. Security Plugins

If you're using a security plugin (like Wordfence, iThemes Security, etc.), it might interfere with Advanced Views in unexpected ways. As a troubleshooting step, temporarily disable the security plugin and check if the issue persists.

Common issues caused by security plugin settings include:

* ***Layouts***** or fields not saving** properly in the admin.
* **Field groups not appearing** or not loading as expected.
* **AJAX errors** when editing or previewing *layouts*.
* **PHP version warnings or blocked scripts** that don’t appear with the plugin disabled.

If disabling the plugin resolves the issue, review your security settings—particularly firewall rules, login protection, and script restrictions—and consider whitelisting the Advanced Views plugin or paths.

## FAQs

<details>

<summary>Why does this happen and why are comments in code critical?</summary>

Some libraries use comments to classes and class fields (PHPDoc) to keep meta information. A common example is [PHP Doctrine](https://www.doctrine-project.org/\).). Our plugin also relies on PHPDoc.

</details>