Skip to content

blueprint causing an error, syntax is correct #2057

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

Closed
asirota opened this issue Dec 4, 2024 · 4 comments
Closed

blueprint causing an error, syntax is correct #2057

asirota opened this issue Dec 4, 2024 · 4 comments

Comments

@asirota
Copy link

asirota commented Dec 4, 2024

This blueprint is causing an error on Safari (Mac)

[04-Dec-2024 19:35:41 UTC] JavaScript Error: PHP.run() failed with exit code 255 and the following output: 
PHPExecutionFailureError@https://playground.wordpress.net/worker-thread-bf1795ed.js:38:437
@https://playground.wordpress.net/worker-thread-bf1795ed.js:53:1916
[04-Dec-2024 19:35:41 UTC] JavaScript Error: Error when executing the blueprint step #5 ({"step":"installTheme","themeData":{"resource":"wordpress.org/themes","slug":"generatepress"}}) : PHP.run() failed with exit code 255 and the following output: 
@https://playground.wordpress.net/assets/config-2770b453.js:750:145943
[04-Dec-2024 19:35:41 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function mysqli_report() in /wordpress/wp-includes/class-wpdb.php:3
Stack trace:
#0 /wordpress/wp-includes/class-wpdb.php(3): wpdb->db_connect()
#1 /wordpress/wp-includes/load.php(2): wpdb->__construct('username_here', 'password_here', 'database_name_h...', 'localhost')
#2 /wordpress/wp-settings.php(2): require_WordPre
#3 /wordpress/wp-config.php(102): require_once('/wordpress/wp-s...')
#4 /wordpress/wp-load.php(2): require_once('/wordpress/wp-c...')
#5 /internal/eval.php(3): require_once('/wordpress/wp-l...')
#6 {main}
  thrown in /wordpress/wp-includes/class-wpdb.php on line 3

The syntax is correct and has been working for weeks. Test here

@asirota
Copy link
Author

asirota commented Dec 4, 2024

On Chrome (Mac) we get this instead:

[04-Dec-2024 19:39:19 UTC] PHP Fatal: PHP.run() failed with exit code 255 and the following output:  Error: PHP.run() failed with exit code 255 and the following output: 
    at PHP.run (https://playground.wordpress.net/worker-thread-bf1795ed.js:53:1888)
    at async PlaygroundWorkerEndpoint.run (https://playground.wordpress.net/worker-thread-bf1795ed.js:4:9449)
[04-Dec-2024 19:39:19 UTC] JavaScript Error: PHP.run() failed with exit code 255 and the following output: 
Error: PHP.run() failed with exit code 255 and the following output: 
    at PHP.run (https://playground.wordpress.net/worker-thread-bf1795ed.js:53:1888)
    at async PlaygroundWorkerEndpoint.run (https://playground.wordpress.net/worker-thread-bf1795ed.js:4:9449)
[04-Dec-2024 19:39:19 UTC] JavaScript Error: Error when executing the blueprint step #5 ({"step":"installTheme","themeData":{"resource":"wordpress.org/themes","slug":"generatepress"}}) : PHP.run() failed with exit code 255 and the following output: 
Error: Error when executing the blueprint step #5 ({"step":"installTheme","themeData":{"resource":"wordpress.org/themes","slug":"generatepress"}}) : PHP.run() failed with exit code 255 and the following output: 
    at Object.run (https://playground.wordpress.net/assets/config-2770b453.js:750:145934)
    at async gu (https://playground.wordpress.net/assets/config-2770b453.js:750:147453)
    at async Qu (https://playground.wordpress.net/assets/config-2770b453.js:754:16954)
    at async https://playground.wordpress.net/assets/main-60d2aed2.js:151:2458

@bgrgicak
Copy link
Collaborator

bgrgicak commented Dec 5, 2024

@asirota the error message is hard to understand, but the root cause is in Query monitor which isn't supported in Playground.

Your Blueprint should work if you remove Query monitor from the plugin list.

I will close this issue as we are already using #1990 to track Query monitor support, but please feel free to comment if you have any more questions.

@bgrgicak bgrgicak closed this as completed Dec 5, 2024
@github-project-automation github-project-automation bot moved this from Inbox to Done in Playground Board Dec 5, 2024
@asirota
Copy link
Author

asirota commented Dec 5, 2024

@bgrgicak thank you so much for your insight. It was running before but I guess causing issues with more recent changes. I really appreciate WordPress Playgrounds!

asirota added a commit to NewPath-Consulting/Wild-Apricot-Press that referenced this issue Dec 5, 2024
Query monitor plugin  is incompatible with WordPress Playground. This may be fixed in the future but for now it breaks WordPress Playground.

WordPress/wordpress-playground#2057 (comment)
@asirota
Copy link
Author

asirota commented Dec 5, 2024

Yup that fixed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants