Custom Field don't appear

Hi Jesse,

I have migration rt-3.0.10 to rt-3.4.1 , now i have a problem.The field
“Custom Field”.
In this new version the field “custom field” don’t appear, but im my
mysql DB is ok, all field.

What I have to do?

Ps.: Sorry about my bad english…

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

++ 27/04/05 11:11 -0300 - Fabiano Tomimatsu:

I have migration rt-3.0.10 to rt-3.4.1 , now i have a problem.The field
"Custom Field".
In this new version the field “custom field” don’t appear, but im my
mysql DB is ok, all field.

What I have to do?

Probably, you should read the README file. It says:

| 5b FOR UPGRADING: (Within the RT 3.x series)
|
| Read through the UPGRADING document included in this distribution.
| It may contain important instructions which will help you upgrade
| RT safely.
|
| As root, type:
| make upgrade
|
| This will build new binaries, config files and libraries without
| overwriting your RT database.
|
| You may also need to update RT’s database. To find out, type:
|
| ls etc/upgrade
|
| For each item in that directory whose name is greater than
| your previously installed RT version, run:
| /opt/rt3/sbin/rt-setup-database --action schema
| --datadir etc/upgrade/
| /opt/rt3/sbin/rt-setup-database --action acl
| --datadir etc/upgrade/
| /opt/rt3/sbin/rt-setup-database --action insert
| --datadir etc/upgrade/
|
| Some of these commands will generate errors related to missing files.
| That just means that no action was needed.

I guess this will solve your problem.


Rejo Zenger rejo@rz.xs4all.nl - http://rejo.zenger.nl - PGP 0x75FC50F3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFCb6UwHa9Q5nX8UPMRAmrcAKCuGhz58bAl6xQfh2sah86xxsQfegCg2W+H
W3WfSYA1NzyMBjgkyTyRPcw=
=havd
-----END PGP SIGNATURE-----

At Wednesday 4/27/2005 10:11 AM, Fabiano Tomimatsu wrote:

I have migration rt3.0.10 to rt-3.4.1 , now i have a problem.The field
"Custom Field".
In this new version the field “custom field” dont appear, but im my mysql
DB is ok, all field.

What I have to do?

It may be a rights issue - new custom field permissions have been
introduced since 3.0.

Steve