YonasH wrote:

So, if default group will not have permission to post, you'll get what yu want smile
They (and only they) will just see new forum with instructions how to get full access. No spam boots will come through.

Sorry to resurrect an old thread, but wondering if there's a way to prevent a group of users from modifying visible user parameters (signatures / website, for example). Just some background on the actual problem I'm trying to solve...

I'm seeing a lot of SEO spammers signing up, waiting a while, then adding a signature and / or website, but not actually posting. Even if the signup looks spammy, it's hard to know for sure to can them until the signature shows up (especially since I have a lot of legitimate foreign users on my forum). I believe humans are involved in some part of the process, because they use a variety of throwaway email addresses, are usually connecting from the Philipines or other places where labor is cheap, and I have a captcha on the signup already.

Anyway, I'd love to be able to allow users to signup / post, but require manual intervention before someone can add a link or signature.

Another annoyance is that setting the signature length / lines to "0" prevents even the admin from emptying out a signature -- even if the text box is completely empty with no spaces, it seems to consider it "1" line. I'm running the latest 1.3.x

2

(10 replies, posted in PunBB 1.2 troubleshooting)

william wrote:

I end up with two cookies - one for www.example.com and one for example.com. Maybe makes more sense to make the cookie for .example.com, or at least have an option to do it this way?

ps - I did hard-code $cookie_domain to .example.com in the config, and that seemed to fix the problem, so sorry for the noise.

3

(10 replies, posted in PunBB 1.2 troubleshooting)

I'm having a similar issue, seemingly when someone logs in on www.example.com when the domain is set in the forum options to example.com.
PunBB 1.2.20 (patched for the latest update).

To reproduce:
go to www.example.com/login.php or www.example.com/index.php. Login is successful, but PunBB redirects to example.com/index.php, where the user now shows up as not logged in. If you go back to www.example.com, the user is once again logged in.

I end up with two cookies - one for www.example.com and one for example.com. Maybe makes more sense to make the cookie for .example.com, or at least have an option to do it this way?