Re: [rt-users] RT 3.8.0 painfully slow on Firefox / Ubuntu
On Mon, Sep 01, 2008 at 07:31:38PM -0500, Jesse Vincent wrote: On Sep 1, 2008, at 6:16 PM, Razvan Cosma wrote: Hello, I installed RT a few weeks ago, on Apache/Centos, and while its functions appear to all work correctly, a big problem is that ticket display screens are rendered painfully slow if using Firefox on Linux. On Windows, using IE, everything is snappy, Firefox a bit sluggish, but on Linux scrolling three pages down in a window renders like a 486 computer opening myspace. I have checked CPU and memory usage - no signs of overload there, disabled add-ons and plugins, again no noticeable increase in speed. Can you suggest what causes this slow redraws? It looks like a Javascript issue, should I blame prototipe? scriptaculous? Any suggested ways to search for what freezes the interface? Actually, it's an interaction between firefox's corner rounding CSS and your X server. We've seen it on about 3 machines, but never managed to track it down. Here we ended in commenting all -moz-border-radius: and -webkit-border-radius: in web2 css. With this, we got good performances on FF. You can also try to disable the background image gradient. ___ 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
Re: [rt-users] RT 3.8.0 painfully slow on Firefox / Ubuntu
On Tue, Sep 02, 2008 at 09:06:08AM +0200, Emmanuel Lacour wrote: Here we ended in commenting all -moz-border-radius: and -webkit-border-radius: in web2 css. With this, we got good performances on FF. You can also try to disable the background image gradient. FYI, the bug report: http://rt3.fsck.com/Ticket/Display.html?id=9898user=guestpass=guest ___ 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
[rt-users] Charset issues after upgrade to 3.8.1
Hello, I just upgraded RT from 3.8.0 to 3.8.1 as suggested in the README. Everything is OK except some charset problems with ticket titles as well as templates. In fact, characters like é, à ... appear scrambled. However ticket history, menus and other text is not affected. Is this a known issue ? Thanks for your help. Regards -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19267620.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
I'd like to add that new arriving tickets do not have this problem, only old ones. F350 wrote: Hello, I just upgraded RT from 3.8.0 to 3.8.1 as suggested in the README. Everything is OK except some charset problems with ticket titles as well as templates. In fact, characters like é, à ... appear scrambled. However ticket history, menus and other text is not affected. Is this a known issue ? Thanks for your help. Regards -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19267639.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 03:22:40AM -0700, F350 wrote: Hello, I just upgraded RT from 3.8.0 to 3.8.1 as suggested in the README. Everything is OK except some charset problems with ticket titles as well as templates. In fact, characters like é, à ... appear scrambled. However ticket history, menus and other text is not affected. Is this a known issue ? You missed reading UPGRADING.mysql ... you didn't ran schema.mysql-4.0-4.1.pl. ___ 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
Re: [rt-users] RT requiring login for every click
this my describe table output: id | varchar(32) | | PRI | | | | a_session | longtext| YES | | NULL | | | LastUpdated | timestamp | YES | | CURRENT_TIMESTAMP | and show create table: | sessions | CREATE TABLE `sessions` ( `id` varchar(32) NOT NULL default '', `a_session` longtext, `LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 | There is wrong vlaues? M. * Marco Avvisano Regione Toscana - Giunta Regionale Direzione Generale Organizzazione - Servizio I.I.T.R. Via di Novoli, 26 - 50127 Firenze (Italy) Tel. +39.055.438.3809 - Fax +39.055.438.5101 e-mail: [EMAIL PROTECTED] * - Original Message - From: Chris Searle [EMAIL PROTECTED] To: rt-users@lists.bestpractical.com Sent: Monday, September 01, 2008 10:43 PM Subject: Re: [rt-users] RT requiring login for every click On 31. aug.. 2008, at 11.39, Chris Searle wrote: there are some DB maintenance scripts you need to run. read the install README file. this happened to me, too :) Do you recall which ones? After running make upgrade from 3.8.0 to 3.8.1 I ran /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade And when asked - entered 3.8.0 as the version being upgraded from. However - I'm still getting asked to login for most clicks. I'm a little confused as to what maintenance script didn't get run here. Been digging here - still not getting anywhere. Checked the sessions table structure - CREATE TABLE sessions ( id char(32) NOT NULL, a_session longtext, LastUpdated timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (id) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; which looks very similar to etc/schema.mysql CREATE TABLE sessions ( id char(32) NOT NULL, a_session LONGTEXT, LastUpdated TIMESTAMP, PRIMARY KEY (id) ); The table was originally MyISAM (was the only one that was) - changed it to InnoDB on the offchance - made no difference in behaviour. Its odd - here's an example. Login - you're logged in Click 'Tickets' - you get the tickets query form Choose an owner and hit 'add these terms' - you get to the login screen Login again - you get to the tickets form _with_ the query updated. I've tried clearing the old session table (well - dumping it to disk then truncating it) - no change. The 3.8.0 backup - that works fine with no issues. ___ 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 ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
I'm running Mysql 5 When applying the command: perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 user pass sql.queries i get the following message: DBD::mysql version 4.002 required--this is only version 3.0008 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. BEGIN failed--compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. Thanks Emmanuel Lacour wrote: On Tue, Sep 02, 2008 at 03:22:40AM -0700, F350 wrote: Hello, I just upgraded RT from 3.8.0 to 3.8.1 as suggested in the README. Everything is OK except some charset problems with ticket titles as well as templates. In fact, characters like é, à ... appear scrambled. However ticket history, menus and other text is not affected. Is this a known issue ? You missed reading UPGRADING.mysql ... you didn't ran schema.mysql-4.0-4.1.pl. ___ 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 -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19268595.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 04:41:41AM -0700, F350 wrote: I'm running Mysql 5 When applying the command: perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 user pass sql.queries i get the following message: DBD::mysql version 4.002 required--this is only version 3.0008 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. BEGIN failed--compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. You have to upgrade your DBD::mysql as requested. Uses CPAN or distro packages or backports to upgrade. You can also run this script from a remote machine having the correct DBD::mysql (you need to modify the script to provide the IP/name of the mysql server). ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
Thanks for ur help. I modified the script and excuted it on a remote machine with a newer DBD::mysql The output that i had is the following: ALTER DATABASE rt3 DEFAULT CHARACTER SET utf8; ALTER TABLE ACL DEFAULT CHARACTER SET utf8; ALTER TABLE Attachments DEFAULT CHARACTER SET utf8; ALTER TABLE Attributes DEFAULT CHARACTER SET utf8; ALTER TABLE CustomFields DEFAULT CHARACTER SET utf8; ALTER TABLE CustomFieldValues DEFAULT CHARACTER SET utf8; ALTER TABLE GroupMembers DEFAULT CHARACTER SET utf8; ALTER TABLE Groups DEFAULT CHARACTER SET utf8; ALTER TABLE Links DEFAULT CHARACTER SET utf8; ALTER TABLE ObjectCustomFields DEFAULT CHARACTER SET utf8; ALTER TABLE ObjectCustomFieldValues DEFAULT CHARACTER SET utf8; ALTER TABLE Principals DEFAULT CHARACTER SET utf8; ALTER TABLE Queues DEFAULT CHARACTER SET utf8; ALTER TABLE ScripActions DEFAULT CHARACTER SET utf8; ALTER TABLE ScripConditions DEFAULT CHARACTER SET utf8; ALTER TABLE Scrips DEFAULT CHARACTER SET utf8; ALTER TABLE sessions DEFAULT CHARACTER SET utf8; ALTER TABLE sessions MODIFY id BINARY(32) NOT NULL DEFAULT ''; ALTER TABLE Templates DEFAULT CHARACTER SET utf8; ALTER TABLE Tickets DEFAULT CHARACTER SET utf8; ALTER TABLE Tickets MODIFY Status VARBINARY(10) NULL DEFAULT NULL; ALTER TABLE Tickets MODIFY Status VARCHAR(10) CHARACTER SET ascii NULL DEFAULT NULL; ALTER TABLE Transactions DEFAULT CHARACTER SET utf8; ALTER TABLE Users DEFAULT CHARACTER SET utf8; ALTER TABLE Users MODIFY WebEncoding VARBINARY(16) NULL DEFAULT NULL; ALTER TABLE Users MODIFY WebEncoding VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL; ALTER TABLE Users MODIFY PGPKey BLOB NULL DEFAULT NULL; ALTER TABLE Users MODIFY Timezone VARBINARY(50) NULL DEFAULT NULL; ALTER TABLE Users MODIFY Timezone VARCHAR(50) CHARACTER SET ascii NULL DEFAULT NULL; ALTER TABLE Users MODIFY EmailAddress VARBINARY(120) NULL DEFAULT NULL; ALTER TABLE Users MODIFY EmailAddress VARCHAR(120) CHARACTER SET ascii NULL DEFAULT NULL; ALTER TABLE Users MODIFY EmailEncoding VARBINARY(16) NULL DEFAULT NULL; ALTER TABLE Users MODIFY EmailEncoding VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL; ALTER TABLE Users MODIFY Lang VARBINARY(16) NULL DEFAULT NULL; ALTER TABLE Users MODIFY Lang VARCHAR(16) CHARACTER SET ascii NULL DEFAULT NULL; I then injected these statements into rt3 database: mysql -u root -p rt3 sql.queries without getting an output. I checked back RT's web interface but i still have the same problem: ticket subjects, custom fields and templates are all scrambled :( Regards Emmanuel Lacour wrote: On Tue, Sep 02, 2008 at 04:41:41AM -0700, F350 wrote: I'm running Mysql 5 When applying the command: perl etc/upgrade/schema.mysql-4.0-4.1.pl rt3 user pass sql.queries i get the following message: DBD::mysql version 4.002 required--this is only version 3.0008 at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. BEGIN failed--compilation aborted at etc/upgrade/schema.mysql-4.0-4.1.pl line 7. You have to upgrade your DBD::mysql as requested. Uses CPAN or distro packages or backports to upgrade. You can also run this script from a remote machine having the correct DBD::mysql (you need to modify the script to provide the IP/name of the mysql server). ___ 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 -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19269813.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 06:02:25AM -0700, F350 wrote: I checked back RT's web interface but i still have the same problem: ticket subjects, custom fields and templates are all scrambled :( Did you cleared the Mason cache (rm -rf ~rt/var/mason_data/*) then restart apache. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
Yes i did but that did not fix the problem. I'm confused. Regards Emmanuel Lacour wrote: On Tue, Sep 02, 2008 at 06:02:25AM -0700, F350 wrote: I checked back RT's web interface but i still have the same problem: ticket subjects, custom fields and templates are all scrambled :( Did you cleared the Mason cache (rm -rf ~rt/var/mason_data/*) then restart apache. ___ 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 -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19270223.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 06:25:01AM -0700, F350 wrote: Yes i did but that did not fix the problem. I'm confused. Me too, maybe I gave wrong ideas, did your RT comes from an upgrade of 3.6.x before 3.8.0 ? ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
No I installed from scratch 3.8.0. Somewhere in the UPGRADING.mysql file, they say: don't use utf8 as default mysql's character set, it's default in some distributives. I'm using debian etch but i don't know if my mysql is using utf-8 by default or not. Could that be the problem ? Regards Emmanuel Lacour wrote: On Tue, Sep 02, 2008 at 06:25:01AM -0700, F350 wrote: Yes i did but that did not fix the problem. I'm confused. Me too, maybe I gave wrong ideas, did your RT comes from an upgrade of 3.6.x before 3.8.0 ? ___ 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 -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19271060.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 07:13:24AM -0700, F350 wrote: No I installed from scratch 3.8.0. Somewhere in the UPGRADING.mysql file, they say: don't use utf8 as default mysql's character set, it's default in some distributives. I'm using debian etch but i don't know if my mysql is using utf-8 by default or not. Could that be the problem ? Ok, here is how I understand your problem: - you installed 3.8.0 - you inserted some datas, mysql on debian etch uses latin1 as default, so you have a DB with UTF-8 encoded as latin1 (to confirm this, connect with the mysql client to the rt db and issue: show variables like 'character_set%';) - in 3.8.1, RT forces connexion to mysql to be UTF-8, so you don't convert back latin1 anymore and you get garbled chars so it was needed to run the mysql4.0-4.1 script, for sure. what I don't understand is why it didn't fix the problem:( Are you sure you worked on the right DB, right RT instance, etc... ? ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
Exactly. I run the show variables like 'character_set%'; command, here is the output: +--++ | Variable_name| Value | +--++ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results| latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--++ I did execute the script again, same problem. New tickets however are OK and scrambled custom field attributes and templates can be modified and updated. Is it secure to update everything and forget about this problem ? Emmanuel Lacour wrote: On Tue, Sep 02, 2008 at 07:13:24AM -0700, F350 wrote: No I installed from scratch 3.8.0. Somewhere in the UPGRADING.mysql file, they say: don't use utf8 as default mysql's character set, it's default in some distributives. I'm using debian etch but i don't know if my mysql is using utf-8 by default or not. Could that be the problem ? Ok, here is how I understand your problem: - you installed 3.8.0 - you inserted some datas, mysql on debian etch uses latin1 as default, so you have a DB with UTF-8 encoded as latin1 (to confirm this, connect with the mysql client to the rt db and issue: show variables like 'character_set%';) - in 3.8.1, RT forces connexion to mysql to be UTF-8, so you don't convert back latin1 anymore and you get garbled chars so it was needed to run the mysql4.0-4.1 script, for sure. what I don't understand is why it didn't fix the problem:( Are you sure you worked on the right DB, right RT instance, etc... ? ___ 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 -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19271484.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 07:39:14AM -0700, F350 wrote: Exactly. I run the show variables like 'character_set%'; command, here is the output: +--++ | Variable_name| Value | +--++ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results| latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--++ I did execute the script again, same problem. Maybe not a good idea :( I hope it didn't did wrong things. New tickets however are OK and scrambled custom field attributes and Theoritically you should be in a situation where: - datas inserted before 3.8.1 were converted from latin1 to utf-8 and should appears right - datas inserted after 3.8.1, before 4.0-4.1 script may be inserted as utf-8, but tables may be defined as latin1 so may be garbled - datas inserted after 4.0-4.1 scrip should be ok templates can be modified and updated. Is it secure to update everything and forget about this problem ? The only risk I see (but I may be missing something) is that corrupted tickets will continue to display badly, new tickets will be ok, every RT configuration thinks that may contains non-ascii chars (queue names, templates, scrips names, users names, group names, ...) should be checked and updated manually if needed to look correctly on the UI. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
Thanks a lot for your help and time Emmanuel. I updated all the tickets, CF and templates that look corrupted. Next time i'll make sure I do the updates on a test server :) Thanks again Emmanuel Lacour wrote: On Tue, Sep 02, 2008 at 07:39:14AM -0700, F350 wrote: Exactly. I run the show variables like 'character_set%'; command, here is the output: +--++ | Variable_name| Value | +--++ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results| latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--++ I did execute the script again, same problem. Maybe not a good idea :( I hope it didn't did wrong things. New tickets however are OK and scrambled custom field attributes and Theoritically you should be in a situation where: - datas inserted before 3.8.1 were converted from latin1 to utf-8 and should appears right - datas inserted after 3.8.1, before 4.0-4.1 script may be inserted as utf-8, but tables may be defined as latin1 so may be garbled - datas inserted after 4.0-4.1 scrip should be ok templates can be modified and updated. Is it secure to update everything and forget about this problem ? The only risk I see (but I may be missing something) is that corrupted tickets will continue to display badly, new tickets will be ok, every RT configuration thinks that may contains non-ascii chars (queue names, templates, scrips names, users names, group names, ...) should be checked and updated manually if needed to look correctly on the UI. ___ 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 -- View this message in context: http://www.nabble.com/Charset-issues-after-upgrade-to-3.8.1-tp19267620p19272127.html Sent from the Request Tracker - User mailing list archive at Nabble.com. ___ 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
Re: [rt-users] Charset issues after upgrade to 3.8.1
On Tue, Sep 02, 2008 at 08:14:55AM -0700, F350 wrote: Thanks a lot for your help and time Emmanuel. I updated all the tickets, CF and templates that look corrupted. Next time i'll make sure I do the updates on a test server :) You're welcome :) Using a test server or a test db/rt instance is a must have ;) ___ 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
[rt-users] RT support in France
Hello, We will be looking for rt support in France soon. Does best practical has french recommended partners ? ___ 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
Re: [rt-users] RT requiring login for every click
I'd certainly be interested in what changes (if any) were made in session handling 3.8.0 - 3.8.1 On 2. sep.. 2008, at 18.13, Trenton Taylor wrote: I went back to 3.8.0 and everything is working fine ... Do you think there is any problem with running 3.8.0 against a 3.8.1 database upgrade? I didn't restore back to my 3.8.0 database because I'll lose a couple hundred tickets ... Not sure what to do but I think you guys are in the same place I am. Thanks, Trent -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marco Avvisano Sent: Tuesday, September 02, 2008 3:52 AM To: Chris Searle; rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT requiring login for every click this my describe table output: id | varchar(32) | | PRI | | | | a_session | longtext| YES | | NULL | | | LastUpdated | timestamp | YES | | CURRENT_TIMESTAMP | and show create table: | sessions | CREATE TABLE `sessions` ( `id` varchar(32) NOT NULL default '', `a_session` longtext, `LastUpdated` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 | There is wrong vlaues? M. * Marco Avvisano Regione Toscana - Giunta Regionale Direzione Generale Organizzazione - Servizio I.I.T.R. Via di Novoli, 26 - 50127 Firenze (Italy) Tel. +39.055.438.3809 - Fax +39.055.438.5101 e-mail: [EMAIL PROTECTED] * - Original Message - From: Chris Searle [EMAIL PROTECTED] To: rt-users@lists.bestpractical.com Sent: Monday, September 01, 2008 10:43 PM Subject: Re: [rt-users] RT requiring login for every click On 31. aug.. 2008, at 11.39, Chris Searle wrote: there are some DB maintenance scripts you need to run. read the install README file. this happened to me, too :) Do you recall which ones? After running make upgrade from 3.8.0 to 3.8.1 I ran /opt/rt3/sbin/rt-setup-database --dba root --prompt-for-dba-password --action upgrade And when asked - entered 3.8.0 as the version being upgraded from. However - I'm still getting asked to login for most clicks. I'm a little confused as to what maintenance script didn't get run here. Been digging here - still not getting anywhere. Checked the sessions table structure - CREATE TABLE sessions ( id char(32) NOT NULL, a_session longtext, LastUpdated timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP, PRIMARY KEY (id) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; which looks very similar to etc/schema.mysql CREATE TABLE sessions ( id char(32) NOT NULL, a_session LONGTEXT, LastUpdated TIMESTAMP, PRIMARY KEY (id) ); The table was originally MyISAM (was the only one that was) - changed it to InnoDB on the offchance - made no difference in behaviour. Its odd - here's an example. Login - you're logged in Click 'Tickets' - you get the tickets query form Choose an owner and hit 'add these terms' - you get to the login screen Login again - you get to the tickets form _with_ the query updated. I've tried clearing the old session table (well - dumping it to disk then truncating it) - no change. The 3.8.0 backup - that works fine with no issues. ___ 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 ___ 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 No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.14/1646 - Release Date: 2008-09-01 6:03 PM Important: The information contained in this e-mail message is confidential and is intended only for the named addressee(s). If the reader of this e-mail message is not an intended recipient (or the individual responsible for the delivery of this e-mail message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this e-mail message is prohibited. If you have received this e-mail message in error, please reply to the sender that you have received the message in error and then delete it. Thank you. ___ 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
[rt-users] Editing Comments or Replies
Dear all, Is there a way to edit a comment or reply once it's in a ticket? I understand we can always add another comment but I am just wondering... Are there any specific reasons why we shouldn't have this feature? One of our RT users is asking this question and I would like to see if RT community has any suggestions. Or is there a third-party contribution for this feature? I did a quick search but no match came up. Thanks, Alan ___ 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
Re: [rt-users] Editing Comments or Replies
From an auditing/security perspective why would you ever want to edit something? Think of it like this: You can't rewrite history *contrary to what Doc Marty say :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan Cheng Sent: Tuesday, September 02, 2008 1:36 PM To: rt-users@lists.bestpractical.com Subject: [rt-users] Editing Comments or Replies Dear all, Is there a way to edit a comment or reply once it's in a ticket? I understand we can always add another comment but I am just wondering... Are there any specific reasons why we shouldn't have this feature? One of our RT users is asking this question and I would like to see if RT community has any suggestions. Or is there a third-party contribution for this feature? I did a quick search but no match came up. Thanks, Alan ___ 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 ___ 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
Re: [rt-users] Cannot login with default pasword
Hi all, Can anyone help me at this, Is there another default password. Thanks, abhishek On 9/2/08, abhishek jain [EMAIL PROTECTED] wrote: Hi, I have just installed RT. and am not able to login with the password as password. pl. suggest, i installled via yum on Centos 5.x Thanks -- Thanks and kind Regards, Abhishek jain -- Thanks and kind Regards, Abhishek jain 07799 328 727 skype: ejaincom ___ 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
Re: [rt-users] Cannot login with default pasword
Does the package include any documentation that may indicate it doesn't use the default username and password? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, September 02, 2008 2:07 PM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] Cannot login with default pasword Hi all, Can anyone help me at this, Is there another default password. Thanks, abhishek On 9/2/08, abhishek jain [EMAIL PROTECTED] wrote: Hi, I have just installed RT. and am not able to login with the password as password. pl. suggest, i installled via yum on Centos 5.x Thanks -- Thanks and kind Regards, Abhishek jain -- Thanks and kind Regards, Abhishek jain 07799 328 727 skype: ejaincom ___ 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 ___ 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
[rt-users] Attachments not working on RT 3.8.1
Hey everyone, I recently upgraded our RT installation from 3.8 to 3.8.1. In the process it seems that attachments have stopped working. When you click on an attachment in the Web UI it will show the URL to the attachment (for example: http://rt.corp.cmates.com/Ticket/Attachment/957954/719224/IMG_0014.JPG). The ticket does show the correct size of attachment, it just simply won't show it. Here is the show create table for my Attachments table: | Attachments | CREATE TABLE `Attachments` ( `id` int(11) NOT NULL auto_increment, `TransactionId` int(11) NOT NULL default '0', `Parent` int(11) NOT NULL default '0', `MessageId` varchar(160) default NULL, `Subject` varchar(255) default NULL, `Filename` varchar(255) default NULL, `ContentType` varchar(80) default NULL, `ContentEncoding` varchar(80) default NULL, `Content` longtext, `Headers` longtext, `Creator` int(11) NOT NULL default '0', `Created` datetime default NULL, PRIMARY KEY (`id`), KEY `Attachments2` (`TransactionId`), KEY `Attachments3` (`Parent`,`TransactionId`) ) ENGINE=InnoDB AUTO_INCREMENT=719222 DEFAULT CHARSET=latin1 | When I do a SELECT * FROM `Attachments` WHERE `id` =719224; It shows the binary blob and what not so the attachment is stored in the db. Any idea on what the issue could be? ___ 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
Re: [rt-users] FW: Updating Tickets - MessageBox Size Double Lines
**Joop van de Wege wrote:
Paul Broadwith wrote:
/ I would like to change the size of the message box that is shown when
// you update a ticket. It’s currently around 10 lines high. In the
// RT_SiteConfig.pm file I changed the MessageBoxHeight variable to 30
but
// this doesn’t seem to have made a difference – either it’s the wrong
// thing to change or it just isn’t working for me.
/I think what you're seeing is a 'feature' of the rich text editing mode
of RT.
I saw the same and plan to disable it globally and then let anyone who
want to send HTML enriched correspondence do that via user prefs.
Fixing this will mean fixing FCKeditor. Complete documentation can be
found at http://www.fckeditor.net
Found the fckconfig.js file in /NoAuth/RichText/FCKeditor which contains
the settings used.
It's only partially the fckeditor's fault. While the fckeditor does
replace the textarea with it's own size, the size can be specified by
RT. Since RT doesn't specify a size, it uses the default one.
I've manually patched my /opt/rt3/share/html/Elements/HeaderJavascript
to have a more reasonable size. If anyone else is interested:
--- HeaderJavascript.orig 2008-08-29 16:08:39.0 -0700
+++ HeaderJavascript 2008-08-29 16:47:01.0 -0700
@@ -104,7 +104,7 @@
typeField.setAttribute('value', 'text/html');
textArea.parentNode.appendChild(typeField);
- var oFCKeditor = new FCKeditor( textArea.name ) ;
+ var oFCKeditor = new FCKeditor( textArea.name, '100%', '400' ) ;
oFCKeditor.BasePath = %RT-Config-Get('WebPath')%/NoAuth/RichText/;
oFCKeditor.ReplaceTextarea();
}
___
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
Re: [rt-users] Issue with duplicate replies to Owner and AdminCC's
Braam, I would make sure the the personnel that are just Developers are in a group of their own, then grant that group the following rights: CommentOnTicket CreateTicket OwnTIcket ReplyToTicket SeeQueue ShowTicket ShowTicketComments StealTicket TakeTIcket Watch This will allow anyone in that group thekind of rights you'd like for developers to have. Then, I would grant these rights to the Role Owners: DeleteTicket ModifyTicket By granting ModifyTicket to Owners only, you keep all other users from messing around with another persons tickets. If they need to make comments or reply to email, you only grant them those rights. Then, I'd modify your script for Notify AdminCc on Whatever to check that the ticket owner is not in the AdminCc role for that queue. That should take care of an ADminCc getting another email if they are also the owner. Hope this helps. Kenn LBNL On 9/1/2008 6:04 AM, Braam van Heerden wrote: Greetings, I've got some issues with my RT instance (3.6.6) that I can't solve after reading the Wiki. I am sure I missed the part containing the answer, though. Before I had a group of support personnel (A, B, C, D) that needed to be apprised of everything that happened in the customer support queue. So I went and made them all AdminCC's on the queue, and that worked fine. Howver, C and D are developers, and does not want to be bothered by irrelevant tickets. So I kept A and B as queue AdminCC's, but dropped C and D, though they still have permissions on the queue to own tickets. The permissions on the queue for the group A,B,C and D belong to is: AssignCustomFields CommentOnTicket CreateTicket DeleteTicket ModifyQueueWatchers ModifyTicket OwnTicket ReplyToTicket SeeQueue ShowTicket ShowTicketComments StealTicket TakeTicket Watch WatchAsAdminCc So now C and D gets no notifications of new tickets, while A and B gets all notifications of all tickets on the queue, which is exactly what was wanted. However, last week one of the developers D complained that he's getting no replies to tickets he's an owner of. Upon investigation I found that emails are only being sent to the AdminCC's, and not the Owner of a ticket. To remedy this, I added a scrip to send a notifcation to the owner on correspond or comment. This made D happy, as he now gets all replies. But A and B gets two replies if they are both AdminCC's and Owners, once from the mail-to-AdminCC scrip and once from the mail-to-Owner scrip. If I remove one of the two roles from the Reply-To screen, both are dropped, and if I add them back in, both roles are added back in. How can I disable sending duplicates like this? Thanks :) Braam van Heerden Conversant Systems (Pty) Ltd Tel: +27 11 782 2930 Cell: +27 82 336 4643 Skype: braamvh ___ 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 ___ 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
[rt-users] TicketSQL for dependencies
RT folks, Is there a reasonable way to search for tickets that have no dependencies? The TicketSQL page on the wiki suggests that DependsOn is NULL should work, but I get this error from the RT 3.6.6 Edit Query form: Error near -NULL- expecting a VALUE in 'DependsOn is NULL' I'm lost This is just a first step toward understanding how to search ticket relationships. Ideally I would like to end up with a set of saved searches that will make RT more useful for project management: I'd like to have searches for next actions (tickets with no new/open dependencies) and top-level projects (tickets with dependencies and that nothing depends on). -- Aaron D. Ball [EMAIL PROTECTED] Senior Systems Analyst Broad Institute of MIT and Harvard ___ 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
Re: [rt-users] TicketSQL for dependencies
quote NULL with single or double quote char On Wed, Sep 3, 2008 at 12:09 AM, Aaron D. Ball [EMAIL PROTECTED] wrote: RT folks, Is there a reasonable way to search for tickets that have no dependencies? The TicketSQL page on the wiki suggests that DependsOn is NULL should work, but I get this error from the RT 3.6.6 Edit Query form: Error near -NULL- expecting a VALUE in 'DependsOn is NULL' I'm lost This is just a first step toward understanding how to search ticket relationships. Ideally I would like to end up with a set of saved searches that will make RT more useful for project management: I'd like to have searches for next actions (tickets with no new/open dependencies) and top-level projects (tickets with dependencies and that nothing depends on). -- Aaron D. Ball [EMAIL PROTECTED] Senior Systems Analyst Broad Institute of MIT and Harvard ___ 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 -- Best regards, Ruslan. ___ 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
Re: [rt-users] ISO8859-1(5) issue in search field
Tested in 3.8.1. * created a ticket with subject å * searched for Å, RT found the ticket * searched for a, RT found the ticket, it's mysql specific: A = Å = a = å according to default case insensitive collation. On Mon, Sep 1, 2008 at 3:08 PM, Christopher Ravnborg [EMAIL PROTECTED] wrote: Hi, I'm trying to find out how i make æ ø and å as case insensitive as all other letters. The problem is ofcourse they do not look alike in the query. Here is first århus (lower case å) and Århus (upper case Å) Simple.html?q=%C3%A5rhus Simple.html?q=%C3%85rhus I want to be able to search for århus and get results containing Århus. Is this at all possible ? - I've tried finding some documentation, but failed to find any help. Using 3.6 and debian 4.0. /Christopher ___ 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 -- Best regards, Ruslan. ___ 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
Re: [rt-users] TicketSQL for dependencies
On Wed, Sep 3, 2008 at 1:26 AM, Aaron D. Ball [EMAIL PROTECTED] wrote: Ruslan Zakirov wrote: quote NULL with single or double quote char Thanks! Oddly enough, searching on DependsOn is 'NULL' seems to return only tickets that *do* depend on another ticket. I get the same result with DependsOn is not 'NULL' but it looks like DependsOn = 'NULL' and DependsOn != 'NULL' do what I want in that respect. I can't say I have a terribly good sense of the syntax of TicketSQL at this point, though. Any suggestions for how to find tickets whose dependencies, if any, are all closed? Is there a DependsOnStatus or something? Nope :( -- Aaron D. Ball [EMAIL PROTECTED] Senior Systems Analyst Broad Institute of MIT and Harvard ___ 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 -- Best regards, Ruslan. ___ 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
Re: [rt-users] TicketSQL for dependencies
Thanks, Ruslan. I have updated the wiki page to reflect what I have learned and cleaned it up a little: http://wiki.bestpractical.com/view/TicketSQL By the way, is there any kind of syntax reference for the Wifty wiki you're using? This page was a mess before because the kwiki syntax that had been used wasn't getting parsed properly, but I couldn't find a reference for the new syntax, even in the svn source for Wifty. I ended up inferring enough syntax that I could make a usable page, but it was harder than it had to be. -- Aaron D. Ball [EMAIL PROTECTED] Senior Systems Analyst Broad Institute of MIT and Harvard ___ 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
Re: [rt-users] TicketSQL for dependencies
By the way, is there any kind of syntax reference for the Wifty wiki you're using? This page was a mess before because the kwiki syntax that had been used wasn't getting parsed properly, but I couldn't find a reference for the new syntax, even in the svn source for Wifty. I ended up inferring enough syntax that I could make a usable page, but it was harder than it had to be. Generally, Wifty uses Markdown, but because this wiki was converted from Kwiki, it uses Kwiki markup. Sadly, the only extant Kwiki parser outside of Kwiki is Text::Kwikiformatish. Which clearly isn't everything we'd like it to be. The easiest fix is to patch that. Or write a converter to move us to something more common. Either would be a fantastic contribution to the community. ___ 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
Re: [rt-users] Attachments not working on RT 3.8.1
You've missed important upgrade step! Read UPGRADING.mysql. On Tue, Sep 2, 2008 at 10:09 PM, Yvo van Doorn [EMAIL PROTECTED] wrote: Hey everyone, I recently upgraded our RT installation from 3.8 to 3.8.1. In the process it seems that attachments have stopped working. When you click on an attachment in the Web UI it will show the URL to the attachment (for example: http://rt.corp.cmates.com/Ticket/Attachment/957954/719224/IMG_0014.JPG). The ticket does show the correct size of attachment, it just simply won't show it. Here is the show create table for my Attachments table: | Attachments | CREATE TABLE `Attachments` ( `id` int(11) NOT NULL auto_increment, `TransactionId` int(11) NOT NULL default '0', `Parent` int(11) NOT NULL default '0', `MessageId` varchar(160) default NULL, `Subject` varchar(255) default NULL, `Filename` varchar(255) default NULL, `ContentType` varchar(80) default NULL, `ContentEncoding` varchar(80) default NULL, `Content` longtext, `Headers` longtext, `Creator` int(11) NOT NULL default '0', `Created` datetime default NULL, PRIMARY KEY (`id`), KEY `Attachments2` (`TransactionId`), KEY `Attachments3` (`Parent`,`TransactionId`) ) ENGINE=InnoDB AUTO_INCREMENT=719222 DEFAULT CHARSET=latin1 | When I do a SELECT * FROM `Attachments` WHERE `id` =719224; It shows the binary blob and what not so the attachment is stored in the db. Any idea on what the issue could be? ___ 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 -- Best regards, Ruslan. ___ 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
