Jump to content

Why can't URL block and PROFANITY filter work together?


SJ77

Recommended Posts

Unless I am missing something, it seems you can only have 1 outcome

  • Can block desired word in URL.. but href link will still work
  • Can block href link but full language will be displayed.

This is frustrating especially since neither URL filter or profanity blocker will work retroactively.  I need both the url and the words in the url to be blocked.

Example: www.DirtyWord.com

Suppose I block "DirtyWord" using my profanity filter and replace it with "****".  Then whenever anyone tries to add this URL in a post users will see "www.****.com" but clicking the URL will still lead to www.DirtyWord.com <-- not good.

Well, suppose I instead try to also block the URL, then whenever anyone tries to add the URL users get the full thing "www.DirtyWord.com" but it simply will not be a link that anyone can click. However, they can simply copy the URL and paste it in the address bar.

I want to block both the link AND the word.. so "www.****.com" is what users see and when they click it, NOTHING happens.

Is this just a case of me not understanding how to use the tools? or is something wrong here? Why can't I do both?

Thank you :)

Link to comment
Share on other sites

This particular issue (which is a bit different to the topic chilihead linked to) is fixed in 4.1.9. If "Google" is in your profanity filters and "*.google.com" is in your disallowed URLs, attempting to post http://www.google.com will come through as http://www.xxx.com.

The code which handles all "on submit" parsing has been significantly reworked and a bunch of issues like this where BBCode/profanity/disallowed URLs/acronym expansion/etc. behave oddly, especially in combination with one another, have been resolved.

Link to comment
Share on other sites

25 minutes ago, Mark said:

This particular issue (which is a bit different to the topic chilihead linked to) is fixed in 4.1.9. If "Google" is in your profanity filters and "*.google.com" is in your disallowed URLs, attempting to post http://www.google.com will come through as http://www.xxx.com.

The code which handles all "on submit" parsing has been significantly reworked and a bunch of issues like this where BBCode/profanity/disallowed URLs/acronym expansion/etc. behave oddly, especially in combination with one another, have been resolved.

Thanks Mark

However, will we be able to customize the "xxx" part? That looks a bit like a link to a triple X porn site. Might not be what people want on their forums.

Thank you

Link to comment
Share on other sites

9 hours ago, superj707 said:

Thanks Mark

However, will we be able to customize the "xxx" part? That looks a bit like a link to a triple X porn site. Might not be what people want on their forums.

Thank you

Yeah, I mean it will replace it with whatever you've set the profanity filter too :p 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...