[rt-users] Editing the issue statement
I have a few tickets which, when opened, did not properly wrap lines. The entire issue statement is a single line. When the ticket is selected and the issue is displayed, RT only shows me the left-most characters of the statement. Is there a way to edit that statement to insert the needed NL characters? (RT 3.8.7 on Linux) -- Dave Close, Thales Avionics, Irvine California USA Software integration and performance testing cell +1 949 394 2124, dave.cl...@us.thalesgroup.com I don't send HTML email and I prefer not to receive it. HTML email is ugly and a significant security exposure.
Re: [rt-users] Editing the issue statement
I asked: I have a few tickets which, when opened, did not properly wrap lines. The entire issue statement is a single line. When the ticket is selected and the issue is displayed, RT only shows me the left-most characters of the statement. Is there a way to edit that statement to insert the needed NL characters? (RT 3.8.7 on Linux) Kenneth Crocker answered: Set your RT_SiteConfig.pm settings to: *Set($MessageBoxWrap, HARD);* *Set($MessageBoxRichText, 0);* *Set($PlainTextPre, 1);* *Set($PlainTextMono, 1);* This works for us. Thanks, but that doesn't fix it here. It might help avoid any future tickets with the problem but doesn't change the appearance of existing ones. I'm not referring to attachments (PlainText...). -- Dave Close, Thales Avionics, Irvine California USA
Re: [rt-users] Can't locate object method _Accessible
Joop wrote: Seems that you previously installed using an rpm so you could check that rpm for where all those files ended up and see if anything is left after de-install. You were right. I had forgotten that the previous RT was installed from an RPM as it had been nearly two years. Once I removed the RPM, the error message in the subject vanished. Of course, there were then some Perl modules that could not be found, but a few symbolic links cured that problem. Thanks for the suggestion. -- Dave Close Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Can't locate object method _Accessible
Thank you to Martin Drasar, Jerrad Pierce, and Ian Pellew for their replies to my query. However, the problem remains unresolved and hasn't really been addressed here. Note that RT was working on exactly the same port with exactly the same Apache configuration. I had an opportunity to abort a corporate push for SharePoint, but without the ability to get RT working again, I am doomed to fail. A week ago, I wrote: My server is running Fedora 8 and was running RT 3.6.5 ok. Most files were located in /usr/share/rt3. I have just upgraded to RT 3.8.7 and changed the installation directory to /opt/rt3. All references in /etc/httpd/conf*/* have been changed to refer to /opt/rt3 but the /usr/share/rt3 directory is still present. RT is running on port 8080 to avoid conflict with another application. After the upgrade, RT refuses to run. The log shows this message: [Fri Apr 16 15:04:34 2010] [error] [client 172.16.100.228] Can't locate object method _Accessible via package SubscribeDashboard (perhaps you forgot to load SubscribeDashboard?) at /usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder/Record.pm line 423.\nCompilation failed in require at /opt/rt3/bin/../lib/RT.pm line 443.\n Looking around online, I don't find this specific message referenced anywhere. However, similar messages with other methods are quoted. The general idea seems to be that something isn't up-to-date as expected. So I've run yum update on the server and updated everything. I then used cpan to update File::Temp since the repositories don't seem to be current for that module. After restarting the web server (Apache 2), RT still fails in exactly the same way. Obviously, I'm still missing something simple. Can anyone tell me what? -- Dave Close, Thales Avionics, Irvine California USA Software integration and performance testing cell +1 949 394 2124, dave.cl...@us.thalesgroup.com I don't send HTML email and I prefer not to receive it. HTML email is ugly and a significant security exposure. Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
[rt-users] Can't locate object method _Accessible
My server is running Fedora 8 and was running RT 3.6.5 ok. Most files were located in /usr/share/rt3. I have just upgraded to RT 3.8.7 and changed the installation directory to /opt/rt3. All references in /etc/httpd/conf*/* have been changed to refer to /opt/rt3 but the /usr/share/rt3 directory is still present. RT is running on port 8080 to avoid conflict with another application. After the upgrade, RT refuses to run. The log shows this message: [Fri Apr 16 15:04:34 2010] [error] [client 172.16.100.228] Can't locate object method _Accessible via package SubscribeDashboard (perhaps you forgot to load SubscribeDashboard?) at /usr/lib/perl5/vendor_perl/5.8.8/DBIx/SearchBuilder/Record.pm line 423.\nCompilation failed in require at /opt/rt3/bin/../lib/RT.pm line 443.\n Looking around online, I don't find this specific message referenced anywhere. However, similar messages with other methods are quoted. The general idea seems to be that something isn't up-to-date as expected. So I've run yum update on the server and updated everything. I then used cpan to update File::Temp since the repositories don't seem to be current for that module. After restarting the web server (Apache 2), RT still fails in exactly the same way. Obviously, I'm still missing something simple. Can anyone tell me what? -- Dave Close Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
