WC Post Types, Blocks: Add support for private speakers & sessions #994
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #717 — This is a simpler approach to the issue described, where it's difficult to style the speakers & sessions without making them public. By enabling private sessions & speakers to be used in blocks, this lets organizers (who have permissions to see private content) view and edit the content, without showing sessions & speakers to site visitors, and without notifying the wporg profiles code.
The intention to only show private sessions and not all sessions is that all sessions are submitted as drafts, so this lets the organizer team update and privately publish the accepted talks, while leaving the rest alone.
Screenshots
Private speakers now show up in the sessions list table, with updated label.
Private sessions appear in the Speaker Sessions block, which can be used on speaker posts.
And the main use for this, private sessions will show up in the schedule. In the following screenshot, the "Friday keynote" is a privately published regular session (the rest are public custom sessions).
How to test the changes in this Pull Request: