Hi Dave Not sure how many users are still in 3.8.x, let alone on Fedora, let alone went through a Fedora upgrade, let alone copied the installation over. In other words, you might be targeting a very small audience. Just a guess.
I'm personally on Ubuntu and RT 4.2.0, but I'll take a stab anyway. I wondered about your approach of "just copying the entire installation" -- Does that mean you moved a tar copy of the RT directory tree over (and did a database dump and restore to the new F19 box)? At the very least, I'd recommend downloading RT source and running the config and make testdeps to ensure you have all the proper Perl modules installed. Typically I install from scratch on the new box so I can be sure everything is built properly (e.g. missing dependencies, perhaps something is in a different place now, etc), and then copy over the RT_SiteConfig.pm and any customized code. On another note: I think in general it's frowned upon to post to both the development and user lists. - Brent -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of CLOSE Dave Sent: Wednesday, October 30, 2013 12:37 PM To: [email protected]; [email protected] Subject: Re: [rt-devel] RT pages without links I wrote: > I recently moved our copy of RT 3.8.7 from Fedora 8 to Fedora 19. I > would have preferred to concurrently upgrade to the latest RT but had > some problems converting the data base. So in the interest of time, I > took the simpler approach of just copying the entire installation. > > It works, mostly. In fact, the only problem I see is that ticket lists > on the dashboards are not links. Comparing the old and new > installations (both are running though DNS leads users to the new > one), I see almost exactly the same page layout and content. There are > two obvious differences. > > 1. Font selections are different. This is not critical and the new > fonts are usable. It's clearly an Apache difference. > > 2. On the default home page, the tickets listed under "highest > priority" and "newest unowned" are not active links. Comparing the > page source for old and new installations, it is obvious that the href > tags are simply not present on the new output. Other items, like the > queue summary, do have working links as they did before. > > Digging through the source code, I quickly got lost. I can see where > the collection-as-table class is specified but not where the > associated variables are added. It seems likely to me that something > in F19 is confusing RT but thus far I haven't found what. If I could > see where the variable information was added to the output, I suspect > I'd see some kind of test that is now getting a different answer and > that that test would lead me to the solution. > > So, if anyone can tell me the cause of my problem right away, that > would be much appreciated. But, if not, then a clue on where to look > in the source code might help almost as much. I'm surprised and disappointed that no one seems able to help with this issue. Did I omit something important when describing the problem? -- Dave Close
