Details

    • Branch Version/s:
      5.2.x
    • Backported to Branch:
      Committed
    • Similar Issues:
      Show 5 results 

      Description

      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.

        Issue Links

          Activity

          Hide
          Lisa Simpson added a comment - - Restricted to

          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.

          Show
          Lisa Simpson added a comment - - Restricted to 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.
          Hide
          Brian Chan added a comment - - Restricted to

          Hey Mika,

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

          Show
          Brian Chan added a comment - - Restricted to Hey Mika, Can you reimplement it using the Lock service? See document library. Thanks.
          Hide
          Brian Chan added a comment - - Restricted to

          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.

          Show
          Brian Chan added a comment - - Restricted to 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.
          Hide
          Mika Koivisto added a comment - - Restricted to

          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.

          Show
          Mika Koivisto added a comment - - Restricted to 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.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                5 years, 28 weeks, 6 days ago

                Development

                  Structure Helper Panel