Way to make part of the post visible to author and staff only?

[pfaffman (Jay Pfaffman)]

@Infi

However, it assumes users know how to use the whisper feature

But whispers are available only to staff, and you need the author of the post to be able to see it. And it could be any post, right? (Maybe any post in a certain category).

@Infi

was visible only for staff members and author of the post.

A plugin could add a custom field that’s added to the serializer only for the post owner and staff. Then you’d have both of those separate posts in one place, at least.

If what you really want is a [HIDE] BBCode, then . . . no. The raw post is still visible to everyone who can see the post. It might be possible to encrypt the hidden text in the raw post and then somehow contrive to decript it when an admin or the owner sees it. Seems tricky, though. Or maybe you’d just dupe the whole raw post when it’s saved and then do something to use it when you edit or display the text for the owner.

[putty (Derek Putnam)]

@pfaffman

whispers are available only to staff

Slight correction, you can now specify groups beyond staff.

@Discourse

Enabling whispers

Before whispers can be used, an administrator needs to enable them:

1. Go to your site settings
2. Find the whispers allowed groups setting
3. Add the groups you want to allow to use whispers

[pfaffman (Jay Pfaffman)]

Sorry, I meant “whispers are available only to people who can see whispers”

@Infi

we used [HIDE] BBCode, which allowed to hide part of the post so it was visible only for staff members and author of the post.

The hidden text needs to be visible only to the author of the post and staff. If you add everyone who has hidden text to the whisper group (essentially every user), they’ll be able to see all of the whispers, not just their own. The point of whispers is that the person you’re whispering about can’t hear it, but in this case, they need to be able to create and see the whisper that only they and staff can see.

[Infi]

But whispers are available only to staff, and you need the author of the post to be able to see it. And it could be any post, right? (Maybe any post in a certain category).

Yes, I need the author and members of the staff to be able to see the post. Those will be posts from one specific forum category.

[Heliosurge (Dan DeMontmorency)]

@Infi

I see, but it will still require making two topics: one visible to everyone (which describes the character’s appearance) and one private (with the character’s history and other characteristics that aren’t available at first glance). Like I said, I wouldn’t like to make an already extensive process of creating a character more complicated. Using [HIDE] BBCode back in the day was much easier and intuitive

ATM for a [hide Bbcode] you may need to consider sponsoring a Theme component as not likely need any real strong security or a more complete Plugin as with a plugin it is more secure as the modifications are done on the server side vs browser/client side.

Otherwise it would still need 2 topics of sorts. Both methods would leave the Plugin “Discourse Signatures”

A personal message. Then have them create a link to the PM and paste it in a Signature on their profile. For added benefit for naming use the [Character Name]_(Link to pm)

The other option would need the Private topics plugin. But otherwise the same as above

With the link published in a signature either party the player or game master(s) could access the linked pm/topic.

Persinal messages can work but would require all game masters or game master group invited to pm.

[pfaffman (Jay Pfaffman)]

Oooh! A custom user field visible only to the user (and staff) would let a theme component do it.

Is it the case that there are multiple games (each would get it’s own user custom field) and that you’d want that visible in every post that user made in a certain category? If so, a theme component could add a button or something to show the user field when it was needed as well as link to the profile to edit it.