roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From snoopd...@apache.org
Subject svn commit: r1062150 - in /roller/branches/roller_4.0: ./ apps/weblogger/docs/installguide/ apps/weblogger/docs/installguide/generated/ apps/weblogger/docs/installguide/generated/html/ apps/weblogger/src/java/org/apache/roller/weblogger/config/ apps/we...
Date Sat, 22 Jan 2011 13:10:36 GMT
Author: snoopdave
Date: Sat Jan 22 13:10:36 2011
New Revision: 1062150

URL: http://svn.apache.org/viewvc?rev=1062150&view=rev
Log:
Defaulting to closed registration for 4.0 branch
see also https://issues.apache.org/jira/browse/ROL-1900

Modified:
    roller/branches/roller_4.0/   (props changed)
    roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide.html
    roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.pdf
    roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.txt
    roller/branches/roller_4.0/apps/weblogger/docs/installguide/roller-install-guide.odt
    roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/config/runtimeConfigDefs.xml
    roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/ui/struts2/core/Register.java

Propchange: roller/branches/roller_4.0/
------------------------------------------------------------------------------
--- svn:ignore (original)
+++ svn:ignore Sat Jan 22 13:10:36 2011
@@ -1,3 +1,3 @@
-
-build
+tomcat
 classes.eclipse
+build

Modified: roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide.html
URL: http://svn.apache.org/viewvc/roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide.html?rev=1062150&r1=1062149&r2=1062150&view=diff
==============================================================================
--- roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide.html (original)
+++ roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide.html Sat Jan 22 13:10:36 2011
@@ -3,9 +3,9 @@
 <HEAD>
 	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
 	<TITLE></TITLE>
-	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.0  (Unix)">
+	<META NAME="GENERATOR" CONTENT="LibreOffice 3.3  (Unix)">
 	<META NAME="CREATED" CONTENT="20070706;11182000">
-	<META NAME="CHANGED" CONTENT="20090102;10092100">
+	<META NAME="CHANGED" CONTENT="20110122;7475900">
 	<META NAME="KEYWORDS" CONTENT="OpenDS Directory Server Administration Framework">
 	<META NAME="Info 1" CONTENT="">
 	<META NAME="Info 2" CONTENT="">
@@ -51,7 +51,7 @@
 <BR>
 </P>
 <P CLASS="western" ALIGN=RIGHT STYLE="margin-bottom: 0in; background: transparent">
-<IMG SRC="file:///Users/dave/Source/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide_html_490f4977.png" NAME="graphics1" WIDTH=252 HEIGHT=102 BORDER=0></P>
+<IMG SRC="roller-install-guide_html_490f4977.png" NAME="graphics1" WIDTH=208 HEIGHT=84 BORDER=0></P>
 <P CLASS="western" ALIGN=LEFT STYLE="margin-bottom: 0in; background: transparent">
 <BR>
 </P>
@@ -136,7 +136,7 @@ Roller Weblogger</B></FONT></FONT></P>
 <FONT FACE="Helvetica, sans-serif"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Version
 4.0.1</B></FONT></FONT></P>
 <P CLASS="western" ALIGN=LEFT STYLE="margin-bottom: 0in; background: transparent">
-<SDFIELD TYPE=DOCINFO SUBTYPE=CHANGE FORMAT=DATE SDNUM="1033;1033;MMMM YYYY">January 2009</SDFIELD>
+<SDFIELD TYPE=DOCINFO SUBTYPE=CHANGE FORMAT=DATE SDNUM="1033;1033;MMMM YYYY">January 2011</SDFIELD>
 </P>
 <P CLASS="western" ALIGN=LEFT STYLE="margin-bottom: 0in; background: transparent">
  
@@ -256,25 +256,25 @@ project.</P>
 <BR>
 </P>
 <H2 CLASS="western">1.4Modifications and Updates</H2>
-<TABLE WIDTH=100% BORDER=1 BORDERCOLOR="#000000" CELLPADDING=4 CELLSPACING=0 RULES=COLS STYLE="page-break-inside: avoid">
+<TABLE WIDTH=100% CELLPADDING=4 CELLSPACING=0 RULES=COLS STYLE="page-break-inside: avoid">
 	<COL WIDTH=59*>
 	<COL WIDTH=197*>
 	<THEAD>
 		<TR VALIGN=TOP>
-			<TH WIDTH=23%>
+			<TH WIDTH=23% STYLE="; border-top: 1px solid #000000; border-bottom: none; border-left: 1px solid #000000; border-right: none; padding-top: 0.04in; padding-bottom: 0in; padding-left: 0.04in; padding-right: 0in">
 				<P CLASS="western" ALIGN=LEFT>Date</P>
 			</TH>
-			<TH WIDTH=77%>
+			<TH WIDTH=77% STYLE="border-top: 1px solid #000000; border-bottom: none; border-left: 1px solid #000000; border-right: 1px solid #000000; padding-top: 0.04in; padding-bottom: 0in; padding-left: 0.04in; padding-right: 0.04in">
 				<P CLASS="western" ALIGN=LEFT>Description of Change</P>
 			</TH>
 		</TR>
 	</THEAD>
 	<TBODY>
 		<TR VALIGN=TOP>
-			<TD WIDTH=23%>
+			<TD WIDTH=23% STYLE="border-top: none; border-bottom: 1px solid #000000; border-left: 1px solid #000000; border-right: none; padding-top: 0in; padding-bottom: 0.04in; padding-left: 0.04in; padding-right: 0in">
 				<P CLASS="western" ALIGN=LEFT>July 2007</P>
 			</TD>
-			<TD WIDTH=77%>
+			<TD WIDTH=77% STYLE="border-top: none; border-bottom: 1px solid #000000; border-left: 1px solid #000000; border-right: 1px solid #000000; padding-top: 0in; padding-bottom: 0.04in; padding-left: 0.04in; padding-right: 0.04in">
 				<P CLASS="western" ALIGN=LEFT>Rewritten for simplified Roller 4.0
 				installation process</P>
 			</TD>
@@ -344,7 +344,46 @@ with <B>Section 3</B> below. 
 </P>
 <P CLASS="western"><BR><BR>
 </P>
-<H1 CLASS="western">3Ready to roll?</H1>
+<H1 CLASS="western" STYLE="page-break-before: always">3Securing
+Roller</H1>
+<P CLASS="western"><FONT SIZE=4>Security should be top-of-mind when
+setting up any web site, even one that is on a private network and
+internal to your organization. Here are some recommendations for
+keeping your Roller installation secure:</FONT></P>
+<UL>
+	<LI><P CLASS="western"><FONT SIZE=4><B>Perform Roller installation
+	on a secure network</B>. When you are installing Roller it is
+	possible for other users to interfere with your installation. If
+	other users have access to the server, one of them could create the
+	admin account before you do. So, when you install Roller, do so on a
+	server that cannot be accessed by others.</FONT></P>
+	<LI><P CLASS="western"><FONT SIZE=4><B>Do not allow open
+	registration of new users</B>. Roller can offer a registration link
+	so that new users can register themselves, but this feature is
+	turned off because it is not safe to allow just anybody to register
+	for an account on your blog server. If you want to turn it on, login
+	as an administrative user, go to Roller's Server Administration page
+	and enable the <B>Allow New Users</B> option.</FONT></P>
+	<LI><P CLASS="western"><FONT SIZE=4><B>Do not allow HTML in
+	comments</B>. Roller can allow users to write comments in a
+	safe-subset of HTML, but HTML use in comments is not allowed at all
+	because of security concerns with even a so called safe-subset of
+	HTML. If you want to turn it on, login as an administrative user, go
+	to Roller's Server Administration page, enable <FONT FACE="Times New Roman, serif">the
+	</FONT><FONT COLOR="#000000"><FONT FACE="Times New Roman, serif"><SPAN STYLE="font-style: normal"><B>Allow
+	html in comments</B></SPAN></FONT></FONT><FONT FACE="Times New Roman, serif">
+	o</FONT>ption and make sure the <B>HTML Subset Restriction</B> box
+	is checked.</FONT></P>
+	<LI><P CLASS="western"><FONT SIZE=4><B>Run Roller over SSL
+	connection</B></FONT><FONT SIZE=4>. If you run Roller over a plain
+	old HTTP connection, it is possible for others to snoop your
+	password when you login, for example over an open WIFI network.
+	Instead, you should consult your Java Application Server's
+	documentation and configure your Roller installation to run via
+	HTTPS only. </FONT>
+	</P>
+</UL>
+<H1 CLASS="western">4Ready to roll?</H1>
 <P CLASS="western">First, let's make sure you have everything you
 need to install and run Roller.</P>
 <P CLASS="western" ALIGN=LEFT>Roller is a database-driven Java web
@@ -373,7 +412,7 @@ what you need to install and run Roller:
 you're using Tomcat, check the Tomcat Considerations section below,
 otherwise you are ready to move on to Section 4: Download and
 un-package Roller.</I></FONT></FONT></P>
-<H2 CLASS="western">3.1Tomcat: JavaMail and Activation</H2>
+<H2 CLASS="western">4.1Tomcat: JavaMail and Activation</H2>
 <P CLASS="western" STYLE="font-style: normal"><FONT FACE="Times New Roman, serif"><FONT SIZE=3>Tomcat
 does not include the Java Mail and Activation jars that Roller needs
 for email notification, So, if you like to use Roller's e-mail
@@ -382,7 +421,7 @@ them in Tomcat's classpath. Download the
 (</FONT></FONT><A HREF="http://java.sun.com/products/javamail"><FONT FACE="Times New Roman, serif"><FONT SIZE=3>http://java.sun.com/products/javamail</FONT></FONT></A><FONT FACE="Times New Roman, serif"><FONT SIZE=3>)
 and place them in Tomcat's </FONT></FONT><FONT FACE="Courier New, monospace"><FONT SIZE=3>common/lib</FONT></FONT><FONT FACE="Times New Roman, serif"><FONT SIZE=3>
 directory.</FONT></FONT></P>
-<H2 CLASS="western">3.2Tomcat: URI encoding needed for I118N</H2>
+<H2 CLASS="western">4.2Tomcat: URI encoding needed for I118N</H2>
 <P CLASS="western"><FONT FACE="Times New Roman, serif"><FONT SIZE=3><SPAN STYLE="font-style: normal">Roller
 supports internationalization (I18N), but on Tomcat some additional
 configuration is necessary. You must ensure that Tomcat's URI
@@ -403,7 +442,7 @@ make sure you do this for <I>every</I> c
 use Roller. For example, if you use the AJP connector or HTTPS
 connector you need to add the <TT>URIEncoding=&quot;UTF-8&quot;</TT>
 attribute to those connectors as well.</FONT></FONT></P>
-<H1 CLASS="western">4Download and un-package Roller</H1>
+<H1 CLASS="western">5Download and un-package Roller</H1>
 <P CLASS="western">Download the Apache Roller release file from
 <A HREF="http://roller.apache.org/">http://roller.apache.org</A>. If
 you're a Windows user download the .zip file and use your favorite
@@ -411,7 +450,7 @@ ZIP program to unzip the release into a 
 disk. Unix users can download the .tar.gz file and use GNU tar to
 un-package. 
 </P>
-<H2 CLASS="western">4.1Installation directory layout</H2>
+<H2 CLASS="western">5.1Installation directory layout</H2>
 <P CLASS="western">Once you've unpackaged the files you'll find a
 directory structure like this:</P>
 <P CLASS="western"><BR><BR>
@@ -422,7 +461,7 @@ contain the Apache Software License and 
 to the release. The <FONT FACE="Courier New, monospace">README.txt</FONT>
 file just points to the documentation in the <FONT FACE="Courier New, monospace">docs</FONT>
 directory.</P>
-<H2 CLASS="western">4.2The Roller Weblogger WAR 
+<H2 CLASS="western">5.2The Roller Weblogger WAR 
 </H2>
 <P CLASS="western">The Roller Weblogger application itself is in the
 directory <FONT FACE="Courier New, monospace">webapp/roller</FONT>
@@ -436,7 +475,7 @@ WAR:</P>
    % jar cvf ../roller.war *</PRE><P CLASS="western" STYLE="font-style: normal">
 <BR><BR>
 </P>
-<H1 CLASS="western">5Prepare your database for Roller</H1>
+<H1 CLASS="western">6Prepare your database for Roller</H1>
 <P CLASS="western">Before you can install Roller you'll probably need
 to some work to prepare your database for Roller. 
 </P>
@@ -449,7 +488,7 @@ driver installed for you database of cho
 built-in JavaDB/Derby database, you can skip this section; there's no
 need to create a database in Derby and Glassfish already includes the
 Derby JDBC driver.</I></P>
-<H2 CLASS="western">5.1Create a database for Roller 
+<H2 CLASS="western">6.1Create a database for Roller 
 </H2>
 <P CLASS="western">If you're luck enough to have your own database
 administrator, ask them to setup a database for Roller. When they are
@@ -471,7 +510,7 @@ do something like this:</P>
    <FONT FACE="Courier New"><FONT SIZE=2 STYLE="font-size: 11pt">mysql&gt; create database rollerdb;</FONT></FONT>
    <FONT FACE="Courier New"><FONT SIZE=2 STYLE="font-size: 11pt">mysql&gt; grant all on rollerdb.* to scott@'%' identified by 'tiger';</FONT></FONT>
    <FONT FACE="Courier New"><FONT SIZE=2 STYLE="font-size: 11pt">mysql&gt; grant all on rollerdb.* to scott@localhost identified by 'tiger';</FONT></FONT></PRE><H2 CLASS="western">
-5.2Check your JDBC driver setup</H2>
+6.2Check your JDBC driver setup</H2>
 <P CLASS="western">Make sure that you have the correct JDBC driver
 installed in your server. Usually, this is as simple as downloading
 the JDBC driver jar(s) and placing it (or them) into your server's
@@ -480,7 +519,7 @@ on Tomcat 6.0 in <FONT FACE="Courier New
 on Glassfish in your domain's <FONT FACE="Courier New, monospace">lib</FONT>
 directory. 
 </P>
-<H2 CLASS="western">5.3MySQL and Oracle considerations</H2>
+<H2 CLASS="western">6.3MySQL and Oracle considerations</H2>
 <P CLASS="western">Based on our experience supporting MySQL, we have
 the following recommendations:</P>
 <UL>
@@ -499,7 +538,7 @@ the following recommendations:</P>
 	higher) drivers which should be packaged as ojdbc14.jar, even if
 	operating on Oracle 9 server.</P>
 </UL>
-<H1 CLASS="western">6Configure Roller</H1>
+<H1 CLASS="western">7Configure Roller</H1>
 <P CLASS="western">It is possible for you to configure Roller by
 creating and editing only one file:</P>
 <P CLASS="western">   <FONT FACE="Courier New, monospace">roller-custom.properties</FONT></P>
@@ -539,7 +578,7 @@ are not up-to-date Roller will offer to 
 your Roller installation is complete and you are ready to go “live”
 then you should set<FONT FACE="Courier New, monospace">
 installation.type=manual</FONT>.</P>
