YES! :) -Martin On 01.09.2009, at 22:30, Timothy J. Deerinck wrote:

Martin,

Thanks for the reply back. Does the fix address the issue I was talking about though? When a note would be added to a ticket, it would endlessly loop. So this is fixed in 2.4.4?

~Tim

Timothy J. Deerinck Owner / Senior Network & Systems Engineer

Bringing Technologies Together To Work For You... Web: www.networkp.com Corp: 209.456.5310 x 205 Stockton: 209.670.9200 Lodi: 209.642.4170 Turlock: 209. 485.9069 Fax: 209.623.4656 Toll Free: 877.456.5310

-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Martin Edenhofer Sent: Tuesday, September 01, 2009 10:11 AM To: User questions and discussions about OTRS. Subject: Re: [otrs] Ticket Update

Hi Tim,

that's funny. I did the same by fixing Bug# 4149 - The "TicketCreate" event, used for event based notification, did not have access to Article attributes due to the creation time of the article. The sender of the original article could not be used in the notification (http://bugs.otrs.org/show_bug.cgi?id=4149 ).

So good news. This issue is solved with OTRS 2.4.4 (is available tomorrow). :)

-Martin

On 01.09.2009, at 18:44, Timothy J. Deerinck wrote:

...

Hello,

I am trying to find a way to use Event Notifications to send activity updates to users (not just the agent or customer user). I setup a Notification with "Add Note" as the trigger, and it created a very nasty loop sending hundreds of e-mails since it reported the notification as another add note. Infinite Loop! L

What I want is anytime anything is done to a ticket, the system will send a notification without creating a loop. Can this be done???

~Tim

Hi, I've got a problem with the new auto completion for customers. Each time either the already typed part of the name or one field of the suggested cutomers contains a German umlaut (or other special chars) the suggestion box doesn't appear. I think it's an IIS speciality :-) OTRS 2.4.3 / IIS 6.0 / MS SQL I already tried a few things... Add "escape" method here (AgentCustomerSearch.dtl) will fix the umlaut problen in the search string, but all spaced will be double-encoded. Spaces seem to be already encoded by YUI control. myAutoComp.generateRequest = function(sQuery) { return "?Action=AgentCustomerSearch&Search=" + escape( sQuery ); }; Replace the code snipped that uses "Ascii2Html" (AgentCustomerSearch.pm) by inserting "HTML::Entities::encode" into the following code. To get the suggestion box to work I have to encode the plain value as well, so this hack is not very good. push @Data, { CustomerKey => $CustomerUserID, CustomerValue => HTML::Entities::encode($CustomerUserList{$CustomerUserID}), CustomerValuePlain => HTML::Entities::encode($CustomerValuePlain), }; With these hacks the box appears each time it should but it produces new problems: the search string must not contain spaces and the plain value in result array is destroyed. Encoding in DB and HTML pages of OTRS UI are correct. I hope to get some suggestions to fix this. An IIS configuration issue? THX! Timo Rupp Leiter Entwicklung Huber Verlag für Neue Medien GmbH Lorenzstraße 29 D-76135 Karlsruhe Tel. +49 721 15118-0 Fax +49 721 15118-11 rupp@huberverlag.de www.huberverlag.de Huber Verlag für Neue Medien GmbH   -   high speed information Sitz Karlsruhe, Registergericht: Mannheim (HRB 110836) Ust.-Identnummer DE213372792, Geschäftsführer: Rainer Kölmel

Hi Michiel, I use the DB customer backend. I wanted to be sure, that it isn't any beginner's mistake or a known problem before sending it to the dev list. I you think it's better, I'll post it there. Timo Rupp Leiter Entwicklung Huber Verlag für Neue Medien GmbH Lorenzstraße 29 D-76135 Karlsruhe Tel. +49 721 15118-0 Fax +49 721 15118-11 rupp@huberverlag.de www.huberverlag.de Huber Verlag für Neue Medien GmbH   -   high speed information Sitz Karlsruhe, Registergericht: Mannheim (HRB 110836) Ust.-Identnummer DE213372792, Geschäftsführer: Rainer Kölmel -----Ursprüngliche Nachricht----- Von: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] Im Auftrag von Michiel Beijen Gesendet: Mittwoch, 2. September 2009 09:54 An: User questions and discussions about OTRS. Betreff: Re: [otrs] German umlauts and customer auto completion Hi Timo, Actually these kind of issues are more suitable for the dev@ list than for the otrs@ list... Are you using LDAP or AD as the customer backend? Kindest regards, -- Michiel Beijen ((otrs)) :: OTRS AG :: Norsk-Data-Straße 1 :: 61352 Bad Homburg Phone: +31 (0) 6457 42418 :: Fax: +49 (0) 9421 56818 18 http://www.otrs.com/ :: Communication with success! Geschäftssitz: Bad Homburg Amtsgericht Bad Homburg, HRB 10751 Steuernummer: 003 240 97505 Aufsichtsratsvorsitzender: Burchard Steinbild Vorstand: André Mindermann (Vorsitzender), Martin Edenhofer NEU! ENTERPRISE SUBSCRIPTION - JETZT informieren und buchen! http://www.otrs.com/de/support/enterprise-subscription/ On Wed, Sep 2, 2009 at 08:37, Rupp Timo wrote:

Hi,

I've got a problem with the new auto completion for customers. Each time either the already typed part of the name or one field of the suggested cutomers contains a German umlaut (or other special chars) the suggestion box doesn't appear. I think it's an IIS speciality :-)

OTRS 2.4.3 / IIS 6.0 / MS SQL

I already tried a few things...

Add "escape" method here (AgentCustomerSearch.dtl) will fix the umlaut problen in the search string, but all spaced will be double-encoded. Spaces seem to be already encoded by YUI control.

       myAutoComp.generateRequest = function(sQuery) {          return "?Action=AgentCustomerSearch&Search=" + escape( sQuery );        };

Replace the code snipped that uses "Ascii2Html" (AgentCustomerSearch.pm) by inserting "HTML::Entities::encode" into the following code. To get the suggestion box to work I have to encode the plain value as well, so this hack is not very good.

           push @Data, {                CustomerKey        => $CustomerUserID,                CustomerValue      => HTML::Entities::encode($CustomerUserList{$CustomerUserID}),                CustomerValuePlain => HTML::Entities::encode($CustomerValuePlain),            };

With these hacks the box appears each time it should but it produces new problems: the search string must not contain spaces and the plain value in result array is destroyed.

Encoding in DB and HTML pages of OTRS UI are correct.

I hope to get some suggestions to fix this. An IIS configuration issue? THX!

Timo Rupp Leiter Entwicklung

Huber Verlag für Neue Medien GmbH Lorenzstraße 29 D-76135 Karlsruhe Tel. +49 721 15118-0 Fax +49 721 15118-11 rupp@huberverlag.de www.huberverlag.de

Huber Verlag für Neue Medien GmbH   -   high speed information Sitz Karlsruhe, Registergericht: Mannheim (HRB 110836) Ust.-Identnummer DE213372792, Geschäftsführer: Rainer Kölmel --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/