Page not created on plugin activation

[faisal-alvi]

We are using the playground to show the preview of our Publisher Media Kit plugin.

The plugin creates a page on activation, but while using it in the playground, it does not work, and we have to import the Media Kit page from a test import file. The plugin is supposed to create this itself on activation, but it seems that the activation process that happens when the Playground is initialized doesn't trigger that functionality. This seems to be an issue with the playground.

The code when a plugin creates a page on activation is here:

• Code snippet 1
• Code snippet 2

Related PR: 10up/publisher-media-kit#175

[dmsnell]

@faisal-alvi are you using a blueprint to install the plugin? IIRC the plugins are installed as mu-plugins and don't run their activation hooks. There's an activatePlugin Blueprint step that should do that though, so you might check your configuration to make sure it's doing that.

[dkotter]

We currently are using the installPlugin step with the activate option set to true:

{
	"step": "installPlugin",
	"pluginZipFile": {
		"resource": "wordpress.org\/plugins",
		"slug": "publisher-media-kit"
	},
	"options": {
		"activate": true
	}
}

I tried changing this to use activatePlugin as well but that also didn't work:

{
	"step": "installPlugin",
	"pluginZipFile": {
		"resource": "wordpress.org\/plugins",
		"slug": "publisher-media-kit"
	},
	"options": {
		"activate": false
	}
},
{
	"step": "activatePlugin",
	"pluginName": "Publisher Media Kit",
	"pluginPath": "/wordpress/wp-content/plugins/publisher-media-kit"
}

[dkotter]

And I guess to be more clear, it doesn't appear in either case it's getting installed as an mu-plugin, at least not showing up in the mu-plugins directory or in the Must-Use section on the plugins page

[dmsnell]

@dkotter thanks for double-checking that. in review, I noticed that the test import file is listed in the Blueprint steps after the plugin install and activation. I rearranged those so that the import file appears first, and it appears as though the Media Kit demo content was imported.

{
  "$schema": "https://playground.wordpress.net/blueprint-schema.json",
  "landingPage": "/wp-admin/post.php?post=7&action=edit",
  "preferredVersions": {
    "php": "7.4",
    "wp": "latest"
  },
  "phpExtensionBundles": [
    "kitchen-sink"
  ],
  "steps": [
    {
      "step": "login",
      "username": "admin",
      "password": "password"
    },
    {
      "step": "importFile",
      "file": {
        "resource": "url",
        "url": "https://raw.githubusercontent.com/10up/publisher-media-kit/65a081ba5d9f03270873d96baf7189d20fafcd7c/.wordpress-org/blueprints/demo-data.xml"
      }
    },
    {
      "step": "installPlugin",
      "pluginZipFile": {
        "resource": "wordpress.org/plugins",
        "slug": "publisher-media-kit"
      },
      "options": {
        "activate": true
      }
    }
  ]
}

https://playground.wordpress.net/#{"$schema":"https://playground.wordpress.net/blueprint-schema.json","landingPage":"/wp-admin/post.php?post=7&action=edit","preferredVersions":{"php":"7.4","wp":"latest"},"phpExtensionBundles":["kitchen-sink"],"steps":[{"step":"login","username":"admin","password":"password"},{"step":"importFile","file":{"resource":"url","url":"https://raw.githubusercontent.com/10up/publisher-media-kit/65a081ba5d9f03270873d96baf7189d20fafcd7c/.wordpress-org/blueprints/demo-data.xml"}},{"step":"installPlugin","pluginZipFile":{"resource":"wordpress.org/plugins","slug":"publisher-media-kit"},"options":{"activate":true}}]}

[dkotter]

Thanks for the response.

That import File step shouldn't even be needed. I added it because the Media Kit page which the plugin automatically creates on plugin activation was not being created. So instead I exported that page and we import it. So it shouldn't matter if that step runs before or after activation the problem is we have to use that step at all since it doesn't seem that activating the plugin through the blueprint actually triggers the normal activation code.

[adamziel]

Plugin activation runs without a "current user" which makes this check fail:

	if ( ! current_user_can( 'activate_plugins' ) ) {
		return;
	}

I have a fix incoming. Thank you for reporting!