Re: [Codestriker-user] Receiving configuration error while installing version 1.9.1
Brought to you by:
sits
|
From: Keith L. <the...@gm...> - 2005-08-18 17:17:37
|
Thanks!
On 8/18/05, David Sitsky <si...@us...> wrote:
>=20
> Hi Keith,
>=20
> On Thu, 18 Aug 2005 00:59, Keith Levy wrote:
> > Attached is my copy of the config file ...
>=20
> I can see what the problem is, it has nothing to do with the 1.9.1 as=20
> such,
> but is a problem in the actual configuation file. If you go right down to
> the bottom, to your $comment_state_metrics definition, it reads:
>=20
> # Four metrics defined: Status, Level, Mode and Type.
> $comment_state_metrics =3D
> [
> { name=3D>'Status', values=3D>['Submitted', 'Invalid', 'Completed'],
> default_value=3D>'Submitted' },
> ( name=3D>'Level', values=3D>['Major', 'Minor'] },
> { name=3D>'Mode', values=3D>['Missing', 'Wrong', 'Unclear',
> 'Suggestion'] },
> { name=3D>'Type', values=3D>['Logic', 'Data Handling', 'Interface',
> 'Error Handling', 'Performance', 'Comments',
> 'Standards'] }
> ];
>=20
> You can see for the 'Level' metric, you are starting the definition with=
=20
> an
> open bracket '(', not a curly brace '{'. This has effectively caused a
> syntax error in the configuration file, which has caused the "$db has not
> been set" error. Its a shame we don't get a more helpful error message,
> I'll look into that.
>=20
> The standard configuration file which ships with codestriker doesn't have
> this defect in it, so perhaps you accidently changed this?
>=20
> Anyway - changing it to a brace should fix the issue, ie:
>=20
> { name=3D>'Level', values=3D>['Major', 'Minor'] },
>=20
>=20
> --
> Cheers,
> David
>=20
>
|