-<H2 CLASS="western">6.1MySQL example</H2>
+<H2 CLASS="western">7.1MySQL example</H2>
 <P CLASS="western">Here is an example roller-custom.properties file
 that shows how to setup a MySQL connection. It shows the MySQL JDBC
 driver class name, an example MySQL connection URL and
@@ -556,12 +595,12 @@ username/password settings for the mail 
 <TT>   <FONT FACE="Courier New"><SPAN STYLE="font-style: normal"><SPAN STYLE="font-weight: normal">mail.password=</SPAN></SPAN></FONT></TT><TT><FONT FACE="Courier New"><I><B>tiger</B></I></FONT></TT>
 </PRE><P CLASS="western">
 Next, we'll deploy Roller.</P>
-<H1 CLASS="western" STYLE="page-break-before: always">7Deploy Roller</H1>
+<H1 CLASS="western" STYLE="page-break-before: always">8Deploy Roller</H1>
 <P CLASS="western">Now that you've got the Roller WAR and you've
 created your <FONT FACE="Courier New, monospace">roller-custom.properties</FONT>
 file, you're ready to deploy Roller to your server. First, deploy
 your properties file.</P>
-<H2 CLASS="western">7.1Put <FONT FACE="Courier New, monospace">roller-custom.properties</FONT>
+<H2 CLASS="western">8.1Put <FONT FACE="Courier New, monospace">roller-custom.properties</FONT>
 in classpath</H2>
 <P CLASS="western">Roller can look for your properties file in a
 number of ways and you can see <B>Section 11</B> for details. The
@@ -579,7 +618,7 @@ on some popular servers:</P>
 	directory.</P>
 </UL>
 <P CLASS="western">Now you're ready to deploy Roller itself.</P>
-<H2 CLASS="western">7.2Deploy Roller via administration console</H2>
+<H2 CLASS="western">8.2Deploy Roller via administration console</H2>
 <P CLASS="western">Use your server's administration console to deploy
 the Roller web application. 
 </P>
@@ -614,24 +653,24 @@ Glassfish v2.0</H4>
 <P CLASS="western">You can also deploy to Glassfish as either a
 directory or a WAR file. The screenshot below shows directory-based
 deployment options.</P>
-<P CLASS="western"><IMG SRC="file:///Users/dave/Source/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide_html_148117bd.png" NAME="graphics5" ALIGN=LEFT WIDTH=712 HEIGHT=656 BORDER=0><BR CLEAR=LEFT><BR><BR>
+<P CLASS="western"><IMG SRC="roller-install-guide_html_148117bd.png" NAME="graphics5" ALIGN=LEFT WIDTH=588 HEIGHT=542 BORDER=0><BR CLEAR=LEFT><BR><BR>
 </P>
 <P CLASS="western"><SPAN STYLE="background: transparent">Once Roller
 is deployed, you'll see that it's listed among the other
 applications. There's a <B>Launch</B> link to Roller itself and there
 are buttons to enable, display and redeploy.</SPAN></P>
-<P CLASS="western"><IMG SRC="file:///Users/dave/Source/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide_html_m11d68315.png" NAME="graphics6" ALIGN=LEFT WIDTH=708 HEIGHT=127 BORDER=0><BR CLEAR=LEFT><SPAN STYLE="background: transparent">If
+<P CLASS="western"><IMG SRC="roller-install-guide_html_m11d68315.png" NAME="graphics6" ALIGN=LEFT WIDTH=585 HEIGHT=105 BORDER=0><BR CLEAR=LEFT><SPAN STYLE="background: transparent">If
 Roller doesn't start-up, look for the problem in the logs. You can
 find them in your Glassfish domain's  <FONT FACE="Courier New, monospace">logs</FONT>
 directory. The Glassfish log file is <FONT FACE="Courier New, monospace">server.log</FONT>
 and the Roller log  is <FONT FACE="Courier New, monospace">roller.log</FONT>.</SPAN></P>
-<H1 CLASS="western">8Getting started with Roller</H1>
+<H1 CLASS="western">9Getting started with Roller</H1>
 <P CLASS="western">You're not quite done with the installation
 process Now you're ready to start using Roller, so we'll walk you
 through getting started, registering a user and setting up a blog.
 We'll also discuss briefly what happens when there is an error. 
 </P>
-<H2 CLASS="western">8.1Navigate to Roller and finish the install 
+<H2 CLASS="western">9.1Navigate to Roller and finish the install 
 </H2>
 <P CLASS="western">Navigate to Roller, if you are using a default
 Tomcat or Glassfish installation then then URL of Roller is probably
@@ -647,22 +686,22 @@ you diagnose the problem. It's possible 
 JDBC driver class name, connection URL, username or password. Or
 perhaps your database is not running. Use the information provided to
 determine what is wrong, fix it and then redeploy Roller.</P>
-<P CLASS="western"><IMG SRC="file:///Users/dave/Source/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide_html_79ee0277.png" NAME="graphics7" ALIGN=LEFT WIDTH=581 HEIGHT=331 BORDER=0><BR CLEAR=LEFT><BR><BR>
+<P CLASS="western"><IMG SRC="roller-install-guide_html_79ee0277.png" NAME="graphics7" ALIGN=LEFT WIDTH=480 HEIGHT=273 BORDER=0><BR CLEAR=LEFT><BR><BR>
 </P>
 <H4 CLASS="western">Automatic tables creation</H4>
-<P CLASS="western"><IMG SRC="file:///Users/dave/Source/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide_html_2bf00c9b.png" NAME="graphics8" ALIGN=LEFT WIDTH=558 HEIGHT=127 BORDER=0><BR CLEAR=LEFT>If
+<P CLASS="western"><IMG SRC="roller-install-guide_html_2bf00c9b.png" NAME="graphics8" ALIGN=LEFT WIDTH=461 HEIGHT=105 BORDER=0><BR CLEAR=LEFT>If
 your database configuration is good but Roller cannot find its
 database tables, then Roller will offer to create those pages
 automatically for you. If you give the go-ahead, Roller will run the
 appropriate database creation script for your database and then show
 you the results. You can then proceed to the next step to setup your
 first user account and weblog.</P>
-<H2 CLASS="western">8.2Register a user and create a weblog</H2>
+<H2 CLASS="western">9.2Register a user and create a weblog</H2>
 <P CLASS="western">If Roller starts up fine but doesn't find a
 front-page weblog then it will display the Completing Your
 Installation below that explains how to register your first user,
 create your first weblog and setup your site's front page.</P>
-<P CLASS="western"><IMG SRC="file:///Users/dave/Source/roller_4.0/apps/weblogger/docs/installguide/generated/html/roller-install-guide_html_m8d76424.png" NAME="graphics9" ALIGN=LEFT WIDTH=527 HEIGHT=390 BORDER=0><BR CLEAR=LEFT><BR><BR>
+<P CLASS="western"><IMG SRC="roller-install-guide_html_m8d76424.png" NAME="graphics9" ALIGN=LEFT WIDTH=435 HEIGHT=322 BORDER=0><BR CLEAR=LEFT><BR><BR>
 </P>
 <P CLASS="western">You have to decide what you want as the front-page
 of your Roller site. If you are using Roller to run your personal
@@ -696,12 +735,12 @@ and ask your questions there:
 <A HREF="http://cwiki.apache.org/confluence/display/ROLLER/Roller+Mailing+Lists">http://cwiki.apache.org/confluence/display/ROLLER/Roller+Mailing+Lists</A><BR>
   
 </P>
