CUNY Academic Commons

Oh man...bummer to hear this does not work with block editor.

I have a professor who was planning to have posts be private by default.

I thought other profs might be using the plugin in this way too but because we have not discovered it was broken in the block editor until now, I wonder how prevalent that use case really is.

I will manually change students posts for now (their first assignment is due soon) but not sure how to proceed otherwise. I can change the default text editor to Classic but that doesn't really resolve the issue.

I think having the option to set all posts to private by default is an important function and affordance for teaching contexts. And I think prof appreciate having this an an option (especially since this feature is the case in LMS platforms). But maybe this is something we should discuss at the group meeting to hear what others think about spending time on creating a more permanent fix.

I think having the option to set all posts to private by default is an important function and affordance for teaching contexts. And I think prof appreciate having this an an option (especially since this feature is the case in LMS platforms). But maybe this is something we should discuss at the group meeting to hear what others think about spending time on creating a more permanent fix.

Yes, I think it's worth more discussion. The obvious strategy is simply to make the entire site private. It's a very specific use case that requires a public site but for all student posts to be private. There's also a further discussion to be had about the broader utility of the "private" visibility level in WP - even I don't fully understand what the feature is meant to do.

I will add this to our agenda for next Friday's meeting. I am also curious about the intended use case or design here Laurie, if you know anything else about it. Are there other aspects of this site that should be public, and it's only the student posts that should be private? Are the student posts going to be public eventually? Is there any sense to a public site / private group (or vice versa?) setup?

HI All,

Collecting some thoughts here on the affordances offered by default private post, and it's utility beyond the default site visibility settings.

The obvious strategy is simply to make the entire site private.

This could work if the professor is okay with all students seeing one another's posts. However, we have there are instances in which professors do not want students seeing each others' writing all the time. One professor used default private posts as a way for students to keep private journals during the semester, and a few times throughout the semester the students changed the settings to post "publicly" to the whole course. The ability to facilitate private writing between professor and students is the most common use case, and may be more widely used than we know? (what are the plugin stats?) The most recent professor wanted students to write privately to hone their ideas, and then use the group space in google docs to engage collaborative writing and built out projects.

So in this use case above, making the course "private" does not necessarily allow the professor to do what they imagined. I'll also add that this plugin is, I think, the only mechanism the Commons offers for private assignment submission through a site (or group?).

It's a very specific use case that requires a public site but for all student posts to be private

This is actually very common now with folks teaching OER courses on the Commons. Many of the OER faculty programming requires the creation of an "open" aka public course, with openly licensed public materials. In best case scenarios, faculty host content on the commons but also involve students on the Commons. In these cases, many faculty set the site visibility to public and create a password protected page for the blog posts.

Thanks for this, Laurie. In part this helps me to understand what "Private" means: visible only to the author and to the site's administrators. In my opinion this is not very clear in WordPress itself. But it does seem like a useful feature in the situations you describe.

Let's discuss this at our Friday meeting. But from the development point of view, it's not worth a ton of debate. It's not a huge technical lift to make a version of private-by-default that works with the block editor. So if there's general agreement that the workflows that Laurie describes are ones that we want to support and encourage, then let's go ahead and build it.

We went over the background and pedagogical use cases here (thanks for laying them out, Laurie!) during the monthly meeting today and decided to move ahead with the manageable task of building the feature for a post that is private to only the author and site administrators.

I'm adding some watchers here so we can track development and update documentation as needed when this is ready.

When you think something is going to be easy... :)

It is effectively an intentional design decision to privately publish posts as soon as the private visibility option is selected. This must all be due to the block editor's immediate reaction to state change in the UI. "Draft", "Private", and "Publish" are all post status settings. There is no actual equivalent for "Draft + Private".

In the classic editor, state was really only changed when everything was sent to PHP. The old Private Post Default plugin took advantage of this by wrangling the UI every time the page loaded to make things appear as if they were "new + private" rather than published.

In the block editor, as soon as JS is used to set the status to private, it is immediately published.

So. I think the answer gets a little more complicated.

I'm starting to think of an additional field in the sidebar that is an override of sorts for the published state: public or private. Then, a pre-publish checklist item that describes what will happen: "This post will be published privately."

I think we can chat through expectations a bit during tomorrow's call.

Going through a couple of backlog tickets to see what we might pick up over the summer. Is this one that's pretty close to the finish line and worth a bit more time to complete?