[rt-users] Custom Fields lost after update

[Drew Barnes]

Chris Black wrote:

>Thanks,
>
>But I did read the README and I did do all of that.
>
>Any other ideas?
>
>Thanks.
>Cj B
>  
>
I would empty /opt/rt3/var/mason_data.  That has bit me everytime I move 
a test box up to 3.4.x.

DB

>
>-----Original Message-----
>From: rt-users-bounces at lists.bestpractical.com on behalf of Rejo Zenger
>Sent: Tue 5/24/2005 4:19 PM
>To: rt-users at lists.bestpractical.com
>Subject: Re: [rt-users] Custom Fields lost after update
> 
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>++ 24/05/05 00:20 -0700 - Chris Black:
>  
>
>>I recently updated my installation of RT from 3.2.2 to 3.4.1 and now
>>none of my custom fields show up. All the information looks like it's
>>still in the database, and they work for the root user, but not of any
>>of the other users.
>>    
>>
>
>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/<version>
>|             /opt/rt3/sbin/rt-setup-database --action acl \
>|                 --datadir etc/upgrade/<version>
>|             /opt/rt3/sbin/rt-setup-database --action insert \
>|                  --datadir etc/upgrade/<version>
>| 
>|         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 at rz.xs4all.nl> - http://rejo.zenger.nl - PGP 0x75FC50F3
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.2.2 (GNU/Linux)
>
>iD8DBQFCk7aEHa9Q5nX8UPMRAs1YAJwPVhBDV35HMnKMXNMpPrZXV1+d1gCeIH+j
>Xy7iW0ykPBZ0qkwlktlVTn4=
>=WasY
>-----END PGP SIGNATURE-----
>_______________________________________________
>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
>Be sure to check out the RT Wiki at http://wiki.bestpractical.com
>
>_______________________________________________
>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
>Be sure to check out the RT Wiki at http://wiki.bestpractical.com
>  
>

-- 
Drew Barnes
Applications Analyst
Raymond Walters College
University of Cincinnati