-<H1 CLASS="western">9Configuration tips and tricks</H1>
+<H1 CLASS="western">10Configuration tips and tricks</H1>
 <P CLASS="western">This section covers some tips and tricks that can
 help you get the most out of Roller. It covers Roller's Planet feed
 aggregator, Acegi setup and how to setup Roller to use
 server-provided resources.</P>
-<H2 CLASS="western">9.1Setting up Roller's Planet feed aggregator</H2>
+<H2 CLASS="western">10.1Setting up Roller's Planet feed aggregator</H2>
 <P CLASS="western">Roller includes a RSS/Atom feed aggregator that
 makes it possible to run a site like <A HREF="http://blogs.sun.com/">http://blogs.sun.com</A>
 which provides weblogs for thousands of writers and an aggregated
@@ -793,7 +832,7 @@ at the following URLs:</SPAN></P>
 	<LI><P CLASS="western"><SPAN STYLE="background: #ffff00"><A HREF="http://localhost:8080/roller/rollerrss"><FONT COLOR="#000000"><SPAN STYLE="background: #ffffff">Per
 	group feed<BR></SPAN></FONT></A><A HREF="http://localhost:8080/roller/rollerrss"><FONT COLOR="#000000"><FONT FACE="Courier New, monospace"><SPAN STYLE="background: #ffffff">http://localhost:8080/roller/planetrss?group=&lt;group-name&gt;</SPAN></FONT></FONT></A></SPAN></P>
 </UL>
-<H2 CLASS="western">9.2Changing keys in security.xml</SPAN></H2>
+<H2 CLASS="western">10.2Changing keys in security.xml</SPAN></H2>
 <P CLASS="western">Starting with version 2.1, Roller uses the Acegi
 security infrastructure. Several of the security features rely on
 keys that are intended to be site-specific. These keys are used to
@@ -831,7 +870,7 @@ keys. 
 	</P>
 </OL>
 <H2 CLASS="western"></H2>
-<H2 CLASS="western" STYLE="page-break-before: always">9.3Using
+<H2 CLASS="western" STYLE="page-break-before: always">10.3Using
 Server-provided database and mail resources</H2>
 <P CLASS="western">It's easiest to setup the database connection
 using the 'jdbc' approach and the mail connection using 'properties'
@@ -914,7 +953,7 @@ path=&quot;/roller&quot; </FONT></FONT>
 </P>
 <P CLASS="western">Once your context.xml file is in place, deploy
 Roller to Tomcat as described in <B>Section 7</B>.</P>
-<H2 CLASS="western">9.4Manual table creation and upgrade</H2>
+<H2 CLASS="western">10.4Manual table creation and upgrade</H2>
 <P CLASS="western">If you would rather create your database tables
 yourself instead of letting Roller do it automatically, you can.
 Instead of enabling automatic installation you should disable it by
@@ -930,13 +969,13 @@ script for each of the databases we hope
 <P CLASS="western">And if you are upgrading Roller, you'll have to
 run the migration scripts. You'll find those under the <FONT FACE="Courier New, monospace">dbscripts</FONT>
 directory too.</P>
-<H1 CLASS="western">10Upgrading Roller</H1>
+<H1 CLASS="western">11Upgrading Roller</H1>
 <P CLASS="western">This section describes how to upgrade an existing
 Roller installation to the latest release of Roller by shutting down,
 backing up and then following the installation instructions with a
 couple of key exceptions. But first, there is some required reading
 for those upgrading from ancient versions of Roller.</P>
-<H2 CLASS="western">10.1For those upgrading from Roller 2.x to Roller
+<H2 CLASS="western">11.1For those upgrading from Roller 2.x to Roller
 4.0.1</H2>
 <P CLASS="western"><SPAN STYLE="background: transparent">Roller 3.0
 and Roller 4.0 were <I>major</I> releases and made some big changes
@@ -1021,7 +1060,7 @@ also been moved to the Roller Support pr
 to become part of a community maintained repository. If you or your
 users use any other themes, then you'll need to download and install
 them according to the instructions on that site.</SPAN></P>
-<H2 CLASS="western"><A NAME="ref-UpgradeGuide_2.1-1"></A>10.2Backup
+<H2 CLASS="western"><A NAME="ref-UpgradeGuide_2.1-1"></A>11.2Backup
 your old Roller 
 </H2>
 <P CLASS="western">Before you get started with your upgrade, shutdown
@@ -1056,7 +1095,7 @@ home directory under <FONT FACE="Courier
 so you'll have to copy your uploads there. If you want to change the
 location of the uploads directory, overload the property <FONT FACE="Courier New, monospace">upoads.dir</FONT>.</P>
 <H2 CLASS="western" STYLE="page-break-before: always"><A NAME="ref-UpgradeGuide_2.1-2"></A>
-10.3Install and startup the new Roller 
+11.3Install and startup the new Roller 
 </H2>
 <P CLASS="western">Follow the normal installation instructions for
 the new version of Roller, but...</P>
@@ -1079,7 +1118,7 @@ version to the new version of Roller.</P
 migration scripts yourself, you can. See <B>Section 9.4</B>.</P>
 <P CLASS="western"><B>NOTE</B>: On Tomcat, before startup you should
 delete the contents of the Tomcat work directory</P>
-<H1 CLASS="western">11roller.properties</H1>
+<H1 CLASS="western">12roller.properties</H1>
 <PRE><FONT FACE="Courier New"><FONT SIZE=1 STYLE="font-size: 8pt"># roller.properties</FONT></FONT>
 <FONT FACE="Courier New"><FONT SIZE=1 STYLE="font-size: 8pt">#</FONT></FONT>
 <FONT FACE="Courier New"><FONT SIZE=1 STYLE="font-size: 8pt"># This file is for meant for Roller deployment properties</FONT></FONT>

Modified: roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.pdf
URL: http://svn.apache.org/viewvc/roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.pdf?rev=1062150&r1=1062149&r2=1062150&view=diff
==============================================================================
Binary files - no diff available.

Modified: roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.txt
URL: http://svn.apache.org/viewvc/roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.txt?rev=1062150&r1=1062149&r2=1062150&view=diff
==============================================================================
--- roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.txt (original)
+++ roller/branches/roller_4.0/apps/weblogger/docs/installguide/generated/roller-install-guide.txt Sat Jan 22 13:10:36 2011
@@ -1,7 +1,4 @@
-
-
-
-
+
 
 
 
@@ -30,12 +27,10 @@ Installation Guide
 
 
 
-
-
 Apache Roller Weblogger
-Version 4.0 
-August 2007
-
+Version 4.0.1
+January 2011 
+ 
 Table of Contents
 1   Overview	3
 1.1   Copyright and trademark information	3
@@ -72,28 +67,28 @@ Table of Contents
 10.3   Install and startup the new Roller 	20
 11   roller.properties	21
 
-1Overview
+1 Overview
 This document describes how to install the Apache Roller Weblogger software. It explains what you need to install first, how to download Roller, how to configure Roller and how to install it to your existing Java application server and relational database. If also offers a 5-minute install option   for more advanced folks.
-1.1Copyright and trademark information
+1.1 Copyright and trademark information
 The contents of this document are subject to the terms of the Apache Software License.
 
 All trademarks within this document belong to legitimate owners.
 
-1.2Feedback
+1.2 Feedback
 Please direct any comments or suggestions about this document to: user@roller.apache.org
 
-1.3Acknowledgments
+1.3 Acknowledgments
 The original version of this document was written by Dave Johnson. The document is currently written and updated by the Apache Roller project of the Apache Software Foundation.
 
 The general format of this document was based on the documentation template used by the OpenDS project which in turn was based on the templates used by the OpenOffice.org project.
 
