[rt-users] Very high Apache CPU usage after upgrading to 4.0.0

[Jonah Hirsch]

After updating to 4.0.0, apache will sometimes spawn a process that uses
100% cpu usage for a few seconds, and noticeably slows down the entire
system.

What could be causing this, and what would the best course of action to
debug it be?

I've tried a clean install (with my custom config, but no plugins) which
also has the same issue. 100% cpu usage from Apache, causing the system to
screech to a halt.

Apache 2.2.14 (Ubuntu)

The only thing I'm getting logged is the following warning:

Unable to recognise encoding of this document at
/usr/share/perl5/XML/SAX/PurePerl/EncodingDetect.pm line 100.
(/usr/share/perl5/XML/SAX/PurePerl/EncodingDetect.pm:100)


---
Jonah Hirsch

Re: [rt-users] Radio button or yes/no custom field

[Yan Seiner]

On Fri, May 6, 2011 3:30 pm, Yan Seiner wrote:
> I'm using 3.8.1.  Is there any way to create a checkbox or a yes/no custom
> field with a default to 'no'?
>
> I just need a checkbox to flag a ticket a certain way.

Never mind; found the extension right after I posted.

-- 
If you have eight hours to chop down a tree
spend six sharpening your axe.
--Abraham Lincoln

[rt-users] Radio button or yes/no custom field

[Yan Seiner]

I'm using 3.8.1.  Is there any way to create a checkbox or a yes/no custom
field with a default to 'no'?

"Select one value" doesn't do it as it always presents a third choice '-'
and the window is 5 lines.

The autocomplete doesn't quite do it.

I just need a checkbox to flag a ticket a certain way.


-- 
If you have eight hours to chop down a tree
spend six sharpening your axe.
--Abraham Lincoln

Re: [rt-users] 4.0 Upgrade error

[Thomas Sibley]

On 05/06/2011 04:58 PM, Voity, Michael T. wrote:
> I went back and re-did my install into the /opt/rt3
> 
> went better this time and got to upgrade db...
> 
> now when i bounced the htttpd  i get this error:
> 
> Can't load Perl file: /opt/rt3/bin/webmux.pl
> 
> The file is there...
> 
> odd?

Please actually read the README and UPGRADING documents, as well as
docs/web_deployment.pod.  They explain why you shouldn't install 4.0.0
into /opt/rt3.  They also explain why you shouldn't be trying to use
webmux.pl.

Thomas

Re: [rt-users] 4.0 Upgrade error

[Voity, Michael T.]

I went back and re-did my install into the /opt/rt3

went better this time and got to upgrade db...

now when i bounced the htttpd  i get this error:

Can't load Perl file: /opt/rt3/bin/webmux.pl

The file is there...

odd?


On Fri, May 6, 2011 at 4:39 PM, Alex Vandiver  wrote:
> On Fri, 2011-05-06 at 16:26 -0400, Voity, Michael T. wrote:
>> Well I got a little bit farther...
>>
>> Now i got this error message...
>
> The solution to this, among other things, is documented in
> docs/UPGRADING-4.0  Please read the general upgrading instructions in
> README, as well as docs/UPGRADING-4.0 (which the README also points you
> at).
>  - Alex
>
>



-- 
Michael T. Voity
Network Engineer
TelJet Longhaul LLC
45 Krupp Drive
Williston, VT 05495
D:(802) 922-9507
F:(802) 264-3003
C:(802) 316-9110
E:mvo...@teljet.com

Re: [rt-users] 4.0 Upgrade error

[Alex Vandiver]

On Fri, 2011-05-06 at 16:26 -0400, Voity, Michael T. wrote:
> Well I got a little bit farther...
> 
> Now i got this error message...

The solution to this, among other things, is documented in
docs/UPGRADING-4.0  Please read the general upgrading instructions in
README, as well as docs/UPGRADING-4.0 (which the README also points you
at).
 - Alex

Re: [rt-users] 4.0 Upgrade error

[Ruslan Zakirov]

Drop RTFM from @Plugins.

