> 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/debugging.md).

# Debugging in Advanced Views

Advanced Views plugin follows WordPress standards and best practices. If you encounter an issue, the first step is to narrow down the cause and exclude configuration or environment-related problems.

## 1. Debugging tips

Before contacting support, try the following:

1. **Enable Development Mode**\
   Go to **Advanced Views → Settings** and enable **Development Mode** to display more detailed error messages.
2. **Check the Error Logs**\
   Open **Advanced Views → Tools**, switch to the **Debugging** tab, and review the **Error Logs** field. If any errors are listed, investigate them or use an AI assistant to help determine whether they originate from another plugin or your theme.
3. **Flush the Cache**\
   Open **Advanced Views → Tools**, switch to the **Debugging** tab, enable the **Flush Cache** option, and click the form's submit button.

If the issue persists, generate a **Debug Dump** before contacting support.

## 2. Creating a Debug Dump

A **Debug Dump** collects diagnostic information about your WordPress environment, including error logs. It can also include selected ***Layouts*** and ***Post Selections***, helping us investigate and resolve issues more efficiently.

{% hint style="success" %}
The Debug Dump includes only plugin-related info and does **not** contain any sensitive information, such as passwords or personal user data.
{% endhint %}

To generate a Debug Dump:

1. Go to **Advanced Views → Settings**.
2. On the **General** tab, enable **Development Mode** and click **Save Changes**.
3. Reproduce the issue so that relevant diagnostic information is recorded.
4. Go to **Advanced Views → Tools** and open the **Debugging** tab.
5. Scroll to the bottom of the page and enable **Generate Debug Dump**.
6. Click **Process** to generate and download the report.

<figure><img src="/files/AU31uYmSi5CsZ3rHXizE" alt=""><figcaption></figcaption></figure>

## 3. Potential compatibility issues

Advanced Views requires no special configuration and is compatible with WordPress themes and plugins that follow WordPress coding standards.

In some cases, however, non-standard hosting environments or aggressive security configurations can interfere with the plugin's functionality.&#x20;

### 3.1) Hosting-related issues

Although Advanced Views works with standard hosting configurations, some hosting providers enable non-default PHP settings that may cause compatibility issues.

#### OPcache Removing Comments

{% hint style="warning" %}
Many PHP libraries use comments on classes and class fields (PHPDoc) to keep metadata, e.g., [PHP Doctrine](https://www.doctrine-project.org/\).). Advanced Views also relies on PHPDoc, and automatic comment removal affects the plugin functionality.
{% endhint %}

On Linux servers with the PHP **OPcache** extension enabled, the `opcache.save_comments` setting must remain enabled. If comments are stripped from PHP code (a non-default configuration), the ***Layout*** and ***Post Selection*** interfaces will not function correctly.

**How to Fix It**

You can resolve this issue in one of the following ways:

* Contact your hosting provider and ask them to enable PHP comments by setting `opcache.save_comments=1` for your account.
* If you manage your own server, edit your `php.ini` file and set:

```
opcache.save_comments=1
```

After making the change, restart PHP or your web server if required.

### 3.2) Security-plugin related issues

Security plugins such as **Wordfence,** **iThemes Security**, and similar solutions sometimes interfere with many plugins, including Advanced Views.&#x20;

As a troubleshooting step, temporarily disable the security plugin and check whether the issue persists.

Common symptoms include:

* *Layouts* or fields failing to save.
* Field groups not appearing or loading correctly.
* AJAX errors while editing or previewing *Layouts*.
* PHP warnings or blocked scripts that disappear when the security plugin is disabled.

If disabling the security plugin resolves the issue, review its configuration—particularly firewall rules, script restrictions, and request filtering. You may need to whitelist Advanced Views or its admin URLs to prevent the plugin from being blocked.