Skip to content

Update plugin structure to self-disable after core-merge #49

@garretthyder

Description

@garretthyder

Saw this on another feature plugin repo and figured I'd ensure we're meeting this requirement.

Original Post

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions