Lock Thread Option For Message Boards

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1.2, 5.2.3, 6.0.0 Preview
• Fix Version/s: 6.0.0 Preview
• Component/s: Collaboration > Message Boards
• Labels: None
• Branch Version/s:
  5.2.x
• Backported to Branch:
  Committed
• Similar Issues: Show 5 results ; ;

  LPS-6902	Can not lock threads in home page of Message Boards
  LPS-6727	"Lock Thread"link lacks icon in Message Boards
  LPS-9581	Locked threads in message boards are automatically unlocked when the app. server is restarted
  LPS-31681	Locked message boards messages may load forever with akismet portlet
  LPS-17359	Added option to set threads as questions by default in the Message Boards

Many message boards and forums have the option of locking specific threads once the thread has been answered or presumed dead. It will help so moderators will be able to lock threads so users are not allowed to revive dead threads from the legacy archives or threads from 3-4 years ago.

[Lisa Simpson]

I'm good with this. I think it's an excellent idea. it fits nicely with the prune threads request that's in the wiki.

[Brian Chan]

Hey Mika,

Can you reimplement it using the Lock service? See document library. Thanks.

[Brian Chan]

Very close, a few changes:

1.) Checking of locks should only be done in the *Service tier (and not in the *LocalService tier). It's in a sense, something like a permission check. If somene wants to call the *LocalService, it should just work.

2.) No need for ThreadLockedException, let's reuse the one that the Lock service already throws.

3.) Let's also make MBThreadImpl have the same lock methods that DLFileEntryImpl now has (that Alex added in rev 42844).

Thanks Mika.

[Mika Koivisto]

1) Moved the lock checks to ServiceImpl from LocalServiceImpl

2) ThreadLockedException is needed because Lock Service does not throw any appropriate exception

3) Added the other methods too even though they are not used anywhere.