AdvancedCustomFields / AdvancedCustomFields/acf

Is there any way to disable the wp_kses filter for acf fields?

Open
#622 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
945
Forks
197
PR merge metrics
No merged PRs in 30d

Description

Hey all, I have message fields that are outputting alpinejs components which depend on a ton of custom attributes. I have having trouble getting them allowed within wp_kses_allowed_html and there are a ton of them so is there a way to disable the filter? In the past there was a constant we could use to enable the experimental feature. Is there something similar now to disable it?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by tracing how ACF fields pass through wp_kses_allowed_html and review the existing handling of custom HTML attributes; determine whether a supported opt-out is intended and define the expected behavior for Alpine.js attributes.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.