On Wed, Apr 20, 2011 at 03:51:57PM -0400, Mike Johnson wrote: > Ah... that opens my eyes a bit more... > > > How do I tell get /opt/rt3/local/plugins/ExtractCustomFieldValues in > @INC? > > how did it end up there, that isn't the directory structure for RT > plugins. > > I put it there trying to mimic how ExternalAuth worked. I've backed it out > now and used the
That isn't how ExternalAuth works either, it works with a standard make install and would be in local/plugins/RT-Authen-ExternalAuth > Makefile for it to place itself where it wants to. > It placed the ExtractCustomFieldValues.pm in > /opt/rt3/lib/RT/Action That's wrong. What version of RT and the module are you running. 3.06 (newest on CPAN) and 3.8.10 install into local/plugins/RT-Extension-ExtractCustomFieldValues as expected. -kevin > So now my Plugin's looks like this > Set(@Plugins,qw( > RT::Authen::ExternalAuth > RT::Action::ExtractCustomFieldValues > )); > > How did you install RT-Extension-ExtractCustomFieldValues > I believe you missed a step from the README included with the > extension. > > Please note, you do not ever just untar an extension into /opt/rt3 > You untar it into your home or a source directory and follow the > directions in the README which will ensure that it is placed into the > proper location for RT. > -kevin > > Thank you Kevin, I did not know that! > I have backed out what I did, and followed the correct method and it seems > my setup is no > longer throwing errors and RT can run :D > I appreciate the responses and knowledge that I've gained from them. > -- > Mike Johnson > Datatel Programmer/Analyst > Northern Ontario School of Medicine > 955 Oliver Road > Thunder Bay, ON P7B 5E1 > Phone: (807) 766-7331 > Email: [1][email protected] > > References > > Visible links > 1. mailto:[email protected]
pgpmezZsI5p6N.pgp
Description: PGP signature
