On Fri, Jul 05, 2013 at 05:22:18PM +0100, Samuel Jones wrote:
> On Friday 05 Jul 2013 16:05:56 Joop wrote:
> > Samuel Jones wrote:
> > > The fresh installation of 4.0.12 was to move away from system packages to
> > > source
> > >
> > > I'm all ready to upgrade to 4.0.13, but on make upgrade-databa
Did the upgrade, specified 4.0.4 as the start and 4.0.13 as the end, which went
great and its all working, it didn't however replace the admin comment scrip,
so I think I'll just need to go in and change that manually!
On Friday 05 Jul 2013 16:05:56 Joop wrote:
> Samuel Jones wrote:
> > The fres
Samuel Jones wrote:
The fresh installation of 4.0.12 was to move away from system packages to
source
I'm all ready to upgrade to 4.0.13, but on make upgrade-database, is it best
to run it as upgrade from 4.0.12 or from 4.0.4 which was the previous system
package?
I reckon from 4.0.4 but I
The fresh installation of 4.0.12 was to move away from system packages to
source
I'm all ready to upgrade to 4.0.13, but on make upgrade-database, is it best
to run it as upgrade from 4.0.12 or from 4.0.4 which was the previous system
package?
I reckon from 4.0.4 but I don't want to cause an
Samuel Jones wrote:
Would the regular upgrade path from 4.0.12 --> 4.0.13 resolve the issues,
leave the data where it is and update RT around it?
4.0.12 was a fresh empty install and then the data imported as the documents
say to do. (just importing the mysql essentially, with some scripting t
Would the regular upgrade path from 4.0.12 --> 4.0.13 resolve the issues,
leave the data where it is and update RT around it?
4.0.12 was a fresh empty install and then the data imported as the documents
say to do. (just importing the mysql essentially, with some scripting to
adjust it from SQLi
On Wed, Jul 03, 2013 at 02:42:40PM +0100, Samuel Jones wrote:
> It's a fresh 4.0.12 install with the old data imported rather than an
> upgrade,
> I'm presuming that import mangled the global templates somehow! Well spotted.
If your old data was from a non-4.0.12 install (and your email headers
It's a fresh 4.0.12 install with the old data imported rather than an upgrade,
I'm presuming that import mangled the global templates somehow! Well spotted.
I'll c+p the proper global template in and see if that clears the issue up,
and look at updated to 4.0.13 in the mean time too! (Didn't kno
On Wed, Jul 03, 2013 at 11:32:47AM +0100, Samuel Jones wrote:
> The template is below, all our queues use this global template for 'On
> Comment
> Notify
> AdminCcs as Comment'
>
> Subject: [Comment] {my $s=($Transaction->Subject||$Ticket->Subject||""); $s
> =~
> s/[Comment]s*//g; $s =~ s/^Re
Kevin,
The template is below, all our queues use this global template for 'On Comment
Notify
AdminCcs as Comment'
Subject: [Comment] {my $s=($Transaction->Subject||$Ticket->Subject||""); $s =~
s/[Comment]s*//g; $s =~ s/^Re:s*//i; $s;}
RT-Attach-Message: yes
{RT->Config->Get('WebURL')}Ticket/
On Tue, Jul 02, 2013 at 05:37:44PM +0100, Samuel Jones wrote:
>
>
>We've noticed a problem on our helpdesk recently, where e-mailed
> notifications of new comments
>are loosing letters in their subject lines!
As an Admin - go check your Admin Comment Template
Tools -> Configuration -> G
Hello guys!
We've noticed a problem on our helpdesk recently, where e-mailed notifications
of new
comments are loosing letters in their subject lines!
Some examples are:
[Comment] Missig Ev Rpr
should be: [Comment] Missing Event Report
[Comment] Vhicl Rd ha ar du PMI
should be: [Comment] Vehi
12 matches
Mail list logo
