Hi,
We are just starting to evaluate otrs, and an initial setup has been done by
our systems group. I've created an en_Custom.pm and those changes look OK.
What I want to do next is to make otrs use, for its lists of users, an existing and populated mysql database, while keeping tickets themselves in the test mysql db that was set up for me. If I understand the docs correctly, I can do this by adding stuff
into Config.pm. It looks like what I need to add is from section 11.2 of the Admin manual:
$Self->{CustomerUser} = {
..
..
..
}
and in there I set it to use an external database and change the names of
fields to match those already in use in the existing db.
However, when I do this and restart otrs, I get:
Software Error:
Got no MainObject! at /home/operations/OTRS/otrs-2.2.2//Kernel/System/DB.pm
line 85
I'm no perl expert, but it looks like the sequence is as follows:
1) Web::InterfaceAgent calls System::DB->new (line 144)
2) new sees that I want to use a CustomerUser DB, loads that module, and calls
the new within it (line 146 or so)
3) CustomerUser::DB->new eventually calls again System::DB->new (line 69)
Trouble is, the call in (3) above doesn't include a required MainObject in its
parameter list, so it dies.
Is this a bug or am I missing some parameter setting?
___________________________________________________________________
* * Tim Streater Network Engineer
* *
* City House
* 126-130 Hills Road Tel +44 1223 371300
* Cambridge CB2 1PQ Fax +44 1223 371371
D A N T E United Kingdom WWW http://www.dante.net
____________________________________________________________________
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
