AdvancedCustomFields / AdvancedCustomFields/acf
[ACF PRO 5.7.0-beta1] "acf.get_fields is not a function"
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
While running acf_form on the frontend:
VM2581 input.js:484 Uncaught TypeError: acf.get_fields is not a function
at VM2581 input.js:484
at _runHook (VM2576 acf-input.js:2299)
at Object.doAction (VM2576 acf-input.js:2125)
at Object.acf.doAction (VM2576 acf-input.js:819)
at HTMLDocument.<anonymous> (VM2576 acf-input.js:2045)
at i (VM2555 jquery-1.12.4.min.js:2)
at Object.fireWith [as resolveWith] (VM2555 jquery-1.12.4.min.js:2)
at Function.ready (VM2555 jquery-1.12.4.min.js:2)
at HTMLDocument.K (VM2555 jquery-1.12.4.min.js:2)
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
Reproduce the error while running acf_form on the frontend, then inspect the reported input.js location and the acf-input.js hook path in the stack trace. Trace why acf.get_fields is unavailable during that action and verify that the frontend form no longer raises this TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100