
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hej Peter, Peter Hoogkamer schrieb:
Hi,
I have run the SELECT query on database otrs and this is the result:
mysql> SELECT id,name,valid_id FROM ticket_priority; +----+-------------+----------+ | id | name | valid_id | +----+-------------+----------+ | 1 | 1 heel laag | 1 | | 2 | 2 laag | 1 | | 3 | 3 normaal | 1 | | 4 | 4 hoog | 1 | | 5 | 5 heel hoog | 1 | +----+-------------+----------+ 5 rows in set (0.00 sec)
mysql>
...okay - here we go. Did you rename/translate the priorities directly in the data base? That's not really a good idea, since this is the reason why your postmaster can not find the default priority '3 normal'. So if you want your postmaster running again you should (1) set the normal priority names or (2) replace the default priority in your sysconfig, e.g. Ticket -> Core::PostMaster PostmasterDefaultPriority. BUT there are quite many entries which may contain default priority (just utilize the search function in the sys config), therefore most practical solution is (1) and let the translation be done by the language module. regards, Torsten Thau - -- Torsten Thau, Dipl. Inform. c.a.p.e. IT Labs GbR - Annaberger Str. 240 - D-09125 Chemnitz phone: +49 371 5347 623 cell: +49 176 66 680 680 personal pgp-key: 0x93E0A174 fax: +49 371 5347 625 http://www.cape-it.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHI0bkvXo8m5PgoXQRAjIuAJ9kEPbRxZ3AK6rogirSxlemlqYCVgCfVv4T tx3Nzi1jo9xUJvm8qQnDIig= =vRwS -----END PGP SIGNATURE-----