[rt-users] rt timezone issue after upgrade

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

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

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

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

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:

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

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