Recent content by tehelgee

I've done this, and it appears to be functioning just as I want it to. Thank you and @Brogan both for the assistance. :)

That's exactly what I want. Appear as a regular user to everyone else, including being ignored if a user decides to do so, and only access to the styles section of the ACP.

Will that permit them to be put on the ignore list?

On my forum, we have a position called Stylist, who are granted the sole admin permission of editing themes. I want to make those with that permission to not be Staff. Is that possible?

Man, that permission is confusing. No means approval required and yes means no approval required. :/

In the never ending battle against spam, I have decided I want to sort new users into a different primary group than Registered. Or, failing that, sorting accounts that match the criteria of 5 approved posts and 1 day old into a separate primary group from Registered. User Promotions only alter...

Nevermind, it works. I was just dumb in testing permissions.

Saw that one too, and if I went with any, it'll be that one. Found another, that's free, but it doesn't appear to work.

Saw that. I don't need the other options, so I don't want to pay $30 for a single feature.

The title pretty well says it all. I want to allow my users to lock their threads in specific subforums, but Xenforo's current permissions give users the ability to lock/unlock any thread in those subforums, not just their own.

Alright, I will make that request. Thanks for the answer.

I want to give my users the ability to lock/unlock their own threads in specific subforums OR preventing users from posting in a thread they did not create. I only want to do one, not both. I figure doing either will require a brand new permission not included in Xenforo's default set of...

Oh, hey Xon. Anyway, with the assistance of a much more IT knowledgeable member of my forum, we switched to FastCGI and a reinstall was done with the old database imported into the new install. And, all the problems seem to have gone away. So, it doesn't seem like it was a configuration...

Well, back again after the provider has looked over things. This is what they pointed out. Any ideas?

Update on that: apparently during the reboot, the server failed to reboot. Provider tech couldn't get it to reboot properly either. Provider admin will be looking into it now. /me just has no luck.