[rt-users] rt timezone issue after upgrade

[Satyajeet]

Dear All,

Hope you are doing fine. I need your support on the following issue:

After upgrading rt from 4.2.3 to 4.2.12 all the datetime fields for
unprivileged users are expecting the values in UTC though the global
timezone has been defined to Asia/Muscat, so, as soon as the ticket is
saved/created it adds 4 hours in the values selected in datetime fields.
However, it is functioning fine for root. Please see the below snapshots for
reference:

 

After Save:

 

Appreciate your support on this.

Thank you.



--
View this message in context: 
http://requesttracker.8502.n7.nabble.com/rt-timezone-issue-after-upgrade-tp60829.html
Sent from the Request Tracker - User mailing list archive at Nabble.com.

Re: [rt-users] Problem with RT::SystemUser in escalatePriority

[Christian Loos]

OK, then remember this, once you will upgrade to RT 4.4, because this
version will support [1] searches like

Status = '__active__'

Chris

[1] https://github.com/bestpractical/rt/commit/20f3268

Am 29.10.2015 um 15:39 schrieb markus.wildb...@magna.com:
> Hi Christian!
> 
> Thanks a lot for your response! This solved my problem!
> 
> As we have different lifecycles in place, I stay with looping through
> all queues...
> 
> 
> Greetings,
> Markus

Re: [rt-users] Problem with RT::SystemUser in escalatePriority

[markus . wildbolz]

Hi Christian!

Thanks a lot for your response! This solved my problem!

As we have different lifecycles in place, I stay with looping through all 
queues...


Greetings,
Markus





Von:
Christian Loos 
An:
markus.wildb...@magna.com, rt-users@lists.bestpractical.com, 
Datum:
29.10.2015 15:33
Betreff:
Re: Problem with RT::SystemUser in escalatePriority



Am 29.10.2015 um 13:58 schrieb markus.wildb...@magna.com:
> Hi guys!
> 
> Since a couple of days, I have the problem, that my priority escalation
> script doesn't work anymore. Script is attached...
> 
> 
> 
> The error message is:
> 
> Name "RT::SystemUser" used only once: possible typo at
> ./rt-escalatePriority line 36.
> Can't locate object method "Deprecated" via package "RT" at
> /opt/rt4/lib/RT/Interface/CLI.pm line 93.
> 
> 
> I currently cannot figure out, what's the problem with the mentioned
> line 36:
> 
> my $queues = new RT::Queues($RT::SystemUser);
> 
> 
> Does anybody know this problem?
> 
> 
> Greetings,
> Markus

Hi Markus,

remove the following lines

---
 package RT;

 use RT::Interface::CLI qw(CleanEnv);

 # Clean our the environment

 CleanEnv();

 # Load the RT configuration
 RT::LoadConfig();


 # Initialise RT
 RT::Init();

 my $queues = new RT::Queues($RT::SystemUser);
---

with

---
use RT::Interface::CLI qw(Init);
Init();
my $queues = RT::Queues->new(RT->SystemUser);
---

Also, do you have different Lifecycles defined?
If not, then you can use the rt-crontool with

--search RT::Search::FromSQL

and a search like

-search-arg "Status != 'resolved' AND Status != 'rejected'"

instead if use a Perl script to loop over the queues and then call
rt-crontool from within the Perl script.

See also the second example in
https://www.bestpractical.com/docs/rt/4.2/automating_rt.html#Escalating-Priority


Chris

[rt-users] Component path given to Interp->load must be absolute

[Brad S Konia]

I installed RT 4.2.12 on a Litespeed web server and everything seems to be 
working, except it’s not rendering any of the images, CSS or JS. I see tons of 
messages like this in my error log:

Oct 29 18:27:28 web1 RT: [2202] Component path given to Interp->load must be 
absolute (was given static/images/bpslogo.png)#012Stack:#012  
[/usr/local/share/perl5/HTML/Mason/Request.pm:249]#012  
[/usr/local/share/perl5/HTML/Mason/Request.pm:212]#012  
[/opt/rt4/sbin/../lib/RT/Interface/Web/Request.pm:61]#012  
[/usr/local/share/perl5/Class/Container.pm:275]#012  
[/usr/local/share/perl5/Class/Container.pm:353]#012  
[/usr/local/share/perl5/HTML/Mason/Interp.pm:348]#012  
[/usr/local/share/perl5/HTML/Mason/Interp.pm:342]#012  
[/usr/local/share/perl5/HTML/Mason/PSGIHandler.pm:59]#012  
[/usr/local/share/perl5/HTML/Mason/PSGIHandler/Streamy.pm:52]#012  
[/opt/rt4/sbin/../lib/RT/Interface/Web/Handler.pm:310]#012  
[/usr/local/share/perl5/Plack/Util.pm:339]#012  
[/usr/local/share/perl5/Plack/Handler/FCGI.pm:145]#012  
[/usr/local/share/perl5/Plack/Loader.pm:84]#012  
[/usr/local/share/perl5/Plack/Runner.pm:277]#012  
[/opt/rt4/sbin/../lib/RT/PlackRunner.pm:141]#012  
[/opt/rt4/sbin/rt-server.fcgi:162]

From the above error message, it seems the script wants an absolute path. Upon 
viewing the HTML source code, I see the path is in fact absolute: 
src="/static/images/bpslogo.png”

This led me to believe that something is causing the script to drop the leading 
slash. To test this theory, I tried accessing the image via the following URL:

https://rt.hostland.com//static/images/bpslogo.png (note the extra leading 
slash)

and it worked!

I’m sure this issue is due to some incompatibility between the Litespeed 
configuration and the standard Apache configuration documented in the manual, 
but I’m not sure how to fix this. I tried working around it by playing around 
with the $WebDomain and $WebPath variables to force an extra leading slash and 
the results were fairly disastrous. I’m wondering if anyone else has gotten 
this working on Litespeed or if anyone can offer any suggestions on how I might 
proceed.