[rt-users] Time Worked Report
Kenneth Crocker
kfcrocker at lbl.gov
Tue Mar 29 11:42:14 EDT 2011
Opps, that was supposed to be /local/html/Tools/Report. Sorry.
Kenn
On Tue, Mar 29, 2011 at 8:39 AM, Kenneth Crocker <kfcrocker at lbl.gov> wrote:
> 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
> LBNL
>
>
> On Tue, Mar 29, 2011 at 8:37 AM, Kenneth Crocker <kfcrocker at lbl.gov>wrote:
>
>> Walid,
>>
>> Well, *Wherever* you have the .../Tools/Report/... you will need a
>> .../local/Tools/Report/ version to put "TimeWorkedReport".
>>
>> Kenn
>> LBNL
>>
>>
>> On Tue, Mar 29, 2011 at 7:00 AM, Walid Haider <walid.haider at movensis.com>wrote:
>>
>>> 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 at lists.bestpractical.com [mailto:
>>> rt-users-bounces at lists.bestpractical.com] *On Behalf Of *Johan Sjöberg
>>> *Sent:* terça-feira, 29 de Março de 2011 14:56
>>>
>>> *To:* rt-users at lists.bestpractical.com
>>> *Subject:* Re: [rt-users] Time Worked Report
>>>
>>>
>>>
>>> Do you have a /usr/local/rt3?
>>>
>>>
>>>
>>> /Johan
>>>
>>>
>>>
>>> *From:* rt-users-bounces at lists.bestpractical.com [mailto:
>>> rt-users-bounces at lists.bestpractical.com] *On Behalf Of *Walid Haider
>>> *Sent:* den 29 mars 2011 15:20
>>> *To:* Kenneth Crocker; rt-users at lists.bestpractical.com
>>> *Subject:* Re: [rt-users] Time Worked Report
>>>
>>>
>>>
>>> Kenn,
>>>
>>>
>>>
>>> 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 at lists.bestpractical.com [mailto:
>>> rt-users-bounces at lists.bestpractical.com] *On Behalf Of *Kenneth Crocker
>>> *Sent:* segunda-feira, 28 de Março de 2011 17:33
>>> *To:* rt-users at lists.bestpractical.com
>>> *Subject:* Re: [rt-users] Time Worked Report
>>>
>>>
>>>
>>> Walid,
>>>
>>> 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:
>>>
>>> 1) If it exists,type *“/opt/rt3/local/html/Elements/” <enter>*otherwise, create it.
>>> 2) 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” <enter>*.
>>> 3) Replace the code in *“SelectMultiQueue”* with the code specified for
>>> this file from the document the *“TimeWorkedReport".*
>>> 4) If it exists, type *“/opt/rt3/local/html/Tools/” <enter>*, otherwise,
>>> create it.
>>> 5) Create new directories:
>>> A) Create *“Reports”* directory within *“Tools”
>>> *B) Get into *“Reports*” directory.
>>> C) Create *“Elements”* directory within *“Tools/Reports”*
>>> 6) 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 .” <enter>*.
>>> 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 .” <enter>*.
>>> b) Within *“Tools/Reports”,* type *“cp
>>> /opt/rt3/share/html/Tools/index.html TimeWorkedReport.html” <enter>*.
>>> 7) 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
>>>
>>>
>>>
>>>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110329/5485af1b/attachment.htm>
More information about the rt-users
mailing list