Mailing-List: contact user-help@roller.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@roller.apache.org
Received-SPF: pass (athena.apache.org: domain of snoopdave@gmail.com
 designates 64.233.184.237 as permitted sender)
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=hPaZFDsXk59qPBzr5H3dTFI8v5Jwl6Y9jCZY8ksV+Znk8IiS+d5p3GN/NAip/qmMk/8UHyuGfVF/P5QL6N4+YZDa1oEpunVNS+p+RCLJf5H26INjsujrn4ds0Dv6w+VieilfkzVANOJqJlECvh6LPJViQRVan8Afm0sM7ur+cds=
Message-ID: <8fb9ac720710081210w74e876a6ia15d49879604fc54@mail.gmail.com>
Date: Mon, 8 Oct 2007 15:10:42 -0400
From: Dave <snoopdave@gmail.com>
To: user@roller.apache.org
Subject: Re: Prevent user from deleting blog
In-Reply-To: <470A5F5F.3000005@webopolis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <470A5F5F.3000005@webopolis.com>

On 10/8/07, Joe Meadows <jameadows@webopolis.com> wrote:
> When a new user registers at our site we use AAPP to create a new Roller
> user and a weblog.  The user and blog are both created using the user
> name of the new site user so that new-user's blog will be
> http://oursite.com/roller/new-user.  I've also set groupblogging.enabled
> to false. The problem is that the user may delete this default blog and
> then create a new one using any available handle which we'd like to
> prevent.  Actually, it's fine if the user wants to delete their blog,
> say to get a fresh start, so long as the recreated blog uses the same
> handle that we originally designated.  I haven't found any configuration
> options that can help with this, are there any settings or workarounds
> that can help with this?

I don't know of any way to config Roller to support that. Modifying
Roller to support that would almost certainly require a Java code
change (and thus require a new build). One possible work-around is to
disable weblog removal by removing the delete option from the Weblog
Settings page, that would only require a JSP change, which you could
potentially do yourself without creating your own custom build.

- Dave