RolePlay onLine RPoL Logo

, welcome to RPoL Development

09:49, 19th April 2024 (GMT+0)

Decoupling marking a thread a notice from closing it.

Posted by Pat
Pat
member, 118 posts
Sat 30 Jul 2016
at 20:24
  • msg #1

Decoupling marking a thread a notice from closing it

When I create a new thread as a GM and mark it as a Notice, it is automatically closed when I post it. If I want it open, it takes a separate "edit thread" operation.

Since there are separate tick-boxes for "Notice" and "Closed" when creating a thread, I don't see any advantage. Is this a legacy behavior? Can it be changed?

Thanks!
bigbadron
moderator, 15131 posts
He's big, he's bad,
but mostly he's Ron.
Sat 30 Jul 2016
at 20:34

Decoupling marking a thread a notice from closing it

The separate tick boxes are so that you can close a thread that is no longer used, without making it a Notice.  You can also edit a thread to make it a Notice, without closing it.

The reason that a thread that's created as a Notice is automatically closed is that that was the behaviour that people requested.  Most people creating a Notice wanted it closed as well, so that other people could not reply there.

The main purpose of Notices is to provide information which doesn't change much.  Note that GMs can still post to a closed thread.
Pat
member, 119 posts
Sat 30 Jul 2016
at 21:25
  • msg #3

Decoupling marking a thread a notice from closing it

I understand that, but it seems with separate tick boxes the people who want their notices closed could do so easily without a separate step.

But so be it. Thanks.
This message was last edited by the user at 21:26, Sat 30 July 2016.
Sign In