My point about switching the lines in startup.pl was to give you a
better understanding of what was going on. It was not intended as a fix.
Looks like you've got your base.pm package declaration right. But for
your sites to work as intended, you've got to do that for all the
modules in /ORIG/m
Hello,
What you're doing is not recommended as you run into namespace issues.
Perl caches files and modules that were loaded in %INC, so if you have
files and modules with the same name, only one of them gets loaded.
Possibly, as an exercise, if you switch the order of the ORIG and COPY
lines
Michael Peters wrote:
On 11/29/2011 10:29 PM, Nishikant Kapoor wrote:
I have been running a ModPerl site fine with following configuration.
The problem started when I made a complete copy of the original site and
tried to run the two in the same environment. For some reason, calling
up the ORIG
Am 30.11.2011 um 15:02 schrieb Michael Peters:
> On 11/29/2011 10:29 PM, Nishikant Kapoor wrote:
>
>> I have been running a ModPerl site fine with following configuration.
>> The problem started when I made a complete copy of the original site and
>> tried to run the two in the same environment.
On 11/29/2011 10:29 PM, Nishikant Kapoor wrote:
I have been running a ModPerl site fine with following configuration.
The problem started when I made a complete copy of the original site and
tried to run the two in the same environment. For some reason, calling
up the ORIG site (http://127.0.0.1
Hello List,
I have been running a ModPerl site fine with following configuration.
The problem started when I made a complete copy of the original site and
tried to run the two in the same environment. For some reason, calling
up the ORIG site (http://127.0.0.1/ORIG/) now calls the COPY site at
