Customizing RT interface

I would like to customize the RT interface, colors, and even
get rid of the Best Practical logo from the pages. Are there
any pointers in the documentation on how to get started o that ?

Paulo Ney de Souza
desouza@math.berkeley.edu

Hi,

Yes, there’s a load of stuff in the online Wiki on the website. Most
customisation is done using Callbacks, i.e., code that overrides the
default layout code. It is possible to completely rewrite the
interface over time this way, however most people limit the changes
to the bare minimum.

I’ll also have my archive of alterations / callbacks online soon once
I’ve tidied up a few things. You can find screenshots in a previous
posting of mine to this mailing list (within the past week I believe).

Yours,

GrahamOn 28 Aug 2005, at 20:42, Paulo Ney de Souza wrote:

I would like to customize the RT interface, colors, and even
get rid of the Best Practical logo from the pages. Are there
any pointers in the documentation on how to get started o that ?

Paulo Ney de Souza
desouza@math.berkeley.edu


The rt-users Archives

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Buy your copy of our new book, RT Essentials, today!

Download a free sample chapter from http://rtbook.bestpractical.com

Hi,

Yes, there’s a load of stuff in the online Wiki on the website. Most
customisation is done using Callbacks, i.e., code that overrides the
default layout code. It is possible to completely rewrite the
interface over time this way, however most people limit the changes
to the bare minimum.

I would disagree with this. The Callbacks only add things, but can NOT
override them. To override the layout, you need to create your own version of
the templates, which are Elements/Header and Elements/Footer and
Elements/PageLayout. I have also modified some others – depends on what do
you need to change. Just copy these over to the local area and start
modifying. Also note, that if you just want to replace the logo, it’s in
a variable, so you can do that from the RT_SiteConfig.pm file.

					 Jan 'Bulb' Hudec <bulb@ucw.cz>

signature.asc (189 Bytes)

Yes, of course I was including the fact that there was a local/html
folder for your own HTML code that effectively overrides the HTML
code in share/html in that statement! Of course, if you want to
modify certain components, you need to override the Perl code that
generates them.

Sorry, I should have been more concise and stated that I meant that
you could both override the Perl and HTML aspects of RT, and that it
is quite easy if you read the online documentation and can program
Perl and HTML.

Yours,

GrahamOn 29 Aug 2005, at 07:48, Jan Hudec wrote:

On Mon, Aug 29, 2005 at 00:55:18 +0100, Graham Briggs wrote:

Hi,

Yes, there’s a load of stuff in the online Wiki on the website. Most
customisation is done using Callbacks, i.e., code that overrides the
default layout code. It is possible to completely rewrite the
interface over time this way, however most people limit the changes
to the bare minimum.

I would disagree with this. The Callbacks only add things, but
can NOT
override them. To override the layout, you need to create your own
version of
the templates, which are Elements/Header and Elements/Footer and
Elements/PageLayout. I have also modified some others – depends on
what do
you need to change. Just copy these over to the local area and start
modifying. Also note, that if you just want to replace the logo,
it’s in
a variable, so you can do that from the RT_SiteConfig.pm file.


Jan ‘Bulb’ Hudec bulb@ucw.cz

Yes, of course I was including the fact that there was a local/html
folder for your own HTML code that effectively overrides the HTML
code in share/html in that statement! Of course, if you want to
modify certain components, you need to override the Perl code that
generates them.

… for which again code in local/lib overrides share/lib.

Sorry, I should have been more concise and stated that I meant that
you could both override the Perl and HTML aspects of RT, and that it
is quite easy if you read the online documentation and can program
Perl and HTML.

The confusion stems from the fact, that there is also a mechanism called
“Callbacks”, where you can place mason templates in
html/Callbacks// and it will be inserted where the main
component calls <& Elements/Callback … &>, but this never overrides
anything.> On 29 Aug 2005, at 07:48, Jan Hudec wrote:

On Mon, Aug 29, 2005 at 00:55:18 +0100, Graham Briggs wrote:

Yes, there’s a load of stuff in the online Wiki on the website. Most
customisation is done using Callbacks, i.e., code that overrides the
default layout code. It is possible to completely rewrite the
interface over time this way, however most people limit the changes
to the bare minimum.

