Return-Path: Delivered-To: apmail-roller-user-archive@www.apache.org Received: (qmail 70443 invoked from network); 1 Jun 2007 18:23:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Jun 2007 18:23:26 -0000 Received: (qmail 14161 invoked by uid 500); 1 Jun 2007 18:23:29 -0000 Delivered-To: apmail-roller-user-archive@roller.apache.org Received: (qmail 13992 invoked by uid 500); 1 Jun 2007 18:23:28 -0000 Mailing-List: contact user-help@roller.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@roller.apache.org Delivered-To: mailing list user@roller.apache.org Received: (qmail 13983 invoked by uid 99); 1 Jun 2007 18:23:28 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 11:23:28 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of snoopdave@gmail.com designates 64.233.166.182 as permitted sender) Received: from [64.233.166.182] (HELO py-out-1112.google.com) (64.233.166.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Jun 2007 11:23:23 -0700 Received: by py-out-1112.google.com with SMTP id u52so1103149pyb for ; Fri, 01 Jun 2007 11:23:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MXRQSQ4NnxPa88v2j077h64F5RCbrGILTguUDx/2ID6ngLd6RKqrJ3jhLrkwKqooQmfIWfekwsLvait/tXTs15RnSWRMKsy7HloyQVlkn6aFPIk97TNfahOqoKqr8QHodaqvMPeTFYPPHa5zotFUn3Nr9jpLnZPSnp81lTt6cyM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hc730itvnzFjZOYg8wKUUZu2s2CJepC87OXqt5m2oQXavdpHNXiktWTFD04y/AXvo+9pRh9sW9/axdHeZMmDzI6Co1e2ra1Y3plBDiWFGRs3TXCwgk/VgThaekwA3EFFAg5momPsu6h8/moGGWVYyh3HrmpoY5bxGaQA8I4+0B4= Received: by 10.65.137.5 with SMTP id p5mr3630397qbn.1180722181962; Fri, 01 Jun 2007 11:23:01 -0700 (PDT) Received: by 10.65.180.14 with HTTP; Fri, 1 Jun 2007 11:23:01 -0700 (PDT) Message-ID: <8fb9ac720706011123s1fd9485djb8e26c6d66311f4e@mail.gmail.com> Date: Fri, 1 Jun 2007 14:23:01 -0400 From: Dave To: user@roller.apache.org Subject: Re: new registered users disabled by default In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org On 5/31/07, Andrew Smalera wrote: > Is there a way to say that users who just registered have disabled accounts > by default? That way as an admin I can check and verify registrations > before a new user can start blogging. In Roller 4.0 we will have account activation via email, but I'm guessing you want to do a "manual" review. > I was thinking of this in terms of configuration but if anyone has an > idea in terms of the source code that would help too. So far I tried changing >the default value of the column in the DB but that didn't do it. I can't find > anything in the hibernate config or code that sets a default value either.. >So pointing me to the right place in the code would be very helpful. > > Also is there a way to say that enabled users can't create new blogs (only > post to existing ones that I've created and assigned to them). We don't have a way to configure that now, but IMO it's definitely something that should be configurable. You're going to have to make code changes if you want to implement it. If you want to place restrictions on who can create new blogs, you should probably start with the MainMenu and CreateWeblog actions and corresponding JSP pages. - Dave