Apache Roller
  1. Apache Roller
  2. ROL-952

Installation problems with 2.0-incubating

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Fedora Core 4, PostgreSQL 8
    • Browser Version:
      Firefox
    • Database:
      PostgreSQL 8
    • JDK Version:
      1.5
    • O/S Version:
      Fedora Core 4

      Description

      After getting everything working with the database, I'm unable to get to the admin screens to add a user. They (correctly) ask for a password, but rolleruser is empty. I presume this is an unintentional issue with a fresh install.

        Activity

        Brian Topping made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Mark Thomas made changes -
        Reporter Brian Topping [ roller_topping ] Brian Topping [ topping ]
        Hide
        Mark Thomas added a comment -

        Bulk change of reporter as per INFRA-3803

        Show
        Mark Thomas added a comment - Bulk change of reporter as per INFRA-3803
        Mark Thomas made changes -
        Workflow jira [ 12458672 ] Default workflow, editable Closed status [ 12622205 ]
        David Johnson made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        David Johnson added a comment -

        No longer relevant. Installation and database setup rewritten in 4.0.

        Show
        David Johnson added a comment - No longer relevant. Installation and database setup rewritten in 4.0.
        Henri Yandell made changes -
        Project Import Fri Mar 27 23:38:16 PDT 2009 [ 1238222296558 ]
        David Johnson made changes -
        Field Original Value New Value
        Assignee David Johnson [ djohnson ] Roller Unassigned [ roller_unassigned ]
        Hide
        roller_topping added a comment -

        This was apparently because the site did not initialize correctly. Without looking at the code, it took about ten hours to get things running. About half of this was due to faulty configuation on the database, but after that, the site would partially render, giving very little indication that anything was wrong. The logs told otherwise, but because the data directory permissions were not setup correctly, the database was initialized into a halfway usable state and left.

        My suggestion would be that the database version key is not written unless the database is fully set up. If it is not set up, don't render a half-correct screen for the user, render big stinking stack traces so that the user can see what's ailing them.

        Show
        roller_topping added a comment - This was apparently because the site did not initialize correctly. Without looking at the code, it took about ten hours to get things running. About half of this was due to faulty configuation on the database, but after that, the site would partially render, giving very little indication that anything was wrong. The logs told otherwise, but because the data directory permissions were not setup correctly, the database was initialized into a halfway usable state and left. My suggestion would be that the database version key is not written unless the database is fully set up. If it is not set up, don't render a half-correct screen for the user, render big stinking stack traces so that the user can see what's ailing them.
        roller_topping created issue -

          People

          • Assignee:
            Roller Unassigned
            Reporter:
            Brian Topping
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development