Walid,
Also, we used to have a different $home than /opt/rt3/ (in Solaris) and it
caused endless problems when trying to implement extensions. We decided to
just go to opt/rt3 and put it in VM and we’ve been sailing smoothly ever
since. Just a thought for you to consider.
Kenn
LBNLOn Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker kfcrocker@lbl.gov wrote:
Walid,
Well, Wherever you have the …/Tools/Report/… you will need a
…/local/Tools/Report/ version to put “TimeWorkedReport”.Kenn
LBNLOn Tue, Mar 29, 2011 at 7:00 AM, Walid Haider walid.haider@movensis.comwrote:
Hi Johan,
No, I do not. Should I go ahead and create it and then follow Kenn’s
instructions?Regards,
Walid
From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Johan Sjöberg
Sent: terça-feira, 29 de Março de 2011 14:56To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked ReportDo you have a /usr/local/rt3?
/Johan
From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Walid Haider
Sent: den 29 mars 2011 15:20
To: Kenneth Crocker; rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked ReportKenn,
Again, thanks for the reply. As I ran a packaged install of RT 3.8.4, my
$home is /usr/share/rt3. My folder structure is different compared to what
you mention below, as I do not have a share directory within my RT $home.Please advise if I should create the local directory within
/usr/share/rt3.Thanks,
Walid
From: rt-users-bounces@lists.bestpractical.com [mailto:
rt-users-bounces@lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
Sent: segunda-feira, 28 de Março de 2011 17:33
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Time Worked ReportWalid,
What I mean is this; it is highly recommended that any changes you make
to RT code be done in a “local” version. RT will automatically look to
$Home/local/…/…/ (where $home is usually opt/rt3/) for any
override code that an installation may have developed. In this example
(TimeWorkedReport), I copied the various /$home*/share/…/…
directories & files listed in the "readme’ for that report into a /$home/
local/…/… version/copy of those directoryies & files. I did *
NOT make any changes to any /share/ version of RT code. This is
recommended for a couple reasons; the least of which it is easier to
maintain later versions of RT without wiping out your local code
(provided you keep a copy of that code). Also, industry wide for about the
last 40 years, it has been considered a best practice to never mess
with original code, but to provide a method that allows you to use other
code instead.So, my advice is to first; return all /share/ code to it’s original state.
Then create $home*/local/*html/Tools/Reports directories in order to
copy/create the files mentioned in the “TimeWorkedReport” documentation.
That’s what I did:
- If it exists,type “/opt/rt3/local/html/Elements/” otherwise,
create it.- Copy the “delivered” file (from …/share/…) SelectQueue over to
this directory with a the new name.
A) Type “cp /opt/rt3/share/html/Elements/SelectQueue
SelectMultiQueue” .- Replace the code in “SelectMultiQueue” with the code specified for
this file from the document the “TimeWorkedReport".- If it exists, type “/opt/rt3/local/html/Tools/” , otherwise,
create it.- Create new directories:
A) Create “Reports” directory within *“Tools”
*B) Get into “Reports” directory.
C) Create “Elements” directory within “Tools/Reports”- Copy the “delivered” files (from …/share/…) (Tabs, index.html)
over to the new directories:
A) Copy the “Tabs” file over to “Tools/Reports/Elements”:
1) Within “Elements”, type “cp
/opt/rt3/share/html/Tools/Reports/Elements/Tabs .” .
2) Go back 1 directory level to get to “/Tools/Reports”.
3) Copy the “index.html” file over to “Tools/Reports” twice:
a) Within “Tools/Reports”, type “cp
/opt/rt3/share/html/Tools/index.html .” .
b) Within “Tools/Reports”, type “cp
/opt/rt3/share/html/Tools/index.html TimeWorkedReport.html” .- Modify/Replace the code in *“Tabs”, “index.html” & “TimeWorkedReport”
*with the code specified for these files from the document the “Time
Worked Report”.Anyway, This is the procedure I followed and I had absolutely no problems
AND I didn’t have to worry about Production being messed up.Also, I’m in 3.8.7 so I made sure to follow the 3.8 instructions.
Hope this helps.
Kenn
LBNL