-1.4Modifications and Updates
+1.4 Modifications and Updates
 Date
 Description of Change
 July 2007
 Rewritten for simplified Roller 4.0 installation process
 
-2The 5-minute install
+2 The 5-minute install
 If you really know what you're doing, you just want to get Roller up-and-running for a quick evaluation and you are using a well-supported platform (e.g. Tomcat and MySQL), you can probably get up and running in about 5-minutes by following the simple instructions on this page. If you're not so confident, then skip this page and go on to Section 3. Here's what you do for the 5-minute install:
 
 STEP 1: Download Roller and un-package into a directory on your disk via Zip or GNU Tar.
@@ -121,17 +116,23 @@ STEP 4: Check your Servlet container's J
 STEP 5: Deploy Roller to your Servlet container using your container's Admin Console deploy Roller as a directory. The Roller WAR directory is in the installation directory under webapp/roller.
 STEP 6: Browse to Roller and get Rollin' (probably at http://localhost:8080/roller). If Roller is up and running, then proceed to Section 8 Getting started with Roller. If Roller isn't up and running and you can 't figure out why, then try the normal installation procedure starting with Section 3 below. 
 
-3Ready to roll?
+3 Securing Roller
+Security should be top-of-mind when setting up any web site, even one that is on a private network and internal to your organization. Here are some recommendations for keeping your Roller installation secure:
+Perform Roller installation on a secure network. When you are installing Roller it is possible for other users to interfere with your installation. If other users have access to the server, one of them could create the admin account before you do. So, when you install Roller, do so on a server that cannot be accessed by others.
+Do not allow open registration of new users. Roller can offer a registration link so that new users can register themselves, but this feature is turned off because it is not safe to allow just anybody to register for an account on your blog server. If you want to turn it on, login as an administrative user, go to Roller's Server Administration page and enable the Allow New Users option.
+Do not allow HTML in comments. Roller can allow users to write comments in a safe-subset of HTML, but HTML use in comments is not allowed at all because of security concerns with even a so called safe-subset of HTML. If you want to turn it on, login as an administrative user, go to Roller's Server Administration page, enable the Allow html in comments option and make sure the HTML Subset Restriction box is checked.
+Run Roller over SSL connection. If you run Roller over a plain old HTTP connection, it is possible for others to snoop your password when you login, for example over an open WIFI network. Instead, you should consult your Java Application Server's documentation and configure your Roller installation to run via HTTPS only. 
+4 Ready to roll?
 First, let's make sure you have everything you need to install and run Roller.
 Roller is a database-driven Java web application. To run it you need Java, a Java Servlet container such as Tomcat and a database such as MySQL. More specifically, here's what you need to install and run Roller:
 The Java development kit, specifically the Sun Java 2 SE 1.5 JDK. The computer on which you install Roller should be configured to run with the Java SE 5. Roller 3.x was the last major Roller release to support Java 1.4.2.
 A Java application server, or more specifically a Servlet container that supports the Servlet 2.4 API. Hereinafter, we'll just call this your server. The Roller community tends to use and is best able to answer questions about Tomcat 5.5, Tomcat 6.0, Sun Web Server 7.0 and Glassfish 2.0. 
 A relational database such as MySQL or Apache Derby. The Roller community tends to use and is best able to answer questions about MySQL and Apache Derby, but it is possible to use other databases with Roller. Roller includes database creation scripts for DB2, Derby, HSQL-DB, Microsoft SQL Server, MySQL, Oracle and PostgreSQL.
 If you're using Tomcat, check the Tomcat Considerations section below, otherwise you are ready to move on to Section 4: Download and un-package Roller.
-3.1Tomcat: JavaMail and Activation
+4.1 Tomcat: JavaMail and Activation
 Tomcat does not include the Java Mail and Activation jars that Roller needs for email notification, So, if you like to use Roller's e-mail notification features, you'll need to download those jars and place them in Tomcat's classpath. Download them from Sun (http://java.sun.com/products/javamail) and place them in Tomcat's common/lib directory.
-3.2Tomcat: URI encoding needed for I118N
-Roller supports internationalization (I18N), but on Tomcat some additional configuration is necessary. You must ensure that Tomcat's URI encoding is set to UTF-8. You can do this by editing the Tomcat configuration file conf/server.xml and adding URIEncoding="UTF-8" to each connector element, as shown below:
+4.2 Tomcat: URI encoding needed for I118N
+Roller supports internationalization (I18N), but on Tomcat some additional configuration is necessary. You must ensure that Tomcat's URI encoding is set to UTF-8. You can do this by editing the Tomcat configuration file conf/server.xml and adding URIEncoding=”UTF-8” to each connector element, as shown below:
    <Connector port="8080"
       maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
       enableLookups="false" redirectPort="8443" debug="0" 
