Recent content by Wutime

If you need it in the future do the following to override defaults and delete all guests: php cmd.php wutime-adblock-tracker:clear-data -d 0 guests

Wutime updated AdBlock Usergroup Swap & Tracker with a new update entry: v3.1.2 Read the rest of this update entry...

I don't think there is; I'll follow up.

Wutime updated Search Limit Essentials - Boost Registrations and Upgrades with a new update entry: v1.3.2 Read the rest of this update entry...

Last time I had this issue was Wednesday and then it resolved itself since. I think it was an issue with their service not Xenforo.

Yeah, like @philmckrackon said, just add a new usergroup that bypasses the adblock, and then add a "usergroup promotion" that promotes users to that new usergroup based on having X posts.

Wutime updated Content Blur Pro - Boost Registrations and Upgrades with a new update entry: v2.5.0 Release Candidate 3 Read the rest of this update entry...

Hey, let the morphine wear off and focus on getting better. Did my best by including the screenshot.

Oh, I thought you were running the "Release Candidate" (RC). If you want to stick with v2.4.8 you'll need to just edit the phrase to remove "<strong>" and "</strong>" yourself. I was referring to downoading the RC version, which is the one I updated.

Then I'm confused, because "thread ids" input box ONLY shows in the Guests Mode. Yes, correct, 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. Yes, the above ONLY exists if you use GUESTS mode, which...

Hmmm, the link is in the identical spot that the form RC download button was. Click it and it'll download the current one.

Okay, it's posted @philmckrackon, RC2 doesn't have the phrase issue. Same download location as before, need to visit to download.

Oh, my bad, I'll release the RC2 update now. Thanks for letting me know about the issue.

The phrase is: wutime_forcereg_blur_please_register_x_or_y_message You're also using the old "Choose your implementation = Guests Mode (legacy mode)" system implementation as this issue doesn't occur with the recommended "Users" mode. You should update. I've been asking customers to migrate...

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.