Hello all,
I’m attempting an upgrade of RT & RTFM on my test server. The RT
upgrade (from 3.4.4 to 3.6.5) went fine. The upgrade of RTFM, not so
good.
I’m going from 2.0.4 to 2.2.1. I’ve followed the instructions in the
README, and all the upgrade scripts ran without any errors or warnings.
However, after the upgrade process (& clearing Mason dirs & restarting
httpd of course) I can’t see the articles contents any more. They are
still there on the Overview page, just empty of content on the Article page.
No errors in the Apache logs.
In rt.log only:
[Wed Oct 31 20:54:37 2007] [debug]: RT::FM::ArticleCollection Limit
called :QUOTEVALUE 0 VALUE LastUpdated FIELD Created OPERATOR !=
(/usr/local/rt3/lib/RT/FM/ArticleCollection_Overlay.pm:78)
not sure if it’s relevant?
I’m still troubleshooting, but I wonder if anyone else might know where
I went wrong?
Thanks,
Roy
PS: Solaris 10, Perl 5.8.8, Apache 2.2.6, mod_perl 2.0.3, MySQL 5.0.45
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran@mdibl.org
I found that I had to upgrade to 2.1 and run the associated scripts
first, then upgrade again to 2.2.1.
Roy McMorran wrote:
I found that I had to upgrade to 2.1 and run the associated scripts
first, then upgrade again to 2.2.1.
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.
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.
-kevin
Kevin Falcone 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
mcmorran@mdibl.org
Roy McMorran wrote:
Kevin Falcone 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.
OK, I backed out and re-upgraded as far as 2.1.40 and had the same
result. No custom fields selected; no content visible. Not much point
in proceeding to 2.2.x.
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).
Ignore that bit about the formatting. I had changed that earlier on
this test server.
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran@mdibl.org
Roy McMorran wrote:
Kevin Falcone wrote:
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.
In the end I just manually re-enabled the correct custom fields for the
18 classes I had.
Thanks for the input everyone.
Cheers,
-r
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmorran@mdibl.org