blocking plugin (or code/script) needed

[RichardInTN]

There was some suggestion on the main "support" subforum (here's the thread) for an option for Admin and/or Mods to be able to force "ignore" on members between members, and it was deemed by PB to be unnecessary as a built in function.

I think there's definitely a use for such an option though.

So here's what I am requesting:

I need a plugin that only Mods and Admin can access (it's fine if changes need to be made via the "Admin Control Panel") where we can cause members thread posts to be ignored by each other. Ideally I'd like the plugin to completely block the post itself from even existing, using a suggestion from Lynx I tweaked the  CSS in each of my Themes so that they remove blocked posts from even existing, that members themselves have blocked, so I know removing posts is doable:

Here's what I did there:

Changed

{if $[post.is_blocked]}
<td class="$[post.blocked_class] content center">
<div class="message note pad-bottom">This post is hidden</div>
$[post.display_blocked_post_button]
</td>
{/if}

to

<!-- {if $[post.is_blocked]}
<td class="$[post.blocked_class] content center">
<div class="message note pad-bottom">This post is hidden</div>
$[post.display_blocked_post_button]
</td>
{/if}
-->

"commenting" it out

I'm thinking some sort of "{if $[member.name]=variable-for-any-name-from-the-editable-list}" in place of "{if $[post.is_blocked]}" and then removal of the post itself




The block needs to be bidirectional. If "Member A" is blocked from seeing "Member B", then "Member B" needs to be blocked from seeing "Member A" at the same time. Duplicate entry should not be necessary.

In the "Settings" section of the plugin, there should be a simple line for each instance that needs to be enforced:

Block these two members from seeing each other: {member picker} {member picker}

And then a new line is created for the next entry.

There would also need to be a way of removing the blocks... like a "select to remove" (or an "X" that can be clicked) option or something.

If you'd like to take up the challenge and have any questions, please feel free to post 'em!

[RichardInTN]

Thank GOD it's been 24 hours now...

I really, really, REALLY need this plug in!

(kidding)

Just bumping it to keep it relevant.

[RichardInTN]

Bump!

[RichardInTN]

Bump, and also adding an option that could come in handy.

If possible, it would be nice if bi-directional blocking could also be user controlled as well, based on who a user is blocking as well.

[Kami]

Just some brainstormy ideas for this plugin / possible roadblocks:

- the plugin would have to be written in javascript and therefore not a secure option (disabling js in any manner would render it inoperable. Might not be a problem if the user is not tech savvy and wouldn't know to do so, but could be if they are)

- how would the blocked users be identified without making the effects of the plugin affect all users? i can think of using a personal key (which is bugged) so it can only be written for that account, but that also means the staff can't use the plugin to force a block on an unwilling person. You could, theoretically, use member groups to dictate the plugin only affects those in that member group, but there might be an issue with regards to one block affecting all users in the group (eg: if Bob, Joe, and Mike are in the affected group, Bob blocking / being made to ignore Joe means that Mike also winds up with Joe blocked / ignored).

[RichardInTN]

Javascript problem is taken care of. I'm running the "Hide Forum When Javascript Is Disabled" plugin.


ETA: and it does actually work, I just checked by turning off Javascript and reloading a page on my forum, it wouldn't display.

[Kami]

Jun 8, 2017 2:29:06 GMT -8 RichardInTN said:

Javascript problem is taken care of. I'm running the "Hide Forum When Javascript Is Disabled" plugin.

that's good for desktop view but wouldn't affect anyone on the current mobile view.

[RichardInTN]

I understand that. It's a limitation, sure, but we do the best we can with what we have.

[RichardInTN]

Bump... and a thought... Could this be done with PHP in HTML? doing a little research led me to the knowledge that PHP has the "if, then" capability.



ETA: forget the PHP suggestion. That was a brain fart on my part. I was confusing PHP with "pbp format" which plugins use.

[Kami]

Jun 9, 2017 17:51:10 GMT -8 RichardInTN said:

Bump... and a thought... Could this be done with PHP in HTML? doing a little research led me to the knowledge that PHP has the "if, then" capability.

Sorry I keep responding despite not being able to write plugins yet, but to answer your question PB does not support PHP. :(

There's no need for it though, because javascript can also use conditional statements, albeit with different syntax. It's just a matter of whether or not this is possible (as in, if the software will allow for such a modification) and whether or not a plugin author would be willing to take on the task.

[Former Member]

The problem is with persisting data, it really is that simple. Proboards allows modifying frontend behaviors(html|css|javascript). It does not support backend communication via an API for persistent data

[RichardInTN]

Jun 9, 2017 17:57:06 GMT -8 Kami said:

Jun 9, 2017 17:51:10 GMT -8 RichardInTN said:

Bump... and a thought... Could this be done with PHP in HTML? doing a little research led me to the knowledge that PHP has the "if, then" capability.

Sorry I keep responding despite not being able to write plugins yet, but to answer your question PB does not support PHP.

There's no need for it though, because javascript can also use conditional statements, albeit with different syntax. It's just a matter of whether or not this is possible (as in, if the software will allow for such a modification) and whether or not a plugin author would be willing to take on the task.

LOL... no worries about responding with a good question! I can't write plugins either, but I have ideas. People voicing ideas, even if they have no ability to implement them, is how great things happen!

I was trying to come up with a workaround to do it outside of Java... Because maybe someone would say "Hey, instead of a plugin, do this in your {header or footer}, and then it will work on mobile too. {with appropriate code attached in a "code" box}" That's what happened when I asked for a plugin to remove the "you are blocking this member, click here to reveal post" (or whatever it said) posts of blocked members

[Kami]

Jun 9, 2017 19:53:24 GMT -8 RichardInTN said:

Jun 9, 2017 17:57:06 GMT -8 Kami said:

Sorry I keep responding despite not being able to write plugins yet, but to answer your question PB does not support PHP. :(

There's no need for it though, because javascript can also use conditional statements, albeit with different syntax. It's just a matter of whether or not this is possible (as in, if the software will allow for such a modification) and whether or not a plugin author would be willing to take on the task.

LOL... no worries about responding with a good question! I can't write plugins either, but I have ideas. People voicing ideas, even if they have no ability to implement them, is how great things happen!

I was trying to come up with a workaround to do it outside of Java... Because maybe someone would say "Hey, instead of a plugin, do this in your {header or footer}, and then it will work on mobile too. {with appropriate code attached in a "code" box}" That's what happened when I asked for a plugin to remove the "you are blocking this member, click here to reveal post" (or whatever it said) posts of blocked members

java and javascript are not the same thing for whatever it's worth! but the thing about headers & footers is that they are also written in javascript, plugins simply make a user-friendly UI. With v6, headers and footers will become plugins anyway and they will be eliminated as a whole.

I do not know who told you that H/F would work on mobile v5, because that is 100% misinformation. No coding modifications beyond some UBBC and some css (as dictated by the themes section of the admin panel) appear on mobile view.

[RichardInTN]

Jun 9, 2017 19:56:34 GMT -8 Kami said:

Jun 9, 2017 19:53:24 GMT -8 RichardInTN said:

LOL... no worries about responding with a good question! I can't write plugins either, but I have ideas. People voicing ideas, even if they have no ability to implement them, is how great things happen!

I was trying to come up with a workaround to do it outside of Java... Because maybe someone would say "Hey, instead of a plugin, do this in your {header or footer}, and then it will work on mobile too. {with appropriate code attached in a "code" box}" That's what happened when I asked for a plugin to remove the "you are blocking this member, click here to reveal post" (or whatever it said) posts of blocked members

java and javascript are not the same thing for whatever it's worth! but the thing about headers & footers is that they are also written in javascript, plugins simply make a user-friendly UI. With v6, headers and footers will become plugins anyway and they will be eliminated as a whole.

I do not know who told you that H/F would work on mobile v5, because that is 100% misinformation. No coding modifications beyond some UBBC and some css (as dictated by the themes section of the admin panel) appear on mobile view.

No one told me that... I was just flowing the thought that someone would say "this will work if you do (whatever)" Sorry for the confusion.

I was however, under the impression that it was just plugins that didn't run on the Mobile version. I didn't realize Mobile also blocked headers and footers. Good to know!

[Kami]

Oh I see! I misinterpreted that entirely, sorry!

And yeah the current mobile view does not take ANY coding changes into consideration -- plugins, headers and footers, and a vast majority of CSS (as a side note this is why v6 is such a big deal, as forums will be responsive instead of having a separate mobile view so all modifications will work unless someone deliberately circumvents it). Right now though. there is no way to get any coding (even html) to work in the mobile view, you have to switch to the desktop view.

Phil seems to have presented another hiccup in this request as well, so it may not be possible after all due to developer limitations (if I'm understanding him correctly).