Kevin Falcone wrote:
On Nov 1, 2007, at 9:22 AM, Drew Barnes wrote:
I found that I had to upgrade to 2.1 and run the associated scripts
first, then upgrade again to 2.2.1.
Perhaps I'll try that.
You need to run migrate-2.0-to-2.1 and then do the various
schema/acl/content
upgrades in etc/upgrade. You should be able to do this from a 2.2.x
tarball.
That migrate script does not appear to be much different between 2.1.x
to 2.2.1. I ran the latter version and it seemed to finish without errors.
I also (subsequently) ran the 2.1.0, 2.1.30 and 2.2.0RC2 etc/upgrade
scripts - schema/acl/content (that's a total of 9 times). I believe
this to be the process described in the README. Still...
I'm updating the upgrade instructions to get ready for 2.2.2 so I'm
interested
in seeing what you need to do to get safely upgraded.
What I'm seeing is that (post-upgrade) none of the custom fields are
selected for any class, hence no content.
I can enable the custom fields manually, but the formatting is hosed
(what was entered as WikiTextSingleBody now shows up in Body).
Thanks,
-r
--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
[EMAIL PROTECTED]
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch today.
Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.
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
