Skip to content
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

introduce blueprint.json for plugin preview #289

Merged
merged 1 commit into from
Mar 24, 2024
Merged

Conversation

stklcode
Copy link
Contributor

Add a blueprint.json to run WordPress in Playground with Statify installed.

Ref.: https://developer.wordpress.org/plugins/wordpress-org/previews-and-blueprints/

@stklcode stklcode self-assigned this Mar 24, 2024
@Zodiac1978
Copy link
Member

Zodiac1978 commented Mar 24, 2024

If I am correct, it is not necessary to install the plugin on WordPress.org. This is only needed, if you are coming from the outside. On wp.org this happens automatically.

See this working example from ASB:
https://github.com/pluginkollektiv/antispam-bee/blob/master/.wordpress-org/blueprints/blueprint.json

Copy link

sonarcloud bot commented Mar 24, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@stklcode
Copy link
Contributor Author

Hm I see it's working for ASB, so I assume it will do the job for Statify as well.

I tested the blueprint locally with wp-now, this seems to require explicit plugin setup to do anything useful. Seems implementations have some differences.

I just pushed another blueprint for Statify Filter (https://wordpress.org/plugins/statify-blacklist/) with installation steps. Think it is necessary there, because the plugin has a dependency to Statify and WP < 6.5 does not support dependencies out of the box. (and I have no idea if the playground supports it in 6.5)

Copy link
Member

@Zodiac1978 Zodiac1978 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@stklcode stklcode merged commit c0b8077 into develop Mar 24, 2024
19 checks passed
@stklcode stklcode deleted the feature/blueprint branch March 24, 2024 17:26
@stklcode stklcode added this to the 2.0.0 milestone Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants