AdvancedCustomFields / AdvancedCustomFields/acf
ACF needs to update the updater to take advantage of auto-updates
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 945
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
For reference / context see this ticket: https://core.trac.wordpress.org/ticket/50280 with WP 5.5 auto-updates will be a new feature. In order for the "enable auto-updates" link to show, the no_updates array in the update transient needs to be populated with data. Currently ACF only populates the response array when there is a new version, and does nothing when there is not a new version.
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 updater code that populates the update transient, then read WordPress ticket 50280 for the expected auto-update data. Verify how ACF handles both available and current versions, including the no_updates array. Done means WordPress 5.5 can display the enable auto-updates link when appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100