Extend ignore

  • App
    WoltLab Suite Core

    On my site, ignore makes it so from your perspective, the person you are ignoring does not exist.

    • You cannot see their threads
    • You cannot see their replies (comments) made on your threads
    • You cannot see their blogs
    • You cannot see their blog replies (comments) made on your blog
    • They cannot send you a PM (DM)

    I would very much like to see this applied to WBB 4.1 and feel its important. I should point out that it doesn't block people from replying, it just makes it so you do not see or get any notice of those replies.

  • +1! I thought the block feature did this ^^


    I thought so as well. But there seems to be a bit of talk about it here
    https://www.woltlab.com/forum/index.ph…?postID=1387361

    In truth I got a little worried when I discovered it read, 'block' and not ignore. I hadn't noticed it, because I rarely use such a feature.

    I run an uncensored site, so I can't very well let people freely block and deny people the freedom to reply to threads or blog post. So when it read, 'block' I did freak out a bit. I was worried it did exactly that. lol

    But I'm OK with the idea of people ignoring each other.

  • +1

    In communities without censorship or with annoying users this is very necessary to keep the peace in the forum.

    I want to extend two cases:

    • You cannot see their threads
    • You cannot see their replies (comments) made on your threads or other threads (You cannot see their posts).
    • You cannot see their blogs
    • You cannot see their blog replies (comments) made on your blog or other blogs (You cannot see their replies on blogs).
    • They cannot send you a PM (DM)

    Edited 3 times, last by Aethior (November 12, 2014 at 9:19 PM).

  • +1

    In communities without censorship or with annoying users this is very necessary to keep the peace in the forum.

    I want extend two cases:


    I thought that I had included that. I believe I did.

    But I will thank you for making it more clear. I wouldn't want anything be left to chance. :)

  • I thought that I had included that. I believe I did. But I will thank you for making it more clear. I wouldn't want anything be left to chance.

    I supposed it was your intention, but I wanted to clarify. You are doing a good job making many suggestions. ;)

  • sure rasty, but there was already a pretty big discussion about it in the WL forum. I just pointed out to Atlantis that @norse provided a solution for this issue.
    So even if woltlab would decide not to implement it into the core system one can still intervene.
    And @Atlantis if you ask nicely I bet @norse would provide you with a fix for the blog posts and blog comments as well..

    This instruction might be adjusted for the WBB4.1. I'm not sure but norse should be able to clarify.

  • sure rasty, but there was already a pretty big discussion about it in the WL forum. I just pointed out to Atlantis that @norse provided a solution for this issue.
    So even if woltlab would decide not to implement it into the core system one can still intervene.
    And @Atlantis if you ask nicely I bet @norse would provide you with a fix for the blog posts and blog comments as well..

    This instruction might be adjusted for the WBB4.1. I'm not sure but norse should be able to clarify.


    It really should be part of the core.

    • phpBB
    • vBulletin
    • FluxBB
    • NodeBB
    • SMF
    • XenForo
    • IP.Board

    And this list continues on and on. Ignore isn't something new or some sort of hype. It is standard. You'd be hard press to find any development that has not had it for the past 10 years. Because this is the norm. It is expected not only from an administrative point of view, but common newbies expect it as well.

    I was VERY surprised, even thrown back a little, to discover WBB does not have this. It is inconceivable. I mean it is second nature and just naturally expected. So I never even thought to look. It would be like not expecting to find the post button or smilie or report button.

  • it's used to be the case in WBB3 but woltlab changed it for whatever reason. And I think they had their reasoning to do so. But if there are many users requesting that feature it might come back into wbb4.1...not sure.. Let's be patient and wait what woltlab will say. We won't hear anything now. It's half past 4 in the middle of the night in Germany :)


    * waits & tries not to freak out * :P

  • What about the solution I ( norse) presented?

    if you are lookin for a developer to do that for you better look in WL forum, not everyone is registered here.


    @Alexander Ebert posted this else where....

    Quote

    Adam We've discussed this internally and we came up that this is nothing we can add in an instant. We either implement it everywhere or nowhere and some parts of the system are not ready for this yet. For example the comment system isn't designed to have things filtered out on runtime, because they belong to an object (e.g. a user profile or blog article) and thus only require permissions for that object.

    Updating Redactor 9 -> 10 has already caused a significant delay and we're behind our internal schedule. Furthermore we plan on upgrading woltlab.com to Burning Board 4.1 in the next days, thus we don't want to start messing with an already working system.

    We have some stuff in our minds which aims to allow a user to temporarily override the block to be able to see blocked content. For example posts in a thread would appear collapsed, hiding it at a first glance but the user could click on that post to view it content. This way a user can decide if he/she wants to view the content in order to be able to follow the entire discussion. It's intended to be a balance between blocking and still be able to follow a thread if the user wishes to.

    I understand that you and your community would be satisfied by simply filtering everything out, but we're taking a look at the big picture and try to account the wishes of all our customers and compile that into a single feature.


    ^ Their desired goal for 4.2 is what I would have an added do. When asked if it currently supports the hooks for an addon, this was the reply...

    Quote

    There should be more than enough events, any experienced developer should be able to handle this.

    So that's basically what I'll be aiming for :)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!