I had a problem like that when first installed Roller. I changed this
element in the roller.properties file.
# The directory in which Roller will upload files
uploads.dir=${user.home}/appservers/roller_data/uploads
using the default ${user.home}/roller_data/uploads Roller was trying to
write to an area that was write protected. I was sitting behind an Apache
Http Server and my root context was the Apache Http Server.
It turned out the directory was write protected. I was getting a wierd
errors like can't log-in because I didn't have the correct user permissions.
So I added an additional appservers directory to the roller.properties
files. directory where my Tomcat installation was. That seem to solve the
problem.
From: kiwi2 <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: New installation problem
Date: Thu, 19 Jul 2007 23:45:13 -0700 (PDT)
Leon Messerschmidt-2 wrote:
>
> It could be a number of things. Anything in the log files that could
> help?
>
Leon,
The only Warn messages in the roller log are:
EhCacheProvider:buildCache - Could not find configuration... and using
defaults
NEW:
WARN 2007-07-20 01:39:56,171 PingQueueProcessor:processQueue - WARNING:
Skipping current ping queue processing round because we cannot yet
determine
the site's absolute context url.
This is the key - where did I go wrong setting the context URL?
Tony
--
View this message in context:
http://www.nabble.com/New-installation-problem-tf4112627s12275.html#a11702633
Sent from the Roller - User mailing list archive at Nabble.com.
_________________________________________________________________
http://im.live.com/messenger/im/home/?source=hmtextlinkjuly07
