Yep, that is there fine already.. PerlModule Apache::Filter PerlModule Apache::RegistryNG PerlModule Apache::RegistryBB PerlModule Apache::Compress PerlModule Apache::RegistryFilter
<Location ...> SetHandler perl-script PerlHandler Apache::RegistryNG </Loction> # runtime, this location generates the error, browser sees 500 internal server error <Location ...> SetHandler perl-script PerlHandler Apache::RegistryBB </Location> <Location ...> SetHandler perl-script PerlSetVar Filter on PerlHandler Apache::RegistryFilter Apache::Compress </Location> It is like RegistryBB is not exporting or inheriting the handler properly? All I have to do to make the 2nd location work perfectly, is change BB to NG, but then my script is recompiled whenever the disk date changes. I prefer to control that with HUP, or let them roll naturally. -Justin GY> justin wrote: >> Although I can get RegistryNG working just fine, I can't seem to get >> RegistryBB working. It insists it cannot find the handler, even though I >> should be able to just change NG to BB in the config file, right? >> >> RegistryBB seems not to have changed since modperl 1.13 or prior, and >> was usable there. >> >> What is it, or am I, missing here? >> >> [Thu Oct 23 19:06:50 2003] [error] Undefined subroutine >> &Apache::RegistryBB::handler called. GY> it's been ages since I messed with any of this stuff, but both NG and BB are GY> method handlers, and I've typically seen that message when the module isn't GY> preloaded for method handlers. GY> so, try adding GY> PerlModule Apache::RegistryBB GY> or otherwise use()ing BB in a startup.pl to get it recognized. GY> HTH GY> --Geoff
