Charles L Bombard wrote: > Ok I do not understand what is going on. I try to run the dbinstall from > the data package and it is erroring when it tries to run repligard, state > that it is unable to login into the database.
When you configure the data package, make sure you supply the correct username/password if it is different from the default 'midgard'/'midgard'. See also $ ./configure --help in the data package directory. > I edited the script to use the > conf file that I created for the repligard portion of my original site > update (creating the missing GUIDS). It will run after this change. The > reason I am confused is that it is creating the host entries for asgard with > a name of localhost. That's what the default install of asgard assumes. You can change it with $ ./configure --with-host=hostname > If I update the table to have the name be that of the > host, I get a login prompt, but then I am told the URL is not found (I do > not get a login unless I make this change). Set LogLevel to debug in your apache config and try again, midgard will log why it's not resolving the URL. It's possible midgard can't find the rootfile, which is one reason why you'd see the behaviour above. > To recap the reason that we are doing this is that, what I am finding is > that users of sitegroup 1 are able to login and add articles, but the admin > is able to login, create users, but is unable to add them to groups. My > understanding is that this is because the old admin site does not handle > sitegroups properly. Is this correct? Oldadmin doesn't do anything with sitegroups, but will behave correctly in a sitegroups setup. Sitegroups were designed to be transparent to the application, and in fact oldadmin was the only admin site available when SGs were developed. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