On Sat, May 7, 2011 at 12:26 AM, Voity, Michael T.  wrote:
> Well I got a little bit farther...
>
> Now i got this error message...
>
> [Fri May  6 20:23:39 2011] [crit]: Can't locate RT/FM.pm in @INC (@INC
> contains: /opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib
> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
> /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .)
> at /opt/rt4/sbin/../lib/RT.pm line 652,  line 4.
> (/opt/rt4/sbin/../lib/RT.pm:340)
> Can't locate RT/FM.pm in @INC (@INC contains:
> /opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib
> /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
> /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
> /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .)
> at /opt/rt4/sbin/../lib/RT.pm line 652,  line 4.
>
>
> Now I'm lost...
>
> On Fri, May 6, 2011 at 4:02 PM, Johan Sjöberg
>  wrote:
>> Verify the database settings in /opt/rt4/etc/RT_SiteConfig.pm are correct. 
>> You can probably just copy your old RT_SiteConfig.pm from your rt3 
>> installation.
>>
>> /Johan
>>
>> -Original Message-
>> From: rt-users-boun...@lists.bestpractical.com 
>> [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Voity, 
>> Michael T.
>> Sent: den 6 maj 2011 21:54
>> To: rt-users@lists.bestpractical.com
>> Subject: [rt-users] 4.0 Upgrade error
>>
>> Hello,
>>
>> I have been following the recent threads on the 4.0 upgrade.   It
>> looks as if that the system I run will not fall into the bugs that everyone 
>> else has found.
>>
>> I did however get this error when trying to upgrade the database:
>>
>> DBI connect('dbname=rt4;host=localhost','rt_user',...) failed: Access denied 
>> for user 'rt_user'@'localhost' (using password: YES) at 
>> /usr/lib/perl5/site_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 106 Connect 
>> Failed Access denied for user 'rt_user'@'localhost' (using
>> password: YES)
>>  at /opt/rt4/sbin/../lib/RT.pm line 164
>>
>> What am i doing wrong?
>>
>>
>> I don't have a DB of "rt4"
>> I do have a user "rt_user"
>>
>> Do I need to edit the "rt-setup-database" file  to change things around?
>>
>> my upgrade from 3.8.7 to 3.8.9-> 3.8.10 went just fine months ago
>>
>> Please point me in the right direction.
>>
>> Regards,
>> --
>> Michael T. Voity
>> TelJet Longhaul LLC
>>
>
>
>
> --
> Michael T. Voity
> Network Engineer
> TelJet Longhaul LLC
> 45 Krupp Drive
> Williston, VT 05495
> D:(802) 922-9507
> F:(802) 264-3003
> C:(802) 316-9110
> E:mvo...@teljet.com
>



-- 
Best regards, Ruslan.

Re: [rt-users] 4.0 Upgrade error

[Voity, Michael T.]

Well I got a little bit farther...

Now i got this error message...

[Fri May  6 20:23:39 2011] [crit]: Can't locate RT/FM.pm in @INC (@INC
contains: /opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
/usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .)
at /opt/rt4/sbin/../lib/RT.pm line 652,  line 4.
(/opt/rt4/sbin/../lib/RT.pm:340)
Can't locate RT/FM.pm in @INC (@INC contains:
/opt/rt4/sbin/../local/lib /opt/rt4/sbin/../lib
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
/usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .)
at /opt/rt4/sbin/../lib/RT.pm line 652,  line 4.


Now I'm lost...

On Fri, May 6, 2011 at 4:02 PM, Johan Sjöberg
 wrote:
