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.

Sign up for GitHub

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

Jump to bottom

[Tracking] WordPress.org readiness #183

Closed
3 tasks done
adamziel opened this issue Mar 28, 2023 · 4 comments
Closed
3 tasks done

[Tracking] WordPress.org readiness #183

adamziel opened this issue Mar 28, 2023 · 4 comments
Labels
[Type] Tracking Tactical breakdown of efforts across the codebase and/or tied to Overview issues.

Comments

@adamziel
Copy link
Collaborator

adamziel commented Mar 28, 2023 •
edited
Loading

This issue tracks the pre-requisites to using WordPress Playground as an official WordPress demo on wordpress.org. I'm not declaring this will happen. I simply want to ensure there are no blockers if it were to happen:
@adamziel adamziel added [Feature] WordPress Previewer [Type] Tracking Tactical breakdown of efforts across the codebase and/or tied to Overview issues. labels Mar 28, 2023
@adamziel adamziel mentioned this issue Apr 13, 2023
Closed
@adamziel
Copy link
Collaborator Author

Specific to previewing plugins:

We could run some async tests, and flag ones that don’t work in the directory pre user interaction. We run similar jobs for themes & block plugins. That would require us to know what to look for though. Its fine, we can just improve warning/error messaging for now. Over time, provided we can eliminate most issues.

We could include a mu-plugin in the package that will filter certain hooks and help make it obvious if a plugin/theme doesn’t work. Trigger a specific message on network requests, direct SQL queries, SQL errors, stuff like that.

@adamziel
Copy link
Collaborator Author

adamziel commented Jun 1, 2023

For third-party cookies, Playground will just need to be hosted on <subdomain>.wordpress.org, see #87. I don't think there's any other way to solve it – Chrome is pretty good with blocking all features that could be used in lieu of cookies.

@adamziel
Copy link
Collaborator Author

adamziel commented Jun 1, 2023

There are no more blockers on WordPress Playground's end! 🎉

@adamziel adamziel mentioned this issue Jun 5, 2023
Open
@adamziel
Copy link
Collaborator Author

With WordPress Beta support this issue is now solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Type] Tracking Tactical breakdown of efforts across the codebase and/or tied to Overview issues.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adamziel