On Jun 7, 2007, at 4:27 PM, Malcolm Tester wrote:

Hi,
        Someone installed a modified version of RT by Secure Scout,
version 3.4.5 on Windows in my organization. We've been using it a few months now, and I want to move it over to Linux (FC 6). I actually have
everything running ok with version 3.6.3.  I had to do a few tweaks to
get rid of Secure Scouts stuff, but nothing major.

        However, there is a big difference between the old version and
the new version.  The new version uses the MyRT.html to determine the
widgets shown on the 'RT at a Glance' page.  The old version, at least
SS's version, had the index.html hard coded to show the various
Elements.  I wrote a few new Elements that I just hard-coded into the
index.html as well.  On the new version, I would like to do it the
'Right' way. That means I need to add in my custom Elements as widgets.
To do this, I need to know how to get them to show up on the MyRT.html
page.

Any pointers would be greatly appreciated!


What you want to be looking at is the "HomepageComponents" stuff.


# $HomepageComponents is an arrayref of allowed components on a user's
# customized homepage ("RT at a glance").

Set($HomepageComponents, [qw(QuickCreate Quicksearch MyAdminQueues MySupportQueu
es MyReminders  RefreshHomepage)]);

RTIR 2.3 extends RT in this way.


Malcolm

_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com


Attachment: PGP.sig
Description: This is a digitally signed message part

_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. 
Buy a copy at http://rtbook.bestpractical.com

Reply via email to