> 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/features/workflow/template-validation.md).

# Automatic template validation

Advanced Views provides automatic template validation for both [*Layouts*](/advanced-views/getting-started/first-layout.md) and [*Post Selections*](/advanced-views/getting-started/first-post-selection.md).

Default templates are generated automatically and are always valid. Validation is primarily intended for **Custom Templates**, where template code is edited manually.

## 1. **Validation on save**

Whenever you save a *Layout* or *Post Selection*, Advanced Views validates it template before applying the changes. If validation fails, the template is not saved, and the detected errors are displayed so you can fix them.

## 2. Validation on Field Group changes

Whenever you modify a field group in a supported custom field provider (such as [ACF](/advanced-views/fields/meta-plugins/advanced-custom-fields.md) or [Meta Box](/advanced-views/fields/meta-plugins/meta-box-fields.md)), Advanced Views automatically checks all *Layouts* that use fields from that group.

For example, if you remove a field that is referenced in a *Layout* template, Advanced Views displays a notice with a link to edit the affected *Layout*, allowing you to update it immediately.

This helps ensure that all parts of your website continue to work correctly after field changes.

## 3. Bulk Validation

Both *Layouts* and *Post Selections* list screens include a **Bulk Validation** tab.

Clicking on it scans all items and validates their templates. Once the scan is complete, only items with validation errors are displayed, making it easy to identify and fix any issues across your project at any time.