> By "hide the error" I mean that if an ErrorDocument 500 is enabled in
> httpd.conf, EMBPERL_OPTIONS is set to return the error in the Apache
request,
> and I call a template in base.epl that causes an error then it seems to
> simply abort that current template and continue on, as opposed to sho
By "hide the error" I mean that if an ErrorDocument 500 is enabled in
httpd.conf, EMBPERL_OPTIONS is set to return the error in the Apache request,
and I call a template in base.epl that causes an error then it seems to
simply abort that current template and continue on, as opposed to showing me
>no i doesn't have ClearModuleList somewhere in my httpd.conf.
>But i have downgraded to apache-2.0.39 and mod_perl-1.99.04
>and now it works. But don't ask me why?
So it seems to be a problem of the new Apache or mod_perl versions. I
already have downloaded them, but not yet tested. I will do it
> Hi, I am looking for the PC C compiler. Does any one
> know where I could download it? Thanks.
>
I use MSVC++, of course it's not free, but the smallest version isn't very
expensive and fits for most needs.
If you like to have OpenSource try gcc together with cgywin, but I never
have tried it
>
> I do a couple Execute calls in my base.epl and essentially they hide the
error
> from the parent process.
>
What do you mean by "hide the error"? If a error happens anywhere, you
should get an error page, don't you?
Errors should propgate to the parent, unles you use the errors => parameter
(
> It appears that this was triggered by having two different versions
> of one of my libraries for two sites on a shared server. Although
> the versions were compatible, if the same process hit one site and
> then later hit the second, we could run into problems. The first
> site uses straigh
>
> http://www.conceptionstore.com> border=0>
>
> becomes:
>
> border=0>
>
> which is un-renderable.
>
Go to Embperl/Syntax/HTML.pm line 364 and add :. and / to the list of
recognized chars should do the trick
Gerald
-
Gerald Richter
It appears that this was triggered by having two different versions
of one of my libraries for two sites on a shared server. Although
the versions were compatible, if the same process hit one site and
then later hit the second, we could run into problems. The first
site uses straight Embperl,
