Error when blueprint includes themeInstall step for latest WordPress default theme

[ndiego]

If your blueprint includes a step for themeInstall that includes the latest WordPress theme, which is currently TT4, you get an error because the theme is already installed. Also, if there are steps following the themeInstall step, they won't get triggered due to the error.

Here's an example blueprint.

{
    "$schema": "https://playground.wordpress.net/blueprint-schema.json",
    "features": {
        "networking": true
    },
    "steps": [
        {
            "step": "login"
        },
        {
            "step": "installTheme",
            "themeZipFile": {
                "resource": "wordpress.org\/themes",
                "slug": "twentytwentyfour"
            }
        }
    ]
}

And here's the resulting error.

Perhaps if there's a step that installs a theme or plugin that already exists by default in Playground, the step is ignored.

[adamziel]

Good point @ndiego! I think the step should still execute because the theme might have a newer version than the bundled one. Removing the bundled theme and logging a console.warning could be a good solution.

In the meantime, you could use this as a workaround:

{
  "$schema": "https://playground.wordpress.net/blueprint-schema.json",
  "features": {
    "networking": true
  },
  "steps": [
    {
      "step": "login"
    },
    {
      "step": "rmdir",
      "path": "/wordpress/wp-content/themes/twentytwentyfour"
    },
    {
      "step": "installTheme",
      "themeZipFile": {
        "resource": "wordpress.org/themes",
        "slug": "twentytwentyfour"
      }
    }
  ]
}

[ndiego]

I think the step should still execute because the theme might have a newer version than the bundled one. Removing the bundled theme and logging a console.warning could be a good solution.

Yeah great point!