@@ -140,23 +141,23 @@ Roller supports internationalization (I1
       URIEncoding="UTF-8" />
 
 And make sure you do this for every connector through which you use Roller. For example, if you use the AJP connector or HTTPS connector you need to add the URIEncoding="UTF-8" attribute to those connectors as well.
-4Download and un-package Roller
+5 Download and un-package Roller
 Download the Apache Roller release file from http://roller.apache.org. If you're a Windows user download the .zip file and use your favorite ZIP program to unzip the release into a directory on your computer's disk. Unix users can download the .tar.gz file and use GNU tar to un-package. 
-4.1Installation directory layout
+5.1 Installation directory layout
 Once you've unpackaged the files you'll find a directory structure like this:
 
 The LICENCE.txt and NOTICE.txt files contain the Apache Software License and other legal notices related to the release. The README.txt file just points to the documentation in the docs directory.
-4.2The Roller Weblogger WAR 
+5.2 The Roller Weblogger WAR 
 The Roller Weblogger application itself is in the directory webapp/roller and is organized using the standard Java EE WAR directory structure. Generally speaking, you won't need to modify any files in side the director. You can deploy it as is, in directory form, or you can package it up as a .war if you prefer to deploy as a file.
 For example, here's how you'd package it up as a WAR:
    % cd apache-roller-X.0/webapp/roller
    % jar cvf ../roller.war *
 
-5Prepare your database for Roller
+6 Prepare your database for Roller
 Before you can install Roller you'll probably need to some work to prepare your database for Roller. 
 You need some place to put the Roller tables. Some folks call this a table-space, but we refer to it as a database. You need to create a database for Roller, or get your database administrator to do it for you. And second, you need to have a JDBC driver installed for you database of choice.
 If you're installing on Glasfish and using it's built-in JavaDB/Derby database, you can skip this section; there's no need to create a database in Derby and Glassfish already includes the Derby JDBC driver.
-5.1Create a database for Roller 
+6.1 Create a database for Roller 
 If you're luck enough to have your own database administrator, ask them to setup a database for Roller. When they are done, ask them to provide you with this information, you'll need it later:
 Username and password for connecting to database
 JDBC connection URL for database
@@ -167,9 +168,9 @@ If you don't have a database administrat
    mysql> create database rollerdb;
    mysql> grant all on rollerdb.* to scott@'%' identified by 'tiger';
    mysql> grant all on rollerdb.* to scott@localhost identified by 'tiger';
-5.2Check your JDBC driver setup
+6.2 Check your JDBC driver setup
 Make sure that you have the correct JDBC driver installed in your server. Usually, this is as simple as downloading the JDBC driver jar(s) and placing it (or them) into your server's classpath. For example, on Tomcat 5.5 you place them in common/lib, on Tomcat 6.0 in lib and on Glassfish in your domain's lib directory. 
-5.3MySQL and Oracle considerations
+6.3 MySQL and Oracle considerations
 Based on our experience supporting MySQL, we have the following recommendations:
 For MySQL, make sure that TCP/IP networking is enabled. 
 For MySQL 4.1.x use the J/Connector 3.0.X JDBC drivers instead of the newer 3.1.X series.
@@ -177,7 +178,7 @@ For MySQL 5.X use the J/Connector 3.1.X 
 Make sure you enable MySQL's UTF-8 support. See this page for details:
 http://rollerweblogger.org/wiki/Wiki.jsp?page=SetupUTF8onMySQL 
 For Oracle users, use the 10g (10.1.0.2 higher) drivers which should be packaged as ojdbc14.jar, even if operating on Oracle 9 server.
-6Configure Roller
+7 Configure Roller
 It is possible for you to configure Roller by creating and editing only one file:
    roller-custom.properties
 That file is a simple Java properties file, a text file that overrides settings defined in Roller's internal roller.properties file. To configure Roller you look at Roller's internal properties file, decide which properties you need to override and then set those in your roller-custom.properties file.
@@ -190,10 +191,10 @@ Create a text file named roller-custom.p
    database.jdbc.username=database username
    database.jdbc.password=database password
    mail.configurationType=properties
-   mail.hostName=mail server hostname
+   mail.hostname=mail server hostname
 
-The installation.type=auto property tells Roller to operate in automatic installation mode. In this mode Roller will provide very detailed error output to help you debug database connection problems. If Roller finds that the database exists but its tables are not, it will offer to run the database creation scripts. If find finds that the tables are there, but they are not up-to-date Roller will offer to upgrade them for you. Once your Roller installation is complete and you are ready to go "live" then you should set installation.type=manual.
-6.1MySQL example
+The installation.type=auto property tells Roller to operate in automatic installation mode. In this mode Roller will provide very detailed error output to help you debug database connection problems. If Roller finds that the database exists but its tables are not, it will offer to run the database creation scripts. If find finds that the tables are there, but they are not up-to-date Roller will offer to upgrade them for you. Once your Roller installation is complete and you are ready to go “live” then you should set installation.type=manual.
+7.1 MySQL example
 Here is an example roller-custom.properties file that shows how to setup a MySQL connection. It shows the MySQL JDBC driver class name, an example MySQL connection URL and username/password settings for the mail connection.
    installation.type=auto
    database.configurationType=jdbc
@@ -202,20 +203,20 @@ Here is an example roller-custom.propert
    database.jdbc.username=scott
    database.jdbc.password=tiger
    mail.configurationType=properties
-   mail.hostName=smtp-server.example.com
+   mail.hostname=smtp-server.example.com
    mail.username=scott
    mail.password=tiger
 
 Next, we'll deploy Roller.
-7Deploy Roller
+8 Deploy Roller
 Now that you've got the Roller WAR and you've created your roller-custom.properties file, you're ready to deploy Roller to your server. First, deploy your properties file.
-7.1Put roller-custom.properties in classpath
+8.1 Put roller-custom.properties in classpath
 Roller can look for your properties file in a number of ways and you can see Section 11 for details. The simplest thing for you to do is to place the file in your application server's classpath, by dropping it into a classes directory. On startup, Roller will find it there. Here's how to do it on some popular servers:
 On Tomcat 5.5, copy the file into Tomcat's common/classes directory.
 On Tomcat 6.0, copy it into Tomcat's lib directory.
 On Glassfish, copy can copy it to your domain's lib/classes directory.
 Now you're ready to deploy Roller itself.
-7.2Deploy Roller via administration console
+8.2 Deploy Roller via administration console
 Use your server's administration console to deploy the Roller web application. 
 You can deploy as a directory, in which case you'll have to enter the path to your Roller installation's webapp/roller directory. Or you can deploy as a WAR file, in which case you will have to have created a WAR file as we described in Section 4.2. 
 Let's discuss how to do that for Tomcat 6.0 and Glassfish v2.0.
@@ -230,51 +231,58 @@ You can also deploy to Glassfish as eith
 
 Once Roller is deployed, you'll see that it's listed among the other applications. There's a Launch link to Roller itself and there are buttons to enable, display and redeploy.
 If Roller doesn't start-up, look for the problem in the logs. You can find them in your Glassfish domain's  logs directory. The Glassfish log file is server.log and the Roller log  is roller.log.
-8Getting started with Roller
+9 Getting started with Roller
 You're not quite done with the installation process Now you're ready to start using Roller, so we'll walk you through getting started, registering a user and setting up a blog. We'll also discuss briefly what happens when there is an error. 
-8.1Navigate to Roller and finish the install 
+9.1 Navigate to Roller and finish the install 
 Navigate to Roller, if you are using a default Tomcat or Glassfish installation then then URL of Roller is probably http://localhost:8080/roller. You will see either a web page of error messages, a web page offering to create database tables for you or web page asking you to complete the installation by registering an admin user and creating a front-page blog. First, let's talk about what happens when things go wrong.
 If there's a problem with your database configuration, Roller will display a page or error messages to help you diagnose the problem. It's possible that you entered the wrong JDBC driver class name, connection URL, username or password. Or perhaps your database is not running. Use the information provided to determine what is wrong, fix it and then redeploy Roller.
 
 Automatic tables creation
 If your database configuration is good but Roller cannot find its database tables, then Roller will offer to create those pages automatically for you. If you give the go-ahead, Roller will run the appropriate database creation script for your database and then show you the results. You can then proceed to the next step to setup your first user account and weblog.
-8.2Register a user and create a weblog
+9.2 Register a user and create a weblog
 If Roller starts up fine but doesn't find a front-page weblog then it will display the Completing Your Installation below that explains how to register your first user, create your first weblog and setup your site's front page.
 
 You have to decide what you want as the front-page of your Roller site. If you are using Roller to run your personal weblog, then you probably want your weblog to be the front-page of the site. In this case, create a weblog for yourself, don't choose the front-page theme but do set your weblog as the front-page weblog for the site. 
-If you are using Roller to run a community of multiple weblogs, then you'll probably want to display an aggregated front-page combining all weblogs on the site. In that case, create a weblog to serve as the front-page, set it as the front-page weblog and make sure you set the "aggregated front-page" setting on the Server Admin page.   
+If you are using Roller to run a community of multiple weblogs, then you'll probably want to display an aggregated front-page combining all weblogs on the site. In that case, create a weblog to serve as the front-page, set it as the front-page weblog and make sure you set the “aggregated front-page” setting on the Server Admin page.   
 Don't forget: Reset the installation.type flag
 Now that you're done with the installation you should turn off Roller's auto-installation system. Edit your roller-custom.properties file and set installation.type=manual. Then restart your server or Roller so that it accepts the new setting.
 What's next?
 Once you've gotten Roller up and running refer to the Roller User Guide for more information on running your Roller system and your weblog. For information on customizing your weblog, refer to the Roller Template Guide. If you can't find what you want in the documentation then subscribe to the Roller user mailing list and ask your questions there: http://cwiki.apache.org/confluence/display/ROLLER/Roller+Mailing+Lists
    
-9Configuration tips and tricks
+10 Configuration tips and tricks
 This section covers some tips and tricks that can help you get the most out of Roller. It covers Roller's Planet feed aggregator, Acegi setup and how to setup Roller to use server-provided resources.
-9.1Setting up Roller's Planet feed aggregator
+10.1 Setting up Roller's Planet feed aggregator
 Roller includes a RSS/Atom feed aggregator that makes it possible to run a site like http://blogs.sun.com which provides weblogs for thousands of writers and an aggregated front-page that displays the most recent posts form those plus dozens of Sun bloggers from other sites such as blogger.com, typepad.com and other services. Here's what you need to do.
 STEP 1: Create a Planet cache directory
 Roller Planet needs a cache directory in which to store the feeds it fetches. By default, Roller Planet will put it's cache in your home directory under roller_data/planetcache. If you want to place the cache somewhere else, you must override the planet.aggregator.cache.dir property in your roller-custom.properties file. For example:
     planet.aggregator.cache.dir=c:\\roller_data\planetcache
 
 Whether you override that property or not, you must create the cache directory. Planet will not work unless the cache directory exists and is writable by Roller.
-STEP 2: Enable Planet Roller properties
+STEP 2: Enable Planet via Roller custom properties
 Enable Planet by adding the following to your roller-custom.properties file:
    planet.aggregator.enabled=true
 
    # Tasks which are enabled.  Only tasks listed here will be run.
    tasks.enabled=ScheduledEntriesTask,ResetHitCountsTask,\
-   TurnoverReferersTask,PingQueueTask,RefreshPlanetTask,SyncWebsitesTask
+   TurnoverReferersTask,PingQueueTask,RefreshRollerPlanetTask,SyncWebsitesTask
    
    # Set of page models specifically for site-wide rendering
    rendering.siteModels=\
    org.apache.roller.weblogger.ui.rendering.model.SiteModel,\
    org.apache.roller.weblogger.ui.rendering.model.PlanetModel
 
-Those property settings enable Planet and enable the Planet tasks, both the RefreshPlanetTask, which runs every hour and fetches all RSS/Atom feed subsciptions, and the SyncWebsitesTask, which runs every midnight and ensures that each weblog in the Roller system is represented by a subscription in the Planet aggregator. To enable usage of the PlanetModel in the front-page weblog, we also override the rendering.siteModels property.
+Those property settings enable Planet and enable the Planet tasks, both the RefreshRollerPlanetTask, which runs every hour and fetches all RSS/Atom feed subsciptions, and the SyncWebsitesTask, which runs every midnight and ensures that each weblog in the Roller system is represented by a subscription in the Planet aggregator. To enable usage of the PlanetModel in the front-page weblog, we also override the rendering.siteModels property.
+
+
+STEP 3: Configure Planet via Planet custom properties
+Create a new file called planet-custom.properties and place it in the same directory as your existing roller-custom.properties file. Here's what you need to put in this configuration file:
+1. The exact same database properties that you put in your Roller custom properties file.
+2. Add a property called cache.dir that points to the directory that you'd like Planet to use for caching it's RSS and Atom newsfeeds. The default setting is:
+     cache.dir=${user.home}/roller_data/planetcache
 Once you've made those property settings restart Roller and proceed to the next step.
-Display your Planet aggregations
+STEP 4: Display your Planet aggregations
 You can use Roller's UI to add external RSS/Atom feeds to the Planet setup. To display these feeds you'll need to do a little template customization. The easier way to get started is to Roller's existing Front-Page theme. Here's how.
-Create a weblog to server as the front-page of your Roller site. Start with the Front-Page theme and customize it. Edit the weblog template and look for the part that mentions PLANET-entries. Comment-out the SITE-WIDE part and un-comment the PLANET-entries part. The double hash "##" marks indicate a commented-out line. The code should look like this:
+Create a weblog to server as the front-page of your Roller site. Start with the Front-Page theme and customize it. Edit the weblog template and look for the part that mentions PLANET-entries. Comment-out the SITE-WIDE part and un-comment the PLANET-entries part. The double hash “##” marks indicate a commented-out line. The code should look like this:
 
    ## 1) SITE-WIDE entries (the default)
    ##set($pager = $site.getWeblogEntriesPager($since, $maxResults))
@@ -287,14 +295,14 @@ Main Planet feed
 http://localhost:8080/roller/planetrss
 Per group feed
 http://localhost:8080/roller/planetrss?group=<group-name>
-9.2Changing keys in security.xml
+10.2 Changing keys in security.xml
 Starting with version 2.1, Roller uses the Acegi security infrastructure. Several of the security features rely on keys that are intended to be site-specific. These keys are used to compute HMAC (hash-based message authentication code) values for Remember Me cookies. Knowledge of these keys could allow an attacker to forge invalid cookies, and thereby gain unauthorized access to your Roller installation (at the application level). 
 Roller ships with default values, and these should assumed to be widely known. You should change your keys to be secret values specific to your own site (the reason you should change the anonymous provider key is that a granted authorities list is embedded within the anonymous authentication token). Here is how to change the keys. 
-1.Find your WEB-INF/security.xml file and open it in a text editor.
-2.For the beans with ids "anonymousAuthenticationProvider" and "anonymousProcessingFilter" change the value field of the property with name="key" to be different from the default value of "anonymous". You can use any string value of your choosing. It should be a secret specific to your site. Use the same key value in these two beans; they must match.
-3.For the beans with ids "rememberMeServices" and "rememberMeAuthenticationProvider" change the value field of the property with name="key" to be different from the default value of "rollerlovesacegi". You can use any string value of your choosing. It should be a secret specific to your site. Use the same key value in these two beans; they must match 
+1. Find your WEB-INF/security.xml file and open it in a text editor.
+2. For the beans with ids "anonymousAuthenticationProvider" and "anonymousProcessingFilter" change the value field of the property with name="key" to be different from the default value of "anonymous". You can use any string value of your choosing. It should be a secret specific to your site. Use the same key value in these two beans; they must match.
+3. For the beans with ids "rememberMeServices" and "rememberMeAuthenticationProvider" change the value field of the property with name="key" to be different from the default value of "rollerlovesacegi". You can use any string value of your choosing. It should be a secret specific to your site. Use the same key value in these two beans; they must match 
 
-9.3Using Server-provided database and mail resources
+10.3 Using Server-provided database and mail resources
 It's easiest to setup the database connection using the 'jdbc' approach and the mail connection using 'properties' but in some cases you might want to use the datasource and mail session resources provided by your application server instead. You might do this for a couple of reasons, for example you might want to take advantage of the database connection pool management that is built into your server. Or, your boss might want everything to be managed via your server's Admin Console. No matter the reason, it's easy to do in Roller.
 Instead of setting up your database and mail connections in roller-custom.properties like this:
    installation.type=auto
@@ -338,37 +346,40 @@ Before you deploy Roller to Tomcat, crea
     </Context>
 
 Once your context.xml file is in place, deploy Roller to Tomcat as described in Section 7.
-9.4Manual table creation and upgrade
+10.4 Manual table creation and upgrade
 If you would rather create your database tables yourself instead of letting Roller do it automatically, you can. Instead of enabling automatic installation you should disable it by putting this in your roller-custom.properties file:
     installation.type=manual
 
 Now you've got to run the database creation script. You can find the database creation scripts in the webapp/roller/WEB-INF/classes/dbscripts directory. You'll find a createdb.sql script for each of the databases we hope to support.
 And if you are upgrading Roller, you'll have to run the migration scripts. You'll find those under the dbscripts directory too.
-10Upgrading Roller
+11 Upgrading Roller
 This section describes how to upgrade an existing Roller installation to the latest release of Roller by shutting down, backing up and then following the installation instructions with a couple of key exceptions. But first, there is some required reading for those upgrading from ancient versions of Roller.
-10.1For those upgrading from Roller 2.x to Roller 4.0
+11.1 For those upgrading from Roller 2.x to Roller 4.0.1
 Roller 3.0 and Roller 4.0 were major releases and made some big changes to the way that Roller works. If you're upgrading from the 2.x series you need to be aware of them and especially the new URL structure and the new template system.
 New URL structure
-The most significant change is the new URL structure - we've completely change all of the Roller weblog URLs. We continue to support old Roller URLs, but they are forwarded to the new system. That ensures that nobody will get a 404 when accessing your weblog using an old URL, but you'll still want to encourage people to change links that point to your weblog's old URL, which was of the format:
+The most significant change is the new URL structure – we've completely change all of the Roller weblog URLs. We continue to support old Roller URLs, but they are forwarded to the new system. That ensures that nobody will get a 404 when accessing your weblog using an old URL, but you'll still want to encourage people to change links that point to your weblog's old URL, which was of the format:
 	http://<hostname>/roller/page/<weblog-handle>
 To use the new format, which is:
 	http://<hostname>/roller/<weblog-handle>
 Unfortunately, some custom templates that use relative URLs will have problem with this new URL structure. So, before you go live you should set-up a test server and allow your users to take a look at their weblogs.
 New template system
 We've developed a completely new and greatly improved template system for Roller, which includes new models and new macros. We want to encourage people to start using this new system for all new template and theme development, so we have made it the default. And, by default, we've turned off the old system. 
-So, if you are upgrading and you want your weblogs to work, you must override this Roller property to enable the old "legacy" template system to work:
+So, if you are upgrading and you want your weblogs to work, you must override this Roller property to enable the old “legacy” template system to work:
 	rendering.legacyModels.enabled=true
 See Section 11 for information on overriding Roller startup properties.
 New task management system
 In Roller 3.1 we changed the scheduled task properties, so if you were overriding  the tasks.daily or tasks.hourly properties you need to change your roller-custom.properties file. Refer to the notes in Section 11   roller.properties in the Scheduled Tasks Configuration area.
 New package names
 In Roller 3.0 or package names went from from org.roller to org.apache.roller. In Roller 4.0 they've changed again to org.apache.roller.weblogger. So check your configuration files for references to the old package names. And if you created any plugins, you'll have to recompile them against the new code base.
+Encrypted passwords now the default
+Roller now defaults to storing passwords in the database in an emcrypted format. So, if you are upgrading an older version of Roller and you went with the default setting for encrypted passwords, which was off by default, then you'll need to set this propery in your roller-custom.properties file:
+	passwds.encryption.enabled=false
 Non-core themes removed
 The Roller project is establishing a community site for sharing and maintaining of themes and plugins. 
 From now only, Roller will ship with only a core set of four themes (Basic, BrushedMetal, Sotto and a new Frontpage themes, which is just for site-wide front-page weblogs) . All other themes have been removed from Roller and moved to the Roller Support project at Java.net (http://roller.dev.java.net). If you or your users use any other themes, then you'll need to download and install them according to the instructions on that site.
 Non-core plugins removed
 The same applies to plugins. The JSPWiki, Textile and Read More plugins have also been moved to the Roller Support project at Java.net (http://roller.dev.java.net) to become part of a community maintained repository. If you or your users use any other themes, then you'll need to download and install them according to the instructions on that site.
-10.2Backup your old Roller 
+11.2 Backup your old Roller 
 Before you get started with your upgrade, shutdown your existing Roller install and make a backup of your Roller data. 
 Backup your database to somewhere safe on your system or to a remote file-system. Here are a couple of examples: of how to do that on various databases:
 On MySQL you create a dump file
@@ -379,14 +390,14 @@ And backup any other data. Make a copy o
 Don't store files inside of Roller
 If you do, you'll have to move them around on every Roller upgrade. Put your uploads and themes in a separate directory and point to them via the upoads.dir and themes.dir properties.
 If you're upgrading from an older version of Roller you may have been storing uploaded files inside the Roller web application, in a /resources subdirectory. In Roller 4.0 the default is to store those files your home directory under roller_data/uploads, so you'll have to copy your uploads there. If you want to change the location of the uploads directory, overload the property upoads.dir.
-10.3Install and startup the new Roller 
+11.3 Install and startup the new Roller 
 Follow the normal installation instructions for the new version of Roller, but...
-When creating your roller-custom.properites, copy of your old one. Carefully review each property and compare it to the property settings in the Roller 4.0 property file in Section 11. 
+When creating your roller-custom.properties, copy of your old one. Carefully review each property and compare it to the property settings in the Roller 4.0 property file in Section 11. 
 Don't create a new database for Roller. Instead point Roller to your existing Roller database. This is completely safe because you created a backup of your database (right?).
 When you deploy and startup, Roller will detect that your database needs to be upgraded and it will offer to run each of the migrations scripts necessary to upgrade you from your old version to the new version of Roller.
 NOTE: if you would rather run the database migration scripts yourself, you can. See Section 9.4.
 NOTE: On Tomcat, before startup you should delete the contents of the Tomcat work directory
-11roller.properties
+12 roller.properties
 # roller.properties
 #
 # This file is for meant for Roller deployment properties
@@ -1076,4 +1087,4 @@ webservices.adminprotocol.enabled=false
 
 # If you are using the Hibernate backend (deprecated as of Roller 4.0), 
 # you MUST override this to use a database other than MySQL4
-hibernate.dialect=org.hibernate.dialect.MySQLDialect
\ No newline at end of file
+hibernate.dialect=org.hibernate.dialect.MySQLDialect

Modified: roller/branches/roller_4.0/apps/weblogger/docs/installguide/roller-install-guide.odt
URL: http://svn.apache.org/viewvc/roller/branches/roller_4.0/apps/weblogger/docs/installguide/roller-install-guide.odt?rev=1062150&r1=1062149&r2=1062150&view=diff
==============================================================================
Binary files - no diff available.

Modified: roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/config/runtimeConfigDefs.xml
URL: http://svn.apache.org/viewvc/roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/config/runtimeConfigDefs.xml?rev=1062150&r1=1062149&r2=1062150&view=diff
==============================================================================
--- roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/config/runtimeConfigDefs.xml (original)
+++ roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/config/runtimeConfigDefs.xml Sat Jan 22 13:10:36 2011
@@ -156,7 +156,7 @@
       </property-def>
       <property-def  name="users.comments.htmlenabled"  key="configForm.commentHtmlAllowed">
          <type>boolean</type>
-         <default-value>true</default-value>
+         <default-value>false</default-value>
       </property-def>
       <property-def  name="users.comments.plugins"  key="configForm.commentPlugins">
          <type>string</type>

Modified: roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/ui/struts2/core/Register.java
URL: http://svn.apache.org/viewvc/roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/ui/struts2/core/Register.java?rev=1062150&r1=1062149&r2=1062150&view=diff
==============================================================================
--- roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/ui/struts2/core/Register.java (original)
+++ roller/branches/roller_4.0/apps/weblogger/src/java/org/apache/roller/weblogger/ui/struts2/core/Register.java Sat Jan 22 13:10:36 2011
@@ -77,10 +77,19 @@ public class Register extends UIAction i
     @SkipValidation
     public String execute() {
         
-        if(!WebloggerRuntimeConfig.getBooleanProperty("users.registration.enabled")) {
+        // if registation is disabled, then don't allow registration
+        try {
+            if (!WebloggerRuntimeConfig.getBooleanProperty("users.registration.enabled")
+                // unless there are 0 users (need to allow creation of first user)
+                && WebloggerFactory.getWeblogger().getUserManager().getUserCount() != 0) {
+                return "disabled";
+            }
+        } catch (Exception e) {
+            log.error("Error checking user count", e);
             return "disabled";
         }
-        
+
+       
         // set some defaults
         getBean().setLocale(Locale.getDefault().toString());
         getBean().setTimeZone(TimeZone.getDefault().getID());



Mime
View raw message