> Verify the database settings in /opt/rt4/etc/RT_SiteConfig.pm are correct. 
> You can probably just copy your old RT_SiteConfig.pm from your rt3 
> installation.
>
> /Johan
>
> -Original Message-
> From: rt-users-boun...@lists.bestpractical.com 
> [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Voity, Michael 
> T.
> Sent: den 6 maj 2011 21:54
> To: rt-users@lists.bestpractical.com
> Subject: [rt-users] 4.0 Upgrade error
>
> Hello,
>
> I have been following the recent threads on the 4.0 upgrade.   It
> looks as if that the system I run will not fall into the bugs that everyone 
> else has found.
>
> I did however get this error when trying to upgrade the database:
>
> DBI connect('dbname=rt4;host=localhost','rt_user',...) failed: Access denied 
> for user 'rt_user'@'localhost' (using password: YES) at 
> /usr/lib/perl5/site_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 106 Connect 
> Failed Access denied for user 'rt_user'@'localhost' (using
> password: YES)
>  at /opt/rt4/sbin/../lib/RT.pm line 164
>
> What am i doing wrong?
>
>
> I don't have a DB of "rt4"
> I do have a user "rt_user"
>
> Do I need to edit the "rt-setup-database" file  to change things around?
>
> my upgrade from 3.8.7 to 3.8.9-> 3.8.10 went just fine months ago
>
> Please point me in the right direction.
>
> Regards,
> --
> Michael T. Voity
> TelJet Longhaul LLC
>



-- 
Michael T. Voity
Network Engineer
TelJet Longhaul LLC
45 Krupp Drive
Williston, VT 05495
D:(802) 922-9507
F:(802) 264-3003
C:(802) 316-9110
E:mvo...@teljet.com

Re: [rt-users] 4.0 Upgrade error

[Johan Sjöberg]

Verify the database settings in /opt/rt4/etc/RT_SiteConfig.pm are correct. You 
can probably just copy your old RT_SiteConfig.pm from your rt3 installation.

/Johan

-Original Message-
From: rt-users-boun...@lists.bestpractical.com 
[mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Voity, Michael T.
Sent: den 6 maj 2011 21:54
To: rt-users@lists.bestpractical.com
Subject: [rt-users] 4.0 Upgrade error

Hello,

I have been following the recent threads on the 4.0 upgrade.   It
looks as if that the system I run will not fall into the bugs that everyone 
else has found.

I did however get this error when trying to upgrade the database:

DBI connect('dbname=rt4;host=localhost','rt_user',...) failed: Access denied 
for user 'rt_user'@'localhost' (using password: YES) at 
/usr/lib/perl5/site_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 106 Connect 
Failed Access denied for user 'rt_user'@'localhost' (using
password: YES)
 at /opt/rt4/sbin/../lib/RT.pm line 164

What am i doing wrong?


I don't have a DB of "rt4"
I do have a user "rt_user"

Do I need to edit the "rt-setup-database" file  to change things around?

my upgrade from 3.8.7 to 3.8.9-> 3.8.10 went just fine months ago

Please point me in the right direction.

Regards,
--
Michael T. Voity
TelJet Longhaul LLC

[rt-users] 4.0 Upgrade error

[Voity, Michael T.]

Hello,

I have been following the recent threads on the 4.0 upgrade.   It
looks as if that the system I run will not fall into the bugs that
everyone else has found.

I did however get this error when trying to upgrade the database:

DBI connect('dbname=rt4;host=localhost','rt_user',...) failed: Access
denied for user 'rt_user'@'localhost' (using password: YES) at
/usr/lib/perl5/site_perl/5.8.8/DBIx/SearchBuilder/Handle.pm line 106
Connect Failed Access denied for user 'rt_user'@'localhost' (using
password: YES)
 at /opt/rt4/sbin/../lib/RT.pm line 164

What am i doing wrong?


I don't have a DB of "rt4"
I do have a user "rt_user"

Do I need to edit the "rt-setup-database" file  to change things around?

my upgrade from 3.8.7 to 3.8.9-> 3.8.10 went just fine months ago

Please point me in the right direction.

Regards,
-- 
Michael T. Voity
TelJet Longhaul LLC

Re: [rt-users] HTTP/HTTPS bug in 4.0?

[Mike Johnson]

Hi,

First, apparently I typed it wrong in the config.(added the 'd' to it).

The Wiki (http://requesttracker.wikia.com/wiki/ManualInstallation) says

"

$WebBaseURL = "http://not.configured:80 ";

A variable used to help RT construct
URLsthat
point back to RT. $
WebBaseURLis
the base of the URL. it should usually include the scheme, the host,
and
the port if non-standard.
"
That is what led me to the suggestion of setting WebBaseURL.(by the way I
tested WebBasedURL as well... that actually works,) although both of these
are probably not recommended  :D as stated by Ruslan.

I then removed the above and set WebPort to 443.

Based on Ruslan's comment, this sounds like the recommended way of doing it
:D

Thanks Ruslan.


On Fri, May 6, 2011 at 10:30 AM, Ruslan Zakirov wrote:

> Hi,
>
> Set WebDomain, WebPath and WebPort properly. In simple case (like
> yours) you shouldn't set WebBaseURL (it's WebBaseURL, not
> WebBasedURL). Don't know what you found on the wiki, but information
> is probably out of date.
>
> On Fri, May 6, 2011 at 5:17 PM, Mike Johnson  wrote:
> > Hi everyone,
> >
> > I notice this in our 3.8.10 instance of RT as well. Our redirection of
> all
> > traffic to https picks it up and you continue to browse on port 443.
> >
> > Ruslan mentions that it is a config issue,
> >
> > Searching the Wiki and RT_Config.pm, I found that
> >
> > Set($WebBasedURL, 'https://yourrtinstance.com');
> >
> > Is what you need to set to ensure your links are formed correctly.
> >
> > I've tested, works as expected.
> >
> > Thanks!
> > Mike.
> >
> >
> >
> >
> > On Wed, May 4, 2011 at 5:06 PM, Stoned Elipot 
> > wrote:
> >>
> >> Hi,
> >>
> >> On Wed, May 4, 2011 at 9:49 PM, Alex Vandiver  >
> >> wrote:
> >> > On Wed, 2011-05-04 at 14:27 -0500, Dario Landazuri wrote:
> >> >> We are running an RT instance under https only.  I just noticed a
> small
> >> >> issue - when you're looking at a ticket, the links for a requestor's
> >> >> other tickets are non-https (http://...).  On our system, that leads
> to
> >> >> a 404.  Other links in the ticket (creating links, last ticket
> >> >> transaction, etc) all properly go to https://...
> >> >
> >> > This does look to be a bug; I'll bounce your mail into the
> >> > issues.bestpractical.com to track it.
> >> >  - Alex
> >>
> >> Playing around with a 4.0.0 test clone of a 3.8.10 RT instance I noticed
> >> the same thing, both for the requestor's other tickets links and for
> >> the related tickets links.
> >> Then I noticed that the 3.8.10 instance also exhibits the same
> >> behaviour, only it was
> >> masqueraded by the web server doing HTTP to HTTPS redirection :-}
> >>
> >> Cheers, Stoned.
> >
> >
> >
> > --
> > Mike Johnson
> > Datatel Programmer/Analyst
> > Northern Ontario School of Medicine
> > 955 Oliver Road
> > Thunder Bay, ON   P7B 5E1
> > Phone: (807) 766-7331
> > Email: mike.john...@nosm.ca
> >
>
>
>
> --
> Best regards, Ruslan.
>



-- 
Mike Johnson
Datatel Programmer/Analyst
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON   P7B 5E1
Phone: (807) 766-7331
Email: mike.john...@nosm.ca

[rt-users] rich mail format is enabled, but it does not display the color change of fonts or images in the mails

[Fidel S. Gil]

Good Day

 

I have been fiddling with Request Tracker RT 3.8.7 on fedora core 13, for a 
while and I have a minor problem that seems to be on the configuration side of 
things.

 

I have installed the rt3 with yum from the fedora repos, so all options are the 
default, I have configured the sendmail program to send the mail to an exchange 
server that it uses as both destination and relay for mail which is outgoing, 
tested the sendmail and I can receive the most simple mail on any account both 
internal and external, now for receiving I have setup an e-mail address in the 
exchange server that can be reached by imap to store the mails, I have 
configured fetchmail for the task of reading the mails but leave the copy in 
the exchange server. And the thing works wonderfully I now have a fully 
functional RT.

 

Now the problem arises from the fact that those who create email tickets want 
to see the e-mails that create the tickets just like they would see them on any 
mail interface or program (gmail, yahoo, outlook, thunderbird) on the RT 
interface ticket screen. I Thought that the answer would be with the   
MaxInline, PreferRichText, ShowTransactionImages. Although they do modify the 
format of how my received mail are viewed from simple html to more refined 
ways, they do not complete the job. The color fonts and images embedded are not 
being displayed. I Don´t know if the problem could be on the fetchmail, the 
apache or the RT itself.

 

Any Help is very much appreciated and Thanks in advance

 

 

FG

 

Fight With honor and valor, as long as you are with them you will never be 
truly defeated

[rt-users] ticket depends on external URI

[Raphaël MOUNEYRES]

Hi,

i have two RT 3.8.8 instances running on two different servers with ip 
such as 10.20.130.10 and 10.20.130.11

the first RT has 
Set($Organization, 'serverone.mydomain') 
Set($WebBaseURL, 'http://serverone.mydomain')
the second RT has 
 Set($Organization, "servertwo.mydomain') 
 Set($WebBaseURL, 'http://servertwo.mydomain')

when on the first instance i try to create a depenence toward a ticket on 
the other instance with the following address :
  fsck.com-rt://servertwo/ticket/51
it says
"cannot convert  fsck.com-rt://servertwo/ticket/51 to a URI"

what am i missing here ? is such a thing possible ?

Raphaël
#
" Ce courriel et les documents qui lui sont joints peuvent contenir des
informations confidentielles ou ayant un caractère privé. S'ils ne vous sont
pas destinés, nous vous signalons qu'il est strictement interdit de les
divulguer, de les reproduire ou d'en utiliser de quelque manière que ce
soit le contenu. Si ce message vous a été transmis par erreur, merci d'en
informer l'expéditeur et de supprimer immédiatement de votre système
informatique ce courriel ainsi que tous les documents qui y sont attachés."


   **

" This e-mail and any attached documents may contain confidential or
proprietary information. If you are not the intended recipient, you are
notified that any dissemination, copying of this e-mail and any attachments
thereto or use of their contents by any means whatsoever is strictly
prohibited. If you have received this e-mail in error, please advise the
sender immediately and delete this e-mail and all attached documents
from your computer system."
#

Re: [rt-users] Time fields in days

[Joosep]

Hi!

Thanks for the info Kenneth i will look into it further.

Joosep

On Thu, May 5, 2011 at 5:43 PM, Kenneth Crocker  wrote:

> Joosep,
>
> I would think the DB changes ARE necessary. If you don't define the field
> with 3 decimal positions, then it would always round up or down and you'd
> gain/lose a lot of time. We didn't like the option of hours or minutes, so I
> removed the top-down choice. Since we offered hours in the form of .125
> days, we felt that should be sufficient. We didn't know of ANYONE in our
> organization that would project time estimates in hours or minutes. Most
> projects involve many, many man-days.
>
> Anyway, that was our thinking.
>
> Kenn
>
>
> On Thu, May 5, 2011 at 7:06 AM, Joosep  wrote:
>
>> Thanks for the reply Kenneth,
>>
>> Is the database modification also necessary in order it to work, or should
>> it work with just the modifications in the file 
>> local/html/Elements/SelectTimeUnits
>> ?
>>
>> Implementing the code from that thread so far only seem to give the
>> possibility to select days from the dropdown menu when using for example
>> "time estimated" field in the ticket basics, but seem to lack the math. At
>> least in RT 3.8.10. When inserting some value in hours, RT automatically
>> converts the inserted value into minutes(for example inserting 2 hours
>> results after save 120 minutes). When inserting for example 5 hours, after
>> the save, it results in 5 minutes.
>> I'm not very familiar with perl, but it seems that these rows should be
>> responsible for the math:
>> > % my $selected = 'minutes';
>> > % $selected = 'hours' if $minutes > 60;
>> > % $selected = 'days' if $minutes > 480;
>>
>> But they don't seem to do it. Maybe the math has moved since then or i'm
>> doing something wrong.
>> I would be grateful for any pointers and hints where to look.
>>
>> Thanks in advance
>> Joosep
>>
>>
>

Re: [rt-users] HTTP/HTTPS bug in 4.0?

[Ruslan Zakirov]

Hi,

Set WebDomain, WebPath and WebPort properly. In simple case (like
yours) you shouldn't set WebBaseURL (it's WebBaseURL, not
WebBasedURL). Don't know what you found on the wiki, but information
is probably out of date.

On Fri, May 6, 2011 at 5:17 PM, Mike Johnson  wrote:
> Hi everyone,
>
> I notice this in our 3.8.10 instance of RT as well. Our redirection of all
> traffic to https picks it up and you continue to browse on port 443.
>
> Ruslan mentions that it is a config issue,
>
> Searching the Wiki and RT_Config.pm, I found that
>
> Set($WebBasedURL, 'https://yourrtinstance.com');
>
> Is what you need to set to ensure your links are formed correctly.
>
> I've tested, works as expected.
>
> Thanks!
> Mike.
>
>
>
>
> On Wed, May 4, 2011 at 5:06 PM, Stoned Elipot 
> wrote:
>>
>> Hi,
>>
>> On Wed, May 4, 2011 at 9:49 PM, Alex Vandiver 
>> wrote:
>> > On Wed, 2011-05-04 at 14:27 -0500, Dario Landazuri wrote:
>> >> We are running an RT instance under https only.  I just noticed a small
>> >> issue - when you're looking at a ticket, the links for a requestor's
>> >> other tickets are non-https (http://...).  On our system, that leads to
>> >> a 404.  Other links in the ticket (creating links, last ticket
>> >> transaction, etc) all properly go to https://...
>> >
>> > This does look to be a bug; I'll bounce your mail into the
>> > issues.bestpractical.com to track it.
>> >  - Alex
>>
>> Playing around with a 4.0.0 test clone of a 3.8.10 RT instance I noticed
>> the same thing, both for the requestor's other tickets links and for
>> the related tickets links.
>> Then I noticed that the 3.8.10 instance also exhibits the same
>> behaviour, only it was
>> masqueraded by the web server doing HTTP to HTTPS redirection :-}
>>
>> Cheers, Stoned.
>
>
>
> --
> Mike Johnson
> Datatel Programmer/Analyst
> Northern Ontario School of Medicine
> 955 Oliver Road
> Thunder Bay, ON   P7B 5E1
> Phone: (807) 766-7331
> Email: mike.john...@nosm.ca
>



-- 
Best regards, Ruslan.

Re: [rt-users] HTTP/HTTPS bug in 4.0?

[Mike Johnson]

Hi everyone,

I notice this in our 3.8.10 instance of RT as well. Our redirection of all
traffic to https picks it up and you continue to browse on port 443.

Ruslan mentions that it is a config issue,

Searching the Wiki and RT_Config.pm, I found that

Set($WebBasedURL, 'https://yourrtinstance.com');

Is what you need to set to ensure your links are formed correctly.

I've tested, works as expected.

Thanks!
Mike.




On Wed, May 4, 2011 at 5:06 PM, Stoned Elipot wrote:

> Hi,
>
> On Wed, May 4, 2011 at 9:49 PM, Alex Vandiver 
> wrote:
> > On Wed, 2011-05-04 at 14:27 -0500, Dario Landazuri wrote:
> >> We are running an RT instance under https only.  I just noticed a small
> >> issue - when you're looking at a ticket, the links for a requestor's
> >> other tickets are non-https (http://...).  On our system, that leads to
> >> a 404.  Other links in the ticket (creating links, last ticket
> >> transaction, etc) all properly go to https://...
> >
> > This does look to be a bug; I'll bounce your mail into the
> > issues.bestpractical.com to track it.
> >  - Alex
>
> Playing around with a 4.0.0 test clone of a 3.8.10 RT instance I noticed
> the same thing, both for the requestor's other tickets links and for
> the related tickets links.
> Then I noticed that the 3.8.10 instance also exhibits the same
> behaviour, only it was
> masqueraded by the web server doing HTTP to HTTPS redirection :-}
>
> Cheers, Stoned.
>



-- 
Mike Johnson
Datatel Programmer/Analyst
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON   P7B 5E1
Phone: (807) 766-7331
Email: mike.john...@nosm.ca

Re: [rt-users] Watched queues

[Raed El-Hames]

I gather each work group are admin cc on their queue,
If this is the case then try
AdminCc.id = '__CurrentUser__'

Regards;
Roy

> -Original Message-
> From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-
> boun...@lists.bestpractical.com] On Behalf Of Yan Seiner
> Sent: 05 May 2011 18:23
> To: rt-users@lists.bestpractical.com
> Subject: [rt-users] Watched queues
> 
> I'm stuck on the best way to set this up:
> 
> Our department is set up as a bunch of workgroups.  I have a queue set up
> for each workgroup.  4As things stand, it makes sense to allow anyone to
> create a ticket for any other workgroup and to monitor all the tickets in
> their workgroup.
> 
> It does not make sense to have everyone monitor everyone else's tickets.
> 
> So
> 
> I set up all previledged users with the rights to see all queues, and to
> crteate and comment on tickets in all queues.
> 
> Now I need to set up a search that finds only those queues that each
> member belongs to.
> 
> I am not sure how to do that; I don't see a search option that allows me
> to do that.
> 
> 
> --
> If you have eight hours to chop down a tree
> spend six sharpening your axe.
> --Abraham Lincoln

Re: [rt-users] problems upgrading to 4.0.0 from 3.8.10

[Ruslan Zakirov]

On Thu, May 5, 2011 at 4:27 PM, Robert Wysocki
 wrote:
> Dnia 2011-04-29, pią o godzinie 20:49 +0400, Ruslan Zakirov pisze:
>> Hello,
>>
>> We've reproduced this problem with BasedOn column. Patch is ready,
>> however still need some testing. Failure is not critical. People
>> either would have to manually set BasedOn for custom fields or patch
>> and re-apply an upgrade step.
>
> Hi, is there any chance the patch will be released some time soon?
> I've run into the same problem.

It will be released as 4.0.1rc1 with other important fixes. You can
extract fix from github, test and report back:

https://github.com/bestpractical/rt/commit/506d072c43b8be0ab52ddc852200d21909070eec

> --
> Robert Wysocki
> CONTIUM S.A., http://www.contium.pl
>
>



-- 
Best regards, Ruslan.

Re: [rt-users] HTTP/HTTPS bug in 4.0?

[sunnavy]

I believe it's a config issue too.

sunnavy

On 11-05-05 06:02, Ruslan Zakirov wrote:
> Check rt config through the web UI.
> 
> Regards, Ruslan. From phone.
> 05.05.2011 3:56 пользователь "Lars Braeuer"  написал:
> > Hi,
> >
> > are you talking about the "More about the requestors" section when viewing
> a ticket?
> >
> > Our RT 4.0.0 test instance runs on https, but all the links (i.e. 10 most
> important active tickets)
> > are https, just as expected.
> >
> > Lars
> >
> > Am 04.05.2011 23:06, schrieb Stoned Elipot:
> >> Hi,
> >>
> >> On Wed, May 4, 2011 at 9:49 PM, Alex Vandiver 
> wrote:
> >>> On Wed, 2011-05-04 at 14:27 -0500, Dario Landazuri wrote:
>  We are running an RT instance under https only. I just noticed a small
>  issue - when you're looking at a ticket, the links for a requestor's
>  other tickets are non-https (http://...). On our system, that leads to
>  a 404. Other links in the ticket (creating links, last ticket
>  transaction, etc) all properly go to https://...
> >>>
> >>> This does look to be a bug; I'll bounce your mail into the
> >>> issues.bestpractical.com to track it.
> >>> - Alex
> >>
> >> Playing around with a 4.0.0 test clone of a 3.8.10 RT instance I noticed
> >> the same thing, both for the requestor's other tickets links and for
> >> the related tickets links.
> >> Then I noticed that the 3.8.10 instance also exhibits the same
> >> behaviour, only it was
> >> masqueraded by the web server doing HTTP to HTTPS redirection :-}
> >>
> >> Cheers, Stoned.
> >>