Hi Jens, Thanks. I filed a bug report for it and corrected it in CVS. It will be fixed in upcoming OTRS 3.0.12.
http://bugs.otrs.org/show_bug.cgi?id=7884 The bug report contains instructions for how to patch your OTRS 3.0.x instance. The issue was that the 'select all' checkbox had an ID but not a value, and OTRS tried to insert this as a standard_response (or as a queue) when it was selected. -- Mike On Wed, Nov 2, 2011 at 11:18, Jens Wilke <jens.wi...@affinitas.de> wrote: > On Wednesday 02 November 2011 09:47:22 you wrote: > > Hi Michiel, > >> No, it's now a known bug. When exactly did this happen? Were you >> creating a new queue? Are you using PostgreSQL as the database? > > This happens on applying "Change Queue Relations for Response foo". > It's the postgres error message that i sent. > > I found out, that there are 2 issues that might be responsible for this > behavior. > - The @IDs Elements are not uniq but 35 times repeated. > - There's is an unecessary loop, that repetedly deletes and inserts the same > values. > Both are responsible for massive loops in AdminQueueResponses.pm > The attached patch is a quick hack to fix these Problems. > > Regards, Jens > > _______________________________________________ > 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 > _______________________________________________ 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
