hello today i purchased this addon but mistakely i think i purchased wrong addon i need addon to hide post and need to reply to see the post so this addon is different ?? am i right ??
Content Blur Pro - Boost Registrations and Upgrades [Paid] v2.4.8
- Thread starter Wutime
- Start date
how i can contact you by email ??? please need urgnt help
Thankyou
Wutime updated Content Blur Pro - Boost Registrations and Upgrades with a new update entry:
v2.4.7
Read the rest of this update entry...
v2.4.7
Read the rest of this update entry...
Wutime updated Content Blur Pro - Boost Registrations and Upgrades with a new update entry:
v2.4.8
Read the rest of this update entry...
v2.4.8
Read the rest of this update entry...
No, but could be added. Would it be just images in posts and attachments (and disabling viewing by clicking)?
Correct
Okay, should be workable. I have a larger update coming out, so I'll see if I can fold this into it prior to release.Correct
There's a Release Candidate v2.5.0 available for download to customers in the "Downloads" section as follows:
This release includes major improvements to blur/fade behavior, media controls, and admin charts/statistics. It has been stable in extended testing, but because of the scope of changes I’m publishing it as a beta first for broader real-world validation before final stable release.
Supported integrations:
Most integrations use a 3-permission model:
For newly added integration permissions, Unregistered + Registered are seeded to Allow so existing community memberes are not suddenly blur-blocked after upgrade.
Admins can then tighten permissions by group/category as needed.
Analytics note:
“Estimated value” is intentionally conservative by default.
This release includes major improvements to blur/fade behavior, media controls, and admin charts/statistics. It has been stable in extended testing, but because of the scope of changes I’m publishing it as a beta first for broader real-world validation before final stable release.
Supported integrations:
- XFMG
- XFRM
- XenAddons AMS (Article Management System)
- XenAddons UBS (User Blogs System)
- XenAddons Showcase
- XenAddons CAS (Classified Ads System)
Most integrations use a 3-permission model:
- Bypass blur for [content]
- Bypass blur for own [content]
- Bypass blur for media
- Content and media permissions are independent in supported integrations, so media-only blur is supported.
- Example media-only setup: allow content bypass, deny media bypass.
Result: text stays visible, media is blurred/locked. - “Own” bypass permissions allow users to view their own authored items unblurred (integration-specific behavior).
For newly added integration permissions, Unregistered + Registered are seeded to Allow so existing community memberes are not suddenly blur-blocked after upgrade.
Admins can then tighten permissions by group/category as needed.
Analytics note:
“Estimated value” is intentionally conservative by default.
- FRB-attributed registrations default to $2.00 each (adjustable in options).
- Upgrades currently reflect initial attributed upgrade events.
- Recurring subscription revenue is not yet included; that may be added in a future update.
Attachments
Last edited:
Wutime updated Content Blur Pro - Boost Registrations and Upgrades with a new update entry:
v2.5.0 Release Candidate 1
Read the rest of this update entry...
v2.5.0 Release Candidate 1
Read the rest of this update entry...
Hi Wutime,
thanks for this awesome add on, you did a great job.
Is it possible to block blurred content for a specific registered user group, independent from guests, on selected thread IDs?
In other words, I would like to restrict access to specific threads by ID for one particular registered user group, even though they are logged in.
Best regards
thanks for this awesome add on, you did a great job.
Is it possible to block blurred content for a specific registered user group, independent from guests, on selected thread IDs?
In other words, I would like to restrict access to specific threads by ID for one particular registered user group, even though they are logged in.
Best regards
Yeah, 100%, just do it with "Node permissions", that's actually the entire reason for the permissions being permissions.
If you have questions, shoot.
Hi Wutime,
thanks for getting back to me.
I found the node permissions now and I understand how to restrict complete forums.
What I still can’t figure out is how to apply the blur to single threads only.
My goal is:
- registered members in a specific user group should be blocked (blurred) on selected thread IDs
- without moving those threads into a separate forum if possible
Am I missing a setting in Content Blur Pro for “thread ID based” restrictions, or is the add on designed to work only via node permissions?
If it’s node only, would you recommend any clean workaround for single threads (besides creating a dedicated node and moving the threads)?
Best regards
There's no "per individual thread" system available to mark something blurred. I think it would get messy trying to fight XenForo to implement it.
Instead, it uses the built-in permission system of XenForo. So yes, in keeping with XF, threads that require special handling need to be in a specific forum. Similarly, media need to be in categories.
Hi Wutime,
thanks, that makes sense and I understand the design choice.
I think I confused myself because I tried to enter thread IDs in the Content Blur Pro admin, and then got results like “everything is blurred” or “nothing is blurred”. So just to confirm, there is no supported way in Content Blur Pro (or in XenForo permissions) to blur or block only specific thread IDs inside the same forum. Correct?
thanks, that makes sense and I understand the design choice.
I think I confused myself because I tried to enter thread IDs in the Content Blur Pro admin, and then got results like “everything is blurred” or “nothing is blurred”. So just to confirm, there is no supported way in Content Blur Pro (or in XenForo permissions) to blur or block only specific thread IDs inside the same forum. Correct?
Oh, you're using the antiquated "Choose your implementation = Guests mode (legacy mode)". Yes, under that mode you can specify NODE ID targeting. But it's not recommended to use that mode, nor is it well tested recently.
