-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using the Sandbox plugin on dev.newpathconsulting.com #358
Comments
this needs to be moved to playground-tools I just realized :) |
Thank you for reporting this! In my testing, it looks like the plugin is broken because of some changes Playground made to exporting. The ZIP file doesn't include WordPress files, only themes, plugins... To fix the plugin, we will need to rebuild the blueprint to work with the ZIP content. |
@adamziel this issue makes me wonder if we should even fix the plugin, or if we should remove it from WordPress.org until we can build a fully working version with the sync protocol. What do you think? |
@bgrgicak I wouldn't mind that, but I just saw this:
Let's keep the plugin in there, then, but replace the logic with a notice saying that it doesn't work at the moment, giving full context, and communicating we're going to be fixing it in short to medium term. I'm thinking of moving that codebase to the core Playground repo maybe two weeks from now to have a central place for incubating all the PHP libraries. |
I can do both, the fix takes a few minutes, but there should also be a notice that the plugin is broken. |
Getting this error when trying to use the Sandbox plugin on site dev.newpathconsulting.com
The text was updated successfully, but these errors were encountered: