Wordpress.org playground files altered and not working

[vyskoczilova]

Prerequisites

• I have carried out troubleshooting steps and I believe I have found a bug.
• I have searched for similar bugs in both open and closed issues and cannot find a duplicate.

Describe the bug

Hi!
I've been early adopter of playground demos in wordpress.org. Here, if you click on "Live demo"https://wordpress.org/plugins/woocommerce-pay-for-payment/ you will find out that it does not work.

I don't know why, but when I updated it, it was working.

I've noticed several issues:

• my blueprint.json doesn't contain step installing the plugin, since it's in the bundle already https://plugins.svn.wordpress.org/woocommerce-pay-for-payment/assets/blueprints/ But the one that is loaded on the playground it does:

Expected behavior

I expect playgrounds used on wordpress.org backwards compatible, or that I get an automated message they are not and what I should change, since the plugins are free, I maintain them, but it's hard for me to go and check some additional functionality regulary.

Actual behavior

• blueprint.json used for wordpress.org preview is manipulated from my own
• not backwards compatible and error is not clear

Steps to reproduce

1. click on "Live demo"https://wordpress.org/plugins/woocommerce-pay-for-payment/ you will find out that it does not work
2. check the plugin's blueprint.json and compare with loaded ones

Isolating the problem

• I have deactivated other plugins and confirmed this bug occurs when only this plugin is active.
• This bug happens with a default WordPress theme active.
• I can reproduce this bug consistently using the steps above.

[adamziel]

@vyskoczilova thank you so much for reporting this! Just to confirm:

I expect playgrounds used on wordpress.org backwards compatible

They are supposed to be backwards compatible. A change in the Blueprints implementation should never require you to revisit your existing Blueprint. In this particular case, the problem seems to come from the sqlite-database-integration plugin. It got a big upgrade recently and now it requires some additional database tables. Your Blueprint imports wp-content from a zip file at https://kybernaut.cz/blueprints/pay-for-payment-playground.zip, which includes a database file in a format from before those changes. The SQLite integration plugin is supposed to be backwards compatible and support older databases, but it seems like something goes wrong in this specific scenario. @JanJakes would you be able to investigate what goes wrong in the plugin, add a test for that case, and deploy a fix to make sure the newer version continues to support all the existing database files?

That being said, adding this step to your Blueprint seems to fix the problem – it enables the older SQLite database driver. Feel free to apply it to your Blueprint if you'd rather fix the demo without waiting for the SQLite-database-integration patch:

{
	"landingPage": "/",
	"preferredVersions": {
		"php": "8.0",
		"wp": "latest"
	},
	"phpExtensionBundles": ["kitchen-sink"],
	"features": {
		"networking": true
	},
	"steps": [
+ 		{
+ 			"step": "defineWpConfigConsts",
+ 			"consts": {
+ 				"WP_SQLITE_AST_DRIVER": false
+ 			}
+ 		},
		{
            "step": "installTheme",
            "themeData": {
                "resource": "wordpress.org/themes",
                "slug": "twentytwentyfour"
            }
        },
		{
			"step": "importWordPressFiles",
			"wordPressFilesZip": {
				"resource": "url",
				"url": "https://kybernaut.cz/blueprints/pay-for-payment-playground.zip"
			}
		},
		{
			"step": "login",
			"username": "admin",
			"password": "password"
		}
	]
}

As a side-note, your Blueprint ships an older database file and still request the latest WordPress version. It works today, but it's slightly risky in that a WordPress release in the future may introduce a database schema change and will prompt the user to go through the WordPress upgrade flow before displaying the demo. A safer way would involve setting up the site using a wxr file or an sql file – although I understand it requires far more work than just shipping a database. We need better developer tools for setting up those demos for sure.