[ 
https://issues.apache.org/jira/browse/ROL-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Mazza closed ROL-1437.
---------------------------

    Resolution: Cannot Reproduce

Problem no longer exists today (was fixed in some earlier version.)  If you try 
to run Roller without read-access to the roller-data directory, you'll get a 
"directory doesn't exist" output in your roller.log file:

Caused by: org.apache.roller.weblogger.business.FileNotFoundException: Invalid 
path [/home/gmazza/roller_data/mediafiles2/gmazza], directory doesn't exist.
        at 
org.apache.roller.weblogger.business.FileContentManagerImpl.getRealFile(FileContentManagerImpl.java:389)
        at 
org.apache.roller.weblogger.business.FileContentManagerImpl.canSave(FileContentManagerImpl.java:213)
        ... 122 more

The roller.log place is precisely the place to look for system-level startup 
exceptions such as these.

                
> Problem to register the first user after the installation using MySQL 5.0.33 
> Database
> -------------------------------------------------------------------------------------
>
>                 Key: ROL-1437
>                 URL: https://issues.apache.org/jira/browse/ROL-1437
>             Project: Roller
>          Issue Type: Bug
>          Components: Authentication, Roles and Access Controls
>    Affects Versions: 3.1
>         Environment: Solaris for SPARC ver. 10 on Sun Fire V210
> Sun JES WebServer ver. 7.0
> MySQL ver. 5.0.33, MySQL JDBC connector ver. 5.0.6
> JDK 1.5
>            Reporter: Konstantin Lovtsky
>            Assignee: Roller Unassigned
>
> Roller 3.1 was installed for testing purposes.
> The following message is received when I started for the first time the 
> Roller and when I attempted to register the first user (super user):
> "I'm sorry, but the administrator of this site has turned off new user 
> registrations."
> The same problem as ROL-1278, but MySQL 5 with JDBC 5.0.6 is used (not Oracle 
> as in ROL-1278).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to