Re: [rt-users] Onetime CC are giving an internal error

2017-02-16 Thread Gordon Messmer

We are running rt-4.4.0 and just noticed that selecting a One-time Cc
gives an internal error in the Scrips and Recipients block.
The error is:

[9625] [Thu Apr  7 12:37:48 2016] [warning]: Use of uninitialized value in 
split at /opt/rt4/share/html/Helpers/PreviewScrips line 81. 
(/opt/rt4/share/html/Helpers/PreviewScrips:81)
[9625] [Thu Apr  7 12:37:48 2016] [error]: Operation "eq": no method found,
 left argument has no overloaded magic,
 right argument in overloaded package Email::Address at 
/opt/rt4/share/html/Helpers/PreviewScrips line 115.


http://lists.bestpractical.com/pipermail/rt-users/2016-April/087217.html

I've been seeing this error since the release of 4.4.  It was mentioned 
here on the list, and at the time I thought a fix would surely make its 
way down the pipeline.  Sadly, I haven't seen one, so I found the error 
and fixed it the other day.  If this is causing your users to miss 
replies to tickets, the issue is fairly simple to fix.  The attached 
patch corrects the problem by quoting a variable that has overloaded 
operators, so that it's treated like a string.  I've also sent this 
patch to rt-devel.


--- rt-4.4.1/share/html/Helpers/PreviewScrips.orig	2017-02-15 19:52:17.761241782 +
+++ rt-4.4.1/share/html/Helpers/PreviewScrips	2017-02-15 19:52:36.460407904 +
@@ -112,7 +112,7 @@
 % $recips{$addr->address}++;
   <%loc($type)%>:
 % my $show_checkbox = 1;
