RT 4.0.6 and aileron CSS

Hi,

There is something a bit annoying with this CSS template: when you
load a big ticket, the “main-navigation” and “page-navigation” menus
are displayed only when the full page is loaded. Sound like a detail
but it gives an impression of slowness. It’s not a big deal if the
page takes time to load, users most of the time don’t notice the
scrollbar is getting smaller, but they do notice the menus are blank
for a while and then appear. Anyone figured out how to fix this?

Another small thing about this template:
Any reason why 4.0/ticket-history-alignment-fix-for-opera-and-ie7 has
not been included in 4.0.6 ? I had to apply the patch myself, the
current template version is broken for IE8 (and maybe opera but not
tested).

Thanks,
L.B.

I reply to myself.

Switching from mod_fastcgi to mod_fcgid improved a lot the speed and
now this “slowness” is hard to notice.

L.B.

There is something a bit annoying with this CSS template: when you
load a big ticket, the “main-navigation” and “page-navigation” menus
are displayed only when the full page is loaded. Sound like a detail
but it gives an impression of slowness. It’s not a big deal if the
page takes time to load, users most of the time don’t notice the
scrollbar is getting smaller, but they do notice the menus are blank
for a while and then appear. Anyone figured out how to fix this?

Unfortunately the DOM needs to be fully loaded before the menus can be
built into their final form. A workaround for this would be to move the
JS that builds the menus out of and into an inline just
after #main-navigation and #page-menu. If it was done cleanly, I think
we’d accept a patch for this.

Another small thing about this template:
Any reason why 4.0/ticket-history-alignment-fix-for-opera-and-ie7 has
not been included in 4.0.6 ? I had to apply the patch myself, the
current template version is broken for IE8 (and maybe opera but not
tested).

It just didn’t get reviewed and merged before we branched for release
engineering. There’s always branches that don’t make it into the
release. :wink:

Thomas

Greetings!

We have RT 4.0.4 installed. It appears that when a user Replies to a new ticket (using the Correspond template), the ticket status is not being set from New to Open.

I have seen reference to a Global Scrip: On Correspond Open Ticket but I do not see that Global Scrip in our environment. This is behavior we desire, so I am wondering, is there another way to get this behavior (configuration / Lifecycles) or are we just missing the Scrip? If we are missing the Scrip, could someone be so kind as to post the settings / field values for the scrip so I can recreate it in our environment.

Thanks,

Denny

We have RT 4.0.4 installed. It appears that when a user Replies to a
new ticket (using the Correspond template), the ticket status is not
being set from New to Open.

I have seen reference to a Global Scrip: On Correspond Open Ticket but
I do not see that Global Scrip in our environment. This is behavior we
desire, so I am wondering, is there another way to get this behavior
(configuration / Lifecycles) or are we just missing the Scrip? If we
are missing the Scrip, could someone be so kind as to post the
settings / field values for the scrip so I can recreate it in our
environment.

Pulled from the installation initialdata:

Description => ‘On Correspond Open Tickets’,
ScripCondition => ‘On Correspond’,
ScripAction => ‘Open Tickets’,
Template => ‘Blank’

You should be able to use that to create a new Global Scrip

-kevin