You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @evrpress, thanks for this. I can confirm. I checked, and I can see wp-now is loading wp-playground/blueprints 1.0.2. Upgrading to 1.0.14 will probably automatically fix this. Now the required elements are ["pluginData", "step"].
@evrpress you may have more luck with @wp-playground/cli. @wp-now is not actively maintained and upgrading the Playground libraries is a real challenge. I'd love to merge it into @wp-playground/cli and only maintain a single too. To do that, we'd need to port the context detection logic (as in – are we in a plugin directory? Or a theme directory? Or wp-content? etc.) into @wp-playground/cli
I try to run a local blueprint with this command:
and get the error
Here's my blueprint:
Playground link
Switching the
pluginData
property to the deprecatedpluginZipFile
will work, but it breaks my blueprint on the playground.The text was updated successfully, but these errors were encountered: