Parsing rules
TQ White II
tq at justkidding.com
Sat Nov 3 08:48:52 PST 2001
SInce I installed Frontier 7, many of my webpages have broken.
I have tracked it down to changes in the way Frontier parses pages.
I do a lot of PHP and Javascript stuff with mySQL implications. That means
that I do a lot of string processing, especially in PHP. As a result, I
have a lot of strings that will become html tags later. That is, they have
> and <, as well as \ in them.
I have had many situations where I rendered a page of code (a PHP class)
with a minor change and spent a couple of hours debugging php language
errors.
I have found that sometimes a macro won't render until I stick an extra
angle brace in a comment in the line before the macro. I have millions of
'\r\n' strings that have their \'s stripped out by Frontier and I haven't
been able to figure out what to do about them. Sometimes the extra angle
brace trick works, other times, no.
Two questions:
Is there somewhere in Frontier that I can look at the code that interprets
this stuff (and perhaps work around it)?
Am I overlooking some way to prevent this behaviour?
Any ideas about what I should do? This is a real problem because it means
that I can't reliably make a small change to any of my systems unless I
know that I can 1) afford to have it down for hours and 2) have the time to
debug on my own.
thanks,
tqii
--------------------------------------------------------------------------------
TQ White II
708/763-0100
tq at justkidding.com
http://www.justkidding.com
Check out my latest addition:
http://justkidding.com/politics
--------------------------------------------------------------------------------
More information about the Frontier-Users
mailing list