-% if ( grep {$_ eq $addr->address} @{$action->{NoSquelch}{$type}} ) {
+% if ( grep {$_ eq "$addr->address"} @{$action->{NoSquelch}{$type}} ) {
 % $show_checkbox = 0;
 % }
 


[rt-users] [rt-announce] RT mailing lists moving over to new community forum

2017-02-16 Thread Talena Gandy
Hello!

The various RT and RTIR mailing lists have been a great resource for help and 
discussion since March 2000 (wow!). Today we're excited to announce that we're 
taking a big step forward and migrating our community discussions to a 
web-based forum hosted using Discourse.

Why the change? Discourse offers tons of great features that will help RT users 
including a built-in search (which should also help as people do web searches) 
and a really nice web interface for reading and commenting on posts. You'll 
also have a user account allowing you to set various preferences to manage how 
you interact with the community.

Worry not if you prefer email over a web site. Discourse has a mailing list 
mode that will allow you to continue to receive and reply to posts via email.

Forum Features

The BPS mailing lists are a great resource for sharing information about RT and 
RTIR, but some of that great information can be lost over time. In addition to 
a native search, the forum will allow us to organize discussions by category 
and topic, making information easier to find. We're also going to provide 
several social login options so it will also be easier for new users to become 
involved.

For more technical posts, Discourse offers formatting for code, including Perl, 
to make things easier to read. Users can like and bookmark useful posts. At BPS 
we'll be able to see which posts are popular, indicating a common feature 
request, bug, or gap in the documentation.

There's way more and the best way to see the new features is to try it out for 
yourself. Discourse hosts a site at try.discourse.org 
 where you can experiment to get ready for the 
change.

Schedule

We are currently targeting early March for the cut-over. To seed the new system 
with helpful discussions from the list, we are importing the last 5 years of 
posts from the lists into Discourse. After a few hours of downtime, we'll send 
a notification when the forum is up and running. We'll also pull in current 
subscribers by email and you'll be able to use the "Forgot password" link to 
set a new password.

We're looking forward to the next 17 years of great community discussion!___
rt-announce mailing list
rt-annou...@lists.bestpractical.com
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-announce


Re: [rt-users] How to customize AssetSearchFields

2017-02-16 Thread Dippery, Kyle
Try:

Set($AssetSearchFields, {
'CF.Inventar-Nr'  => '=',
Name=> 'LIKE',
Description => 'LIKE',
});

Cheers,
Kyle
--
Kyle Dippery
Engineering Computing Services
219 RMB
859-257-1346


From: rt-users  on behalf of 
tbec...@frankenbach.com 
Sent: Wednesday, February 15, 2017 10:29 AM
To: rt-users
Subject: [rt-users] How to customize AssetSearchFields

Hello All,

I try to customize the Option AssetSearchFields in the RT_SiteConfig.pm.

The standard config ist:

Set($AssetSearchFields, {
id  => '=',
Name=> 'LIKE',
Description => 'LIKE',
});

I want to able to search for a cutom field called "Inventar-Nr". I added this 
field like this

Set($AssetSearchFields, {
Inventar-Nr  => '=',
Name=> 'LIKE',
Description => 'LIKE',
});

But after restart of Apache I aleays get the Asset id found. The field 
Inventar-Nr is not searched.

How can I do this?
Mit freundlichen Grüßen / best regards

Torsten Becker
Leiter EDV

Hauptsitz / Head Office:

Ernst Frankenbach GmbH Spedition
Am Weyer 5
D-55252 Mainz-Kastel
Germany Kontakt / Contact:

Phone: +49 (0) 6134 - 2900 130
Fax: +49 6134 - 2900 122
E-Mail: tbec...@frankenbach.com
Web:www.frankenbach.com



Geschäftsführer / Managing Director: Ernst Christian Frankenbach, Bernhard Karl 
Meineck
Amtsgericht / Commercial Register: Wiesbaden HRB 4060
UST-ID / VAT: DE217320363


[cid:_2_1430213414301ABC004E3C71C1257FDA][cid:_2_1430236414301ABC004E3C71C1257FDA][cid:_2_1430259414301ABC004E3C71C1257FDA][cid:_2_143027C414301ABC004E3C71C1257FDA]

Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen 
Spediteurbedingungen, jeweils neuester Fassung. Diese beschränken in Ziffer 23 
ADSp die gesetzliche Haftung für Güterschäden nach § 431 HGB für Schäden im 
speditionellen Gewahrsam auf 5,-- Euro/kg, bei multimodalen Transporten unter 
Einschluss einer Seebeförderung auf 2 SZR/kg sowie ferner je Schadenfall bzw. 
-ereignis auf 1 Mio. bzw. 2 Mio. Euro oder 2 SZR/kg, je nachdem, welcher Betrag 
höher ist. Ergänzend wird vereinbart, dass (1) Ziffer 27 ADSp weder die Haftung 
des Spediteurs noch die Zurechnung des Verschuldens von Leuten und sonstigen 
Dritten abweichend von gesetzlichen Vorschriften wie § 507 HGB, Art. 25 MÜ, 
Art. 36 CIM, Art. 20, 21 CMNI zu Gunsten des Auftraggebers erweitert, (2) der 
Spediteur als Verfrachter in den in § 512 Abs. 2 Nr. 1 HGB aufgeführten Fällen 
des nautischen Verschulden oder Feuer an Bord nur für eigenes Verschulden 
haftet und (3) der Spediteur als Frachtführer im Sinne der CMNI unter den in 
Art. 25 Abs. 2 CMNI genannten Voraussetzungen nicht für nautisches Verschulden, 
Feuer an Bord oder Mängel des Schiffes haftet.

We operate exclusively in accordance with the latest version of the Allgemeinen 
Deutschen Spediteurbedingungen - ADSp - (German Freight Forwarders' 
GeneralTerms and Conditions). These limit in clause 23 ADSp the legal liability 
for damage to goods in case of damage to goods whilst in the care of a 
forwarder to € 5/kg, in ac-cordance with Art. 431 of the German Commercial Code 
(HGB); in case of multimod-al transports including sea transport to 2 SDR/kg. 
In addition the liability is limited to € 1 Million per damage respectively to 
€ 2 Million per event or 2 SDR/kg whichever is the greater. The parties agree 
subsidiary, that (1) clause 27 ADSp does neither ex-tend the liability nor the 
responsibility of the forwarder for agents, servants, employ-ees or crewmembers 
beyond legal regulations as Art. 507 HGB, Art. 25 MC, Art. 36 CIM, Art. 20, 21 
CMNI for the benefit of the principal, (2) the freight forwarder as a sea 
carrier is only liable for fault of his own part in case of risks provided in 
Art. 512 paragraph 2 no. 1 HGB such as default in navigation of the ship or 
fire on board and (3) the freight forwarder as a carrier defined in CMNI is 
relieved of liability in compli-ance with the requirements provided in Art. 25 
paragraph 2 CMNI such as default in navigation of the ship, fire on board or 
defects of vessel.



[rt-users] How to customize AssetSearchFields

2017-02-16 Thread TBecker
Hello All,

I try to customize the Option AssetSearchFields in the RT_SiteConfig.pm.

The standard config ist:

Set($AssetSearchFields, {
id  => '=',
Name=> 'LIKE',
Description => 'LIKE',
});

I want to able to search for a cutom field called "Inventar-Nr". I added 
this field like this

Set($AssetSearchFields, {
Inventar-Nr  => '=',
Name=> 'LIKE',
Description => 'LIKE',
});

But after restart of Apache I aleays get the Asset id found. The field 
Inventar-Nr is not searched. 

How can I do this?
Mit freundlichen Grüßen / best regards

Torsten Becker
Leiter EDV

Hauptsitz / Head Office:

Ernst Frankenbach GmbH Spedition
Am Weyer 5
D-55252 Mainz-Kastel
Germany Kontakt / Contact:

Phone: +49 (0) 6134 - 2900 130
Fax: +49 6134 - 2900 122
E-Mail: tbec...@frankenbach.com
Web:www.frankenbach.com


Geschäftsführer / Managing Director: Ernst Christian Frankenbach, Bernhard Karl 
Meineck
Amtsgericht / Commercial Register: Wiesbaden HRB 4060 
UST-ID / VAT: DE217320363 


Wir arbeiten ausschließlich auf Grundlage der Allgemeinen Deutschen 
Spediteurbedingungen, jeweils neuester Fassung. Diese beschränken in Ziffer 23 
ADSp die gesetzliche Haftung für Güterschäden nach § 431 HGB für Schäden im 
speditionellen Gewahrsam auf 5,-- Euro/kg, bei multimodalen Transporten unter 
Einschluss einer Seebeförderung auf 2 SZR/kg sowie ferner je Schadenfall bzw. 
-ereignis auf 1 Mio. bzw. 2 Mio. Euro oder 2 SZR/kg, je nachdem, welcher Betrag 
höher ist. Ergänzend wird vereinbart, dass (1) Ziffer 27 ADSp weder die Haftung 
des Spediteurs noch die Zurechnung des Verschuldens von Leuten und sonstigen 
Dritten abweichend von gesetzlichen Vorschriften wie § 507 HGB, Art. 25 MÜ, 
Art. 36 CIM, Art. 20, 21 CMNI zu Gunsten des Auftraggebers erweitert, (2) der 
Spediteur als Verfrachter in den in § 512 Abs. 2 Nr. 1 HGB aufgeführten Fällen 
des nautischen Verschulden oder Feuer an Bord nur für eigenes Verschulden 
haftet und (3) der Spediteur als Frachtführer im Sinne der CMNI unter den in 
Art. 25 Abs. 2 CMNI genannten Voraussetzungen nicht für nautisches Verschulden, 
Feuer an Bord oder Mängel des Schiffes haftet. 

We operate exclusively in accordance with the latest version of the Allgemeinen 
Deutschen Spediteurbedingungen - ADSp - (German Freight Forwarders' 
GeneralTerms and Conditions). These limit in clause 23 ADSp the legal liability 
for damage to goods in case of damage to goods whilst in the care of a 
forwarder to € 5/kg, in ac-cordance with Art. 431 of the German Commercial Code 
(HGB); in case of multimod-al transports including sea transport to 2 SDR/kg. 
In addition the liability is limited to € 1 Million per damage respectively to 
€ 2 Million per event or 2 SDR/kg whichever is the greater. The parties agree 
subsidiary, that (1) clause 27 ADSp does neither ex-tend the liability nor the 
responsibility of the forwarder for agents, servants, employ-ees or crewmembers 
beyond legal regulations as Art. 507 HGB, Art. 25 MC, Art. 36 CIM, Art. 20, 21 
CMNI for the benefit of the principal, (2) the freight forwarder as a sea 
carrier is only liable for fault of his own part in case of risks provided in 
Art. 512 paragraph 2 no. 1 HGB such as default in navigation of the ship or 
fire on board and (3) the freight forwarder as a carrier defined in CMNI is 
relieved of liability in compli-ance with the requirements provided in Art. 25 
paragraph 2 CMNI such as default in navigation of the ship, fire on board or 
defects of vessel.