I would disagree with this. The Callbacks only add things, but
can NOT
override them. To override the layout, you need to create your own
version of
the templates, which are Elements/Header and Elements/Footer and
Elements/PageLayout. I have also modified some others – depends on
what do
you need to change. Just copy these over to the local area and start
modifying. Also note, that if you just want to replace the logo,
it’s in
a variable, so you can do that from the RT_SiteConfig.pm file.

					 Jan 'Bulb' Hudec <bulb@ucw.cz>

signature.asc (189 Bytes)

We’ve got different ways to customize RT:

  • callbacks(code extending)
  • local dir(file overriding)
  • overlays(code overriding, extending is also possible)
  • CSS(overriding+extending pages look)
  • patches
    More about this you can read on
    Request Tracker Wiki

you can use this technics:

  • change colors with CSS, copy css file to local dir and rewrite
  • change position of elements in page layout with CSS
  • change page layout by overriding of Mason components like Header,
    Footer, PageLayout…
  • add new funcionality to interface components with Callbacks
  • change RT core behaviour with overlays
  • if you change is bug fix or feature that should be merged into
    mainline use patches and send them to rt-devel

New 3.5.x development releases have a lot of work done in CSS part, it
can have more then one css scheme and you can choose it in RT config.On 8/29/05, Jan Hudec bulb@ucw.cz wrote:

On Mon, Aug 29, 2005 at 09:33:05 +0100, Graham Briggs wrote:

Yes, of course I was including the fact that there was a local/html
folder for your own HTML code that effectively overrides the HTML
code in share/html in that statement! Of course, if you want to
modify certain components, you need to override the Perl code that
generates them.

… for which again code in local/lib overrides share/lib.

Sorry, I should have been more concise and stated that I meant that
you could both override the Perl and HTML aspects of RT, and that it
is quite easy if you read the online documentation and can program
Perl and HTML.

The confusion stems from the fact, that there is also a mechanism called
“Callbacks”, where you can place mason templates in
html/Callbacks// and it will be inserted where the main
component calls <& Elements/Callback … &>, but this never overrides
anything.

On 29 Aug 2005, at 07:48, Jan Hudec wrote:

On Mon, Aug 29, 2005 at 00:55:18 +0100, Graham Briggs wrote:

Yes, there’s a load of stuff in the online Wiki on the website. Most
customisation is done using Callbacks, i.e., code that overrides the
default layout code. It is possible to completely rewrite the
interface over time this way, however most people limit the changes
to the bare minimum.

I would disagree with this. The Callbacks only add things, but
can NOT
override them. To override the layout, you need to create your own
version of
the templates, which are Elements/Header and Elements/Footer and
Elements/PageLayout. I have also modified some others – depends on
what do
you need to change. Just copy these over to the local area and start
modifying. Also note, that if you just want to replace the logo,
it’s in
a variable, so you can do that from the RT_SiteConfig.pm file.


Jan ‘Bulb’ Hudec bulb@ucw.cz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDEwMnRel1vVwhjGURAuTwAJ0Zdg8sj8TBHWRZLc5jrW/YYKJXjACdH7vL
jo/N2W2r8+bcnnpnicXwIaU=
=gbBl
-----END PGP SIGNATURE-----


The rt-users Archives

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Buy your copy of our new book, RT Essentials, today!

Download a free sample chapter from http://rtbook.bestpractical.com

Best regards, Ruslan.

Jan Hudec wrote:

Also note, that if you just want to replace the logo, it’s in
a variable, so you can do that from the RT_SiteConfig.pm file.

Though the variable ($LogoURL) is there, it’s not actually used
anywhere. For reasons that were sensible at one point (and that I can’t
quite remember at the moment), the URL is hardcoded in one of the Mason
components.

Cheers,
Tom

Jan Hudec wrote:

Also note, that if you just want to replace the logo, it’s in
a variable, so you can do that from the RT_SiteConfig.pm file.

Though the variable ($LogoURL) is there, it’s not actually used
anywhere. For reasons that were sensible at one point (and that I can’t
quite remember at the moment), the URL is hardcoded in one of the Mason
components.

Thanks. Good to know. I thought I saw the varable mentioned on the Wiki
somewhere. Perhaps some good soul could correct it there.

					 Jan 'Bulb' Hudec <bulb@ucw.cz>

signature.asc (189 Bytes)