[rt-users] Complex search for users, as for tickets
Is it possible in RT to : - do a search for users with some search parameters? - as for tickets, include this search within a dashboard ? Thanks, Gaston Huot
[rt-users] Problem with 4.0.22 --> 4.2.9 upgrade
Hello - Upgraded a test RT server from 4.0.22 to 4.2.9 yesterday. Upgrade went smooth and I didn't run into any real big issues. The issue is now when logging in to RT. I get to the login just fine and I enter my credentials. Upon hitting the *Login* button I immediately get sent to a page that shows: Not Found The requested URL /HASH(0x7f632a4a2b98) was not found on this server. With a URL of https://*fqdn*/HASH(0x7f632a4a2b98). However, if I modify the URL to just the *fqdn* of my server, I am logged in just fine to RT and all seems well. If I logout and attempt to login again -- I'll get the same error with a different HASH number following. The mason data cache was cleared after the upgrade. What would cause such an error? Thanks! -- Max McGrath Network Administrator Carthage College 262-552-5512 mmcgr...@carthage.edu
Re: [rt-users] Problem with 4.0.22 --> 4.2.9 upgrade
On Wed, Nov 26, 2014 at 10:47:13AM -0600, Max McGrath wrote: > Upgraded a test RT server from 4.0.22 to 4.2.9 yesterday. Upgrade went smooth > and I didn't run into any real big issues. > > The requested URL /HASH(0x7f632a4a2b98) was not found on this server. > > With a URL of https://fqdn/HASH(0x7f632a4a2b98). > > However, if I modify the URL to just the fqdn of my server, I am logged in > just > fine to RT and all seems well. If I logout and attempt to login again -- I'll > get the same error with a different HASH number following. A similar issue was caused by using older RT-Authen-ExternalAuth with newer RTs. The version you're upgrading from should have exhibited the same bug (this was specific to versions prior to 4.0.8). It's worth checking your customizations and plugins to see if you have stale versions around, especially if you've touched Login. -kevin pgpmHJzN4px14.pgp Description: PGP signature
Re: [rt-users] Problem with 4.0.22 --> 4.2.9 upgrade
Thanks! That seems to have fixed it! I was still on version 0.10 of RT-Authen-ExternalAuth. Got to 0.25 and the problem went away! Thanks so much! Max -- Max McGrath Network Administrator Carthage College 262-552-5512 mmcgr...@carthage.edu On Wed, Nov 26, 2014 at 1:29 PM, Kevin Falcone wrote: > On Wed, Nov 26, 2014 at 10:47:13AM -0600, Max McGrath wrote: > > Upgraded a test RT server from 4.0.22 to 4.2.9 yesterday. Upgrade went > smooth > > and I didn't run into any real big issues. > > > > The requested URL /HASH(0x7f632a4a2b98) was not found on this server. > > > > With a URL of https://fqdn/HASH(0x7f632a4a2b98). > > > > However, if I modify the URL to just the fqdn of my server, I am logged > in just > > fine to RT and all seems well. If I logout and attempt to login again > -- I'll > > get the same error with a different HASH number following. > > A similar issue was caused by using older RT-Authen-ExternalAuth with > newer RTs. The version you're upgrading from should have > exhibited the same bug (this was specific to versions prior to 4.0.8). > It's worth checking your customizations and plugins to see if you have > stale versions around, especially if you've touched Login. > > -kevin > >
[rt-users] plugins link to module file, not package file
Hey guys and gals, been a long time. I’m doing an upgrade from 3.8.5 to 4.2. It seems to be going well. I’m liking the changes. Other than some confusion about what order to do things in (see my other message) the one thing I can’t seem to wrap my head around is the new plugin setup. First, yay! I like the idea of what you’ve done with plugins, keeping them local and the simplified syntax in RT_SiteConfig.pm. [in which I wander in the wrong direction… read and giggle] However, I can’t find any plugins other than yours which are built in these new packages you document at https://www.bestpractical.com/docs/rt/4.2/writing_extensions.html What is the fallback method for installing the other style modules? How do I get from a .pm file to an installed module. Can I manually create the directory structures and copy these into place? I see some details there but it doesn’t inspire confidence that everything I need to know is there. A breakout of the directory structure would be really helpful. [forehead slap] I was almost done with this e-mail when I realized the problem. If you go to http://bestpractical.com/rt/extensions.html and you find the extension you are looking for, the link to the Homepage for the extension actually links to the main module, and not to the extension package. Example for one Homepage link takes you to: http://search.cpan.org/dist/RT-Extension-MandatorySubject/lib/RT/Extension/MandatorySubject.pm If you’re a bit tired and under-caffeniated, or just plain new to RT, it may not be clear to you that you need to remove a bunch from the URL to find the extension package. In my opinion, it would be much better to link to the package instead of the module file, like so: http://search.cpan.org/dist/RT-Extension-MandatorySubject/ I did some random spot checking, and this appears to be true for every module shown there. -- Jo Rhett +1 (415) 999-1798 Skype: jorhett Net Consonance : net philanthropy to improve open source and internet projects.
[rt-users] unordered mismash of upgrade instructions
Hey guys and gals, been a long time. I’m doing an upgrade from 3.8.5 to 4.2. It seems to be going well. I’m liking the changes. Glad to see RTFM integrated. My one big question here that I think the documentation could definitely improve upon, is what order to do the changes in? There are changes in every one of these pages and there’s no clear outline for which ones go first. https://www.bestpractical.com/docs/rt/4.2/README.html https://www.bestpractical.com/docs/rt/4.2/UPGRADING-3.8.html https://www.bestpractical.com/docs/rt/4.2/UPGRADING-4.0.html https://www.bestpractical.com/docs/rt/4.2/UPGRADING-4.2.html https://www.bestpractical.com/docs/rt/4.2/UPGRADING.mysql.html I build the new installation on a new system so I’ve done a test upgrade the following way — totally just guessing which things to do in which order. Can someone take a moment to validate if I did it right? 1. Loaded a backup of the running system's database, renamed to rt4 2. Installed apache2 and mod_perl2, set up vhost according to https://www.bestpractical.com/docs/rt/4.2/web_deployment.html 3. Download 4.2.9, extract, ./configure --with-web-handler=modperl2 --with-web-user=apache --with-web-group=apache 4. sudo make fixdeps 5. make install 6. perl etc/upgrade/upgrade-mysql-schema.pl rt4 rt_user password > ~/update.sql (read and saw only changes to utf8) 7. mysql -u rt-user -p rt4 < ~/update.sql 8. Cleanup from UPGRADING-3.8 $ cd /opt/rt4 $ perl -I /opt/rt4/local/lib -I /opt/rt4/lib etc/upgrade/shrink_transactions_table.pl $ perl -I /opt/rt4/local/lib -I /opt/rt4/lib etc/upgrade/vulnerable-passwords $ perl -I /opt/rt4/local/lib -I /opt/rt4/lib etc/upgrade/vulnerable-passwords --fix $ perl -I /opt/rt4/local/lib -I /opt/rt4/lib etc/upgrade/split-out-cf-categories 9. Database upgrade $ perl -I/opt/rt4/local/lib -I/opt/rt4/lib sbin/rt-setup-database --action upgrade --prompt-for-dba-password $ perl -I /opt/rt4/local/lib -I /opt/rt4/lib etc/upgrade/upgrade-articles $ sbin/rt-validator --check $ sbin/rt-validator --check --resolve I’m thinking that perhaps step 8 should have been done before 6 and 7, but it seems to have worked and it displays the tickets and seems to operate properly. -- Jo Rhett +1 (415) 999-1798 Skype: jorhett Net Consonance : net philanthropy to improve open source and internet projects.
[rt-users] docs improvement suggestion for full-text searching
So the documentation at https://www.bestpractical.com/docs/rt/4.2/UPGRADING-4.0.html says: > Since 4.0.0, RT's ticket content search is disabled by default because of > performance issues when used without full text indexing. For details on how > to re-enable it with (or without) full text indexing, see > docs/full_text_indexing.pod. However this URL https://www.bestpractical.com/docs/rt/4.2/full_text_indexing.html contains only information on how to enable full text indexing, and no information on how to enable it without the indexing. Seems like you need to add the information from http://blog.bestpractical.com/2011/06/full-text-searching.html to the top of this page. -- Jo Rhett +1 (415) 999-1798 Skype: jorhett Net Consonance : net philanthropy to improve open source and internet projects.
