AdvancedCustomFields / AdvancedCustomFields/acf
Unminified scripts have been removed
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
In ACF 6.?.?, ACF used to load unminified assets when SCRIPT_DEBUG was set to true.
Those assets have been removed, making it harder to see what's happening under the hood:
- bugs can sometimes be on your side and users can even provide valuable feedback, if they are able to debug
- make developer's life harder
Expected behavior
Please honor SCRIPT_DEBUG and put your unminified assets back 🙏
There's nothing to hide or obfuscate here.
Version Information:
- WordPress Version 6.6
- PHP Version 8.2
- ACF Version 6.3.11 Pro
Additional context
Add any other context about the problem here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked assets/build/js/acf-input.js file and inspect how ACF selects assets when WordPress SCRIPT_DEBUG is true. Trace the related asset-loading or build entry points mentioned by that behavior, then verify that unminified assets are available and selected in debug mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php, wordpress
- Domain
- build-system, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100