[rt-users] Upgraded 4.0.0 with RTFM 2.0 to RT 4.2 - can RTFM be removed?
Dear list, we have upgrade our 4.0.0 to the latest 4.2, which includes an article functionality and currently testing it (it's a clone of our live system). On our 4.0.0, we had RTFM version 2.0 installed (although we never really used it, nor configured it) and the installation guide says this is not compatible with the auto-upgrade script. I proceeded with the 4.0.0-4.2 upgrade anyway, thinking the RTFM would just be left behind. However, the Articles section doesn't quite work (see screenshot with content not being editable, which is a clear symptom of us never having configured RTFM for use), so I suspect RTFM files are affecting the functionality. Is there a quick fix? I don't mind losing the RTFM 2.0 content to be honest. Any help would be greatly appreciated. Kind regards -- Giuseppe Sollazzo Senior System Analyst Member of the Open Data User Group (Cabinet Office) Member of the Technical Standards Board (Cabinet Office)? Member of the Health and Social Care Transparency Panel (Department of Health) Computing Services Information Services St George's, University of London Cranmer Terrace London SW17 0RE gsoll...@sgul.ac.uk +44 20 8725 5160 @sgulit St George's, University of London is proud to be a Stonewall Diversity Champion: 'people perform better when they can be themselves'. [http://www.sgul.ac.uk/images/misc/diversity_logo_with_text.jpg]
Re: [rt-users] Cannot get JumpToFrontPageOnTicketResolve to work.
Hi, That scrip does not work. Scrips work in the background and the redirection needs to happen client side/browser. I got around this by customising the RT mason elements adding code to check the actions list for the change I needed to act on. Once upon a time anyway. -- Aaron On Fri, 24 Apr 2015 at 12:25 am Johan Sundström johan.sundst...@vbm.se wrote: I have followed this: http://requesttracker.wikia.com/wiki/JumpToFrontPageOnTicketResolve See attachment for my conf. But nothing is happening when i resolve a ticket. If i check the source of the page after a resolve, the meta-string is not inserted at all. Using RT 4.2.10, is this script not compatible? Regards *Johan Sundström* / IT-Ansvarig Västerbottens museum www.vbm.se
[rt-users] charset troubles
Hello I just upgraded Apache to 2.4 and RT to latest 3.8, and I get a charset problem: anything that enter RT through rt-mailgate is fine, but any non ASCII character sent through the web interface gets corrupted: I get a ? in a quare instead, which is usually what happens when ISO-8859-1 character was mistaken as UTF-8. Older messages from before the upgrade display correctly, hence this is really a problem at message POST time. Using Firefox's developer toolbar, I can see the POST request: it contains no information about the charset. I assume this is why e-mail behave differently than the web interface: the former comes with Content-Type header featuring the charset information, while the later does not. The page is being served as UTF-8, the form does not say anything about accepted encoding (I tried patching to specify that, but it did not change anything). Acting on a UTF-8 page, the client should post in UTF-8, but I have not been able to verify that (it goes through SSL,which does not help for checking what happens on the wire). Anyone has an idea of what is wrong? Here are the dependencies: rt-3.8.17 p5-Apache-Session-1.93 p5-CGI-4.13 p5-CSS-Squish-0.10 p5-Cache-Simple-TimedExpiry-0.27 p5-Calendar-Simple-1.21 p5-Class-ReturnValue-0.55 p5-DBD-mysql-4.031 p5-DBI-1.633 p5-DBIx-SearchBuilder-1.66 p5-Data-ICal-0.22 p5-Email-Address-1.905 p5-FCGI-0.77 p5-File-ShareDir-1.102 p5-GD-2.53 p5-GDGraph-1.48 p5-GDTextUtil-0.86 p5-GnuPG-Interface-0.52 p5-HTML-Format-2.11 p5-HTML-Mason-1.56 p5-HTML-Parser-3.71 p5-HTML-RewriteAttributes-0.05 p5-HTML-Scrubber-0.11 p5-HTML-Tree-5.03 p5-HTTP-Server-Simple-0.44 p5-HTTP-Server-Simple-Mason-0.14 p5-Locale-Maketext-Fuzzy-0.11 p5-Locale-Maketext-Lexicon-1.00 p5-Log-Dispatch-2.44 p5-MIME-Types-2.09 p5-MIME-tools-5.505 p5-MailTools-2.14 p5-Module-Refresh-0.17 p5-Module-Versions-Report-1.06 p5-Net-3.05 p5-Net-Server-2.008 p5-PerlIO-eol-0.14 p5-Regexp-Common-2013031301 p5-Term-ReadKey-2.32 p5-Text-Autoformat-1.669004 p5-Text-Quoted-2.08 p5-Text-Template-1.46 p5-Text-WikiFormat-0.81 p5-Text-Wrapper-1.04 p5-Time-modules-2013.0912 p5-TimeDate-2.30 p5-Tree-Simple-1.23 p5-UNIVERSAL-require-0.17 p5-XML-RSS-1.56 p5-XML-Simple-2.20 p5-libwww-6.13 perl-5.20.2 apache-2.4.12 apr-1.5.1 apr-util-1.5.4 mod_fcgid-2.3.9 mod_perl-2.0.8 p5-libapreq2-2.12 postgresql-9.4.1 Relevant httpd.conf part for RT: AddDefaultCharset UTF-8 Directory /usr/pkg/share/rt3/html/NoAuth/images/ SetHandler none Options -ExecCGI allow from all /Directory Directory /usr/pkg/share/rt3/html AddDefaultCharset UTF-8 SetHandler fcgid-script Options +ExecCGI /dIRectory In RT_SiteConfig.pm all I have about encoding if for e-mail: Set(@EmailInputEncodings, qw(utf-8 iso-8859-1 us-ascii windows-1252));Set($EmailOutputEncoding , 'iso-8859-1'); -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org
Re: [rt-users] charset troubles
On Thu, 30 Apr 2015 21:08:00 +0200 m...@netbsd.org (Emmanuel Dreyfus) wrote: I just upgraded Apache to 2.4 and RT to latest 3.8 RT 3.8 reached end-of-life over a year ago. No release of Apache 2.4 had been made before RT 3.8 was in critical security releases only. I'm unsurprised that there are incompatibilities between the two. Please upgrade to a supported version of RT. The unmaintained 3.8 series also now has disclosed security vulnerabilities against it. - Alex
Re: [rt-users] charset troubles
Alex Vandiver ale...@bestpractical.com wrote: Please upgrade to a supported version of RT. After upgrading to RT 4.2.10, the problem vanished when updating tickets on the web interface, but it still exists when creating a new ticket from the web interface. The generated HTML for creating and updating looks similar, hence I assume it is the server-side handling that differ. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org
