Blacklists
By default, UNA has Privacy engine which allows a member to limit his content's visibility to some group of people (visitors, common members, etc). But sometimes it's needed to block only one or more undesirable members.
The Blacklists app adds this Very important feature to your UNA based site. Your users would be able to block undesirable member(s). Blocked member cannot view a content (posts, polls, ptoducts, etc.) of blocking member.
New in Version 2.0.0:
Now your users would be able to block countries which they don't want to be viewed from. It means that if User1 blocked some country and User2 specified this country in his profile's location (default Location field) then User2 won't be able to see profile and content of User1.
New in Version 2.5.0:
1. Common users cannot block advanced users (moderators and administrators)
2. Manage Tools. Advanced users may view cross profiles blocks and remove them if it's necessary.
New in Version 3.0.0:
1. Integration with #Timeine. Blocked member cannot see blocker's posts in Timelines.
2. Integration with standard browsings. Blocked member cannot see blocker's posts in latest, top, popular, etc lists.
3. So called 'Cross mode'. When it's enabled (Studio -> Blacklists -> Settings -> 'Filter out blocked member's content' setting) blocker member won't see the content of blocked member too.
New in Version 3.5.0:
1. Integration with #Messenger. Blocked member cannot contact with blocker using #Messenger app.
New in Version 4.0.0:
1. Works under UNA 13.
2. Allows to make the blocker's comments blurry for blocked member(s). If 'Filter out blocked member's content' setting is enabled, then comments of blocked members will be blurry for a blocker too.
-
- · AQB Soft
- ·
Hello everybody!
Version 1.1.0 was relesed. Changes log:
1. Blocked members cannot see blocker's profile.
2. Settings in Studio -> Blacklists allow to disable Profile and/or Content blocks separately.
3. Bug fixes.
-
- · Baloo
- ·
This module brings a makeup feature in Una, simple and effective, thank you very much for having done so.
-
- · AQB Soft
-
·
In reply to Baloo
- ·
You are very welcome and thank you for the review!
-
- · Cem
-
·
In reply to AQB Soft
- ·
How to name your modules for language files?
for example bx_albums and for black_lists?AQB Soft ?
-
- · AQB Soft
-
·
In reply to Cem
- ·
Hello
You may find the name of any module which can be used in language app in install/config.php file, name parameter.
As for Blacklists it's aqb_black_lists
---
Best Regards
Anton
-
- · Jottwee
- ·
Everything fine, on 11 RC2. Thanks and greetings from Leipzig, Germany.
-
- · AQB Soft
-
·
In reply to Jottwee
- ·
Thank you for the review!
-
- · unknown
- ·
Please just bought module...not seeing block option on profile page
-
- · AQB Soft
-
·
In reply to unknown
- ·
Hello. If the app was installed then could you please check Actions menu -> More submenu on a profile which you want to block. By default new buttons are added at the end of the list.
-
- · AQB Soft
-
·
In reply to unknown
- ·
Hello
I recheked your site and as I found out you are using custom profile URLs like https://goiwelkin.com/Cloudpay It doesn't allow Blacklists app to work correctly.
Note, it may also mix some deafult UNA features because default UNA function bx_get_base_url_inline() cannot determine the page correctly.
-
- · AQB Soft
-
·
In reply to unknown
- ·
Hello. The new 2.0.4 version was released. It should work with custom profile URLs.
-
- · Will Monte
- ·
Nice mod, great work like alway by AQB Soft , may i make a suggestion?
-
- · Will Monte
- ·
I have a question, shouldn't it be that black list completely block those that are not admin accounts to prevent them from seeing anything from the user that blocked other user?
-
-
-
- · Amitesh Kumar
- ·
is the latest version compatible with una 13?
-
- · Antonio
- ·
In the browser console I get this error on all pages.
Uncaught TypeError: AqbBlackListsMain is not a constructor
at XXXXXXXXXXXXXXX
-
- · LoneTreeLeaf
- ·
Broken for 13.1.0 RC2 update.
message: PHP Fatal error: Declaration of AqbBlackListsModule::serviceGetMenuAddonManageToolsProfileStats() must be compatible with BxBaseModGeneralModule::serviceGetMenuAddonManageToolsProfileStats($iProfileId = 0) in /var/www/vhosts/somewebsite.com/httpdocs/modules/aqb/black_lists/classes/AqbBlackListsModule.php on line 139'
-
- · AQB Soft
-
·
In reply to Mayki
- ·
Yes, new 4.1.0 version was released. It correctly works under UNA 13.1.0 RC2.
-
- · Mayki
-
·
In reply to AQB Soft
- ·
Thank you @AQB Soft - upgraded UNA to latest version 13.1.0-RC-2 and all went well - Black Lists module also upgraded to latest version.
-
- · AQB Soft
-
·
In reply to Mayki
- ·
You are very welcome!
-
- · LoneTreeLeaf
- ·
Looks like the latest UNA beta release has broken this app.
Regardless if people have blocked others, they are still able to send friend requests to the person.
-
My statement still stands, your module piggy backed off of your core product, UNA (yes I know you are the same devs, no use in hiding that), so what are we actually buying that is original code here? If the module never prevented someone from interacting with the person, then this is just false advertising on your part, as it's not a black list anymore, and never was. It's just a glorified blur module.
-
This module does exactly what is described in product description: 'allows a member to limit his content's visibility to some group of people'. If in your opinion it should do something else you are welcome to develope your own and use.
-
Nice deflecting, very professional, continue to do so, allow more people to further see how the UNA devs truly are.
Please define "Black List" in the sense of a social networking platform where a user blocks another member, what should be the expected results?
When a user blocks another member on a social networking platform, the "blacklist" refers to the blocked user's restricted ability to interact with the blocker. The expected results typically include the following:
Profile Visibility:
The blocked user cannot view the blocker’s profile.
The blocker’s profile may be completely hidden or limited in visibility to the blocked user.
Communication Restrictions:
The blocked user cannot send messages to the blocker.
Any existing conversations between the two users might be archived or hidden from the blocker’s view.
Interaction Restrictions:
The blocked user cannot comment on or like the blocker’s posts.
The blocked user cannot tag the blocker in posts, photos, or comments.
Content Visibility:
The blocked user cannot see posts, stories, updates, or other content shared by the blocker.
The blocker’s content may not appear in the blocked user’s feed or search results.
Notifications:
The blocked user will not receive notifications about the blocker’s activities (e.g., new posts, likes, comments).
Similarly, the blocker will not receive notifications about the blocked user’s activities.
Searchability:
The blocked user might be unable to find the blocker through search functions on the platform.
The blocker’s profile and content might not appear in the blocked user’s search results.
Group and Event Participation:
In group settings, the blocked user may not see the blocker’s posts and vice versa.
In event settings, interactions between the blocked user and the blocker might be limited or prevented.
Third-Party Applications:
If the platform integrates with third-party applications or services, the block might extend to these, preventing interactions there as well.
Overall, the goal of blocking on social networking platforms is to ensure that users can control their interactions and protect themselves from unwanted communication and engagement.
-
- · LoneTreeLeaf
- ·
Nice to see an update that of which makes this more inline with how a blacklist/blocklist should function, however there seems to be a slight oversight on the interaction part as this is what the blocked member can still see.
Tested to see if the blocked member can send a conversation and they still can indeed.