> addcslashes failed to put a slash in front of a single quote. Can anyone
> imagine how this could happen? Is it possible it didn't catch a multi-byte
> character? Am I back to charset issues?
I would guess: was the single quote something different than the
standard single quote, like a very simi
Cliff Hirsch wrote:
I had a very strange error, catastrophic yesterday.
PEAR Config writes a PHP array file like so:
'value',
param2 => 'val'ue2',
...
);
The writing process is what failed to generate the backslash. The
parsing
happens on subsequent page loads. The strange thing is that I
> On Tue, Feb 12, 2008 at 07:15:37AM -0500, Cliff Hirsch wrote:
>> PEAR Config writes a PHP array file like so:
>
> Your earlier description of the error coming up out of the blue makes it
> sound like you're writing out configuration files on the fly. Is that
> the case? If so, why? If not, pl
Cliff:
On Tue, Feb 12, 2008 at 07:15:37AM -0500, Cliff Hirsch wrote:
>
> PEAR Config writes a PHP array file like so:
Your earlier description of the error coming up out of the blue makes it
sound like you're writing out configuration files on the fly. Is that
the case? If so, why? If not,
> This doesn't make sense. How would a slashing failure lead to a parse
> error? Parsing should always happen first. Were you hacked? Are you
> sure it isn't an unsafe include?
No eval() in the code.
PEAR Config writes a PHP array file like so:
'value',
param2 => 'val'ue2',
...
);
The
Hi Cliff:
> The logs picked up the error after the damage was done: "PHP Parse error:
> syntax error, unexpected T_STRING". But the logs don't indicate why
> addcslashes failed to slash a single quote in this one instance.
Are you eval()'ing code? If so, _that's_ your problem, not the inability
> The logs picked up the error after the damage was done: "PHP Parse error:
> syntax error, unexpected T_STRING". But the logs don't indicate why
> addcslashes failed to slash a single quote in this one instance.
This doesn't make sense. How would a slashing failure lead to a parse
error? Parsin
>> On Feb 11, 2008 6:40 PM, Cliff Hirsch <[EMAIL PROTECTED]> wrote:
>>> I had a very strange error, catastrophic yesterday. addcslashes failed to
>>> put a slash in front of a single quote. Can anyone imagine how this could
>>> happen? Is it possible it didn't catch a multi-byte character? Am I ba
> Hi - do the Apache logs show you something (if you log them via
> php.ini) like warning or errors related to this issue?
Sorry, I meant `if you log the PHP errors using the log_errors
directive in php.ini'.
Matteo Rinaudo
> On Feb 11, 2008 6:40 PM, Cliff Hirsch <[EMAIL PROTECTED]> wrote:
> >
>
Hi - do the Apache logs show you something (if you log them via
php.ini) like warning or errors related to this issue?
Matteo Rinaudo
On Feb 11, 2008 6:40 PM, Cliff Hirsch <[EMAIL PROTECTED]> wrote:
>
> I had a very strange error, catastrophic yesterday. addcslashes failed to
> put a slash in fro
I had a very strange error, catastrophic yesterday. addcslashes failed to
put a slash in front of a single quote. Can anyone imagine how this could
happen? Is it possible it didn¹t catch a multi-byte character? Am I back to
charset issues? Unfortunately, I can¹t reproduce the error.
Cliff
11 matches
Mail list logo
