WordPress / WordPress/wp-consent-level-api
Update plugin structure to self-disable after core-merge
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 92
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 7
Description
Saw this on another feature plugin repo and figured I'd ensure we're meeting this requirement.
One requirement for WordPress Core feature plugins is that they need to "self-disable" after they are merged to core.
An easy way to do that is when the plugin's base-file (wp-autoupdates.php) has only the plugin's headers and a check whether the plugin has been merged, and all the functionality/code is in another file that gets included. For example the Lazy Loading Feature Plugin was recently restructured to include a functions.php file for that reason.
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 plugin's current base file and compare its structure with the wp-autoupdates.php and functions.php pattern described in the issue and linked original post. Confirm that the base file can self-disable after core merge while the remaining functionality stays in the included file; done means the plugin follows that separation and preserves its existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100