[rt-users] Migration from MySQL to PostreSQL - corrupt characters (german umlaut)

[Maik Nergert]

Hi RT Users,

I'm testing the migration from MySQL to PostgreSQL and I'm experiencing 
problems with LATIN1 characters (particularly German umlauts) after the 
migration. They look like ü instead ü


Hexcode from ü → c3 bc
is encoded again to → c3 83 (Ã) and c2 bc (¼)
(http://www.utf8-zeichentabelle.de/)


First I've upgraded RT from 3.8 to 4.2 with mysql db (utf8) and 
everything went smoothly.


New server with fresh installed RT, MySQL, Postgresql from package manager

System (Debian Jessie)
request-tracker: 4.2.8-3+deb8u1
mysql-server: 5.5.44-0+deb8u1
postresql: 9.4.4-0+deb8u1
apache: 2.4.10-10+deb8u3
php: 5.6.13+dfsg-0+deb8u1


Now I followed this tutorial to migrate the DB 
http://requesttracker.wikia.com/wiki/MigrateMysql2PostgresqlV4



The binary files, generated by rt-serializer --clone, include characters 
like öäü so I suppose that there is something going wrong while 
importing to Pg.


'rt-setup-database' creates the Pg DB as UTF8.


postgres=# \l
  List of databases
Name|  Owner   | Encoding  | Collate | Ctype |   Access privileges
---+--+---+-+---+---
  postgres  | postgres | SQL_ASCII | C   | C |
  rt4   | rt_user  | UTF8  | C   | C |
  template0 | postgres | SQL_ASCII | C   | C | =c/postgres  +
|  |   | |   | 
postgres=CTc/postgres

  template1 | postgres | SQL_ASCII | C   | C | =c/postgres  +
|  |   | |   | 
postgres=CTc/postgres




postgres=# show server_encoding;
  server_encoding
-
  SQL_ASCII
(1 row)


postgres=# show client_encoding;
  client_encoding
-
  UTF8
(1 row)

rt4=# select subject from tickets where id=82527;
  subject
--
  Hardware prüfen
(1 row)


Newly created tickets with umlauts are displayed correctly only the 
imported are corrupt!




Switching the client_encoding via “set client_encoding='LATIN1';” or 
directly in /etc/postgresql/9.4/main/postgresql.conf

client_encoding = latin1#(default would be the database encoding utf8)


rt4=# set client_encoding='LATIN1';
SET
rt4=# select subject from tickets where id=82527;
  subject
--
Hardware prüfen
(1 row)



Can someone help me to migrate the db with a full utf8 setup?



Best,
Maik




smime.p7s
Description: S/MIME Cryptographic Signature

[rt-users] New ticket layout change

[Kobus Bensch]

Hi

I am in the process of creating an electronic change request system in 
RT. At the moment the layout is as follows:


-
|  Create new ticket |  Basics
|  Requestor | Queue
|  CC |  Status
|  Admin CC  | Owner
|  Subject |---
|  Describe Issue  |Assets
| |---
| |Custom Fields
| |CF1
| |cf2
| |cf3
| |cf4
| |cfr5
| |cf6
| |cf7
| |etc
-
How do I move the Custom field section to the left and across the whole 
page for this one queue if possible?

How do I change the filed sizes for CF's on a per field basis?

Thanks in advance.

Kobus
P.S. I have searched for the 2 queries. On the first found no answers.
The second there are multiple answers, but I could not get any of them 
to work on a per field basis. Maybe just missing something.




--


Trustpay Global Limited is an authorised Electronic Money Institution 
regulated by the Financial Conduct Authority registration number 900043. 
Company No 07427913 Registered in England and Wales with registered address 
130 Wood Street, London, EC2V 6DL, United Kingdom.


For further details please visit our website at www.trustpayglobal.com.

The information in this email and any attachments are confidential and 
remain the property of Trustpay Global Ltd unless agreed by contract. It is 
intended solely for the person to whom or the entity to which it is 
addressed. If you are not the intended recipient you may not use, disclose, 
copy, distribute, print or rely on the content of this email or its 
attachments. If this email has been received by you in error please advise 
the sender and delete the email from your system. Trustpay Global Ltd does 
not accept any liability for any personal view expressed in this message.

Re: [rt-users] "localtime" without parentheses is ambiguous present in version 4.2.12

[Michiel Beijen]

Hi,

On Thu, Sep 17, 2015 at 4:05 PM, Sunny  wrote:

> We upgraded RT from 4.2.8 to 4.2.12
>
> The following warning appeared
>
> Warning: Use of "localtime" without parentheses is ambiguous at
> /opt/rt4/sbin/../lib/RT/Interface/Email.pm line 526.
>
>
> This link below provided a solution for a user running version 4.2.11
> http://requesttracker.8502.n7.nabble.com/RT-4-2-Use-of-quot-localtime-quot-without-parentheses-is-ambiguous-td60291.html#a60452
>
> vi RT/Interface/Email.pm +526
> print $fh "From $ENV{USER}\@localhost  ".localtime."\n";
>
> added parentheses after localtime
> print $fh "From $ENV{USER}\@localhost  ".localtime()."\n";
>
> This seems to have stopped the warning messages.
>
> Is this a bug that is in 4.2.11 and still in version 4.2.12?

The error is indeed part of in 4.2.11 and 4.2.12; it's fixed in 4.2-trunk though

https://github.com/bestpractical/rt/commit/0cf3eb779a8ce2a26771bf9378ef44553ce2437c

--
Michiel

[rt-users] "localtime" without parentheses is ambiguous present in version 4.2.12

[Sunny]

Hi all,

We upgraded RT from 4.2.8 to 4.2.12

The following warning appeared

Warning: Use of "localtime" without parentheses is ambiguous at 
/opt/rt4/sbin/../lib/RT/Interface/Email.pm line 526.


This link below provided a solution for a user running version 4.2.11
http://requesttracker.8502.n7.nabble.com/RT-4-2-Use-of-quot-localtime-quot-without-parentheses-is-ambiguous-td60291.html#a60452

vi RT/Interface/Email.pm +526
print $fh "From $ENV{USER}\@localhost  ".localtime."\n";

added parentheses after localtime
print $fh "From $ENV{USER}\@localhost  ".localtime*()*."\n";

This seems to have stopped the warning messages.

Is this a bug that is in 4.2.11 and still in version 4.2.12?

Regards