When you say "no scary error messages," does that mean that you still encountered some messages?
The file /opt/rt4/local/html/Ticket/Elements/ShowSummary is a custom override, most definitely copied from an earlier RT version. You will need to identify what that override achieves differently to the stock version, and either copy those changes into a copy of RT v4.2.9's equivalent file, write those changes into a callback instead, or just delete the file altogether if it doesn't seem to bring any benefit. Altering the Makefile directly should never be needed; you should be able to pass options to the configure script instead. On Tue, 30 Dec 2014 8:47 pm Ruben <[email protected]> wrote: > Hi, > > I'm in the process of upgrading an RT4 installation to the latest release > (and after that: to do some performance upgrading). > > If I upgrade RT4.0.22 to RT4.2.9 the installation starts suffering from > multiple errors. The result of the upgrade is "clickable" and most of RT > seems to be working. I'm hoping that some pointers from people that are more > savvy to RT4's internals will help me resolve the issues I am facing. > > The upgrade has been performed on a cloned VM (ubuntu 12). There - > unfortunately - were/are no scary error messages encountered during the > upgrade. > > When we try to verify the upgrade it quickly becomes apparent that : > > Clicking on "Display" ( the generated URL being : > https://tickets.quanza.net/Ticket/Display.html?id=XXX where XXX is the > tickets ID) for an individual ticket results in this entry in the logfile: > > [2334] [Wed Dec 24 15:05:39 2014] [warning]: Use of uninitialized value in > concatenation (.) or string at */opt/rt4/sbin/*../lib/RT/Interface/Web.pm > line 1884. (*/opt/rt4/sbin/*../lib/RT/Interface/Web.pm:1883) > [2334] [Wed Dec 24 15:05:39 2014] [warning]: Use of uninitialized value in > concatenation (.) or string at */opt/rt4/sbin/*../lib/RT/Interface/Web.pm > line 1884. (*/opt/rt4/sbin/*../lib/RT/Interface/Web.pm:1883) > [2334] [Wed Dec 24 15:05:40 2014] [error]: no value sent for required > parameter 'Object' > Stack: > [/opt/rt4/local/html/Ticket/Elements/ShowSummary:98] > [/opt/rt4/share/html/Widgets/TitleBox:56] > [/opt/rt4/local/html/Ticket/Elements/ShowSummary:99] > [/opt/rt4/share/html/Ticket/Display.html:62] > [/opt/rt4/share/html/Widgets/TitleBox:56] > [/opt/rt4/share/html/Ticket/Display.html:63] > [/opt/rt4/share/html/Ticket/autohandler:66] > [*/opt/rt4/sbin/*../lib/RT/Interface/Web.pm:681] > [*/opt/rt4/sbin/*../lib/RT/Interface/Web.pm:369] > [/opt/rt4/share/html/autohandler:53] > (/opt/rt4/lib/RT/Interface/Web/Handler.pm:208) > > I think it might have something to do with this comment: > > MakeClicky handlers added via a callback are now passed an "object" key in > the parameter hash instead of "ticket". The object may be any RT::Record > subclass. > > on https://www.bestpractical.com/docs/rt/4.2/UPGRADING-4.2.html , but I'm > really kind of in the dark here. > > The steps performed (on the clone of my current RT4 setup) were: > > === > > wget https://download.bestpractical.com/pub/rt/release/rt-4.2.9.tar.gz > tar -xvf rt-4.2.9.tar.gz > cd rt-4.2.9 > > service apache2 stop > > make testdeps > make fixdeps > > altering Makefile to fit our user-setup: > > RTGROUP = rt > WEB_USER = www-data > WEB_GROUP = rt > > make upgrade > make upgrade-database > > rm -fr /opt/rt4/var/mason_data/obj > sed -i 's/LogToScreen/LogToSTDERR/g' /opt/rt4/etc/RT_SiteConfig.pm > chown www-data:rt /opt/rt4/var/data/gpg > > service apache2 start > > ==== > > I'm apologizing for asking the obvious if I really should have been heeding > instructions that are available more closely (please feel free to point that > out very blatantly :P). > > Any insights / thoughts on what might be going wrong here would be greatly > appreciated (if any more information is required: i'm happy to provide it)! > > Kind regards, > > Ruben > >
