AdvancedCustomFields / AdvancedCustomFields/acf
Please keep supporting classic WordPress versions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
Currently working on a non-blocky version of WordPress (WP CMS), which doesn't contain block-related functions. There also is ClassicPress.
This issue is just to gently ask for your support by conditionally checking if the plugin is running on a "blocky" version of WP.
Not asking to readapt the plugin to use different functions or anything alike. Just saying: "please load all block related features conditionally, ONLY if it's a blocky WP version, maybe by doing if(function_exists('parse_blocks')){ ... load blocky features ... }"
That way the plugin will keep working fine on WP-CMS and ClassicPress.
This is a fundamental plugin for the WP ecosystem, please don't leave non-blocky people behind.
Thanks.
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 by locating the plugin's block-related features and the entry points where they are loaded; the issue suggests using parse_blocks as the compatibility check. Confirm the plugin still works on WordPress versions without block-related functions, including WP-CMS and ClassicPress, without changing non-block functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100