WordPress / WordPress/secure-custom-fields
Getting "Uncaught ReferenceError: acf is not defined" error on ClassicPress
Open
Nobody has claimed this yet.
[Type] Enhancement
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
Tried installing SCF 6.8.0 on a fresh ClassicPress 2.6.0 installation and it's giving Uncaught ReferenceError: acf is not defined error in console.
This error is causing several issues in field and post creation/editing. Downgrading SCF to version 6.4.2 resolves it.
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 issue on a fresh ClassicPress 2.6.0 installation with SCF 6.8.0, then inspect the console error during field or post creation and editing. Compare the behavior with SCF 6.4.2; the work is done when those workflows operate without the “acf is not defined” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100