Skip to content

Support for plugin header "Requires Plugins" to simplify blueprints #110

Open

Description

@j-falk

Would be great if the blueprints library would support the newly introduced plugin header "Requires Plugins" that was introduced in WP 6.5 (https://make.wordpress.org/core/2024/03/05/introducing-plugin-dependencies-in-wordpress-6-5/).

This would then simplify the blueprints needed to create a WP install for a plugin that require other plugins to work. Eg as for the example mentioned in the blog post, https://wordpress.org/plugins/wpsso-wc-metadata/, you would only have to have a blueprint like:

{
  "preferredVersions": {
    "php": "8.0",
    "wp": "latest"
  },
  "phpExtensionBundles": [
    "kitchen-sink"
  ],
  "plugins": [
    "wpsso-wc-metadata"
  ],
  "steps": [
    {
      "step": "login",
      "username": "admin",
      "password": "password"
    }
  ]
}

instead of:

{
  "preferredVersions": {
    "php": "8.0",
    "wp": "latest"
  },
  "phpExtensionBundles": [
    "kitchen-sink"
  ],
  "plugins": [
    "woocommerce",
    "wpsso",
    "wpsso-wc-metadata"
  ],
  "steps": [
    {
      "step": "login",
      "username": "admin",
      "password": "password"
    }
  ]
}

Activity

  1. adamziel commented on Jul 1, 2024

    @adamziel
    Collaborator

    This does sound useful! I'm thinking the schema will need an explicit switch to turn this behavior on/off, even if only for development when you want to provide your own versions of the required plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions