Hi, I am not sure, but I use this at the start of every script.
[$syntax EmbperlBlocks $] When I switched to embperl 2 I looked for ages to get my embperl 1.3 pages to work. Anyway I am still looking for a global way to turn table and html parsing of. but if I remember correctly this worked for me. (But I did have to edit all those pages to add [$syntax EmbperlBlocks $] to the top.) This is what I have im my httpd.conf but I am not sure if this still is used by embperl 2.x --- PerlModule Embperl Embperl_UseEnv on SetEnv EMBPERL_DEBUG 0 SetEnv EMBPERL_OPTIONS 2064 SetEnv EMBPERL_ESCMODE 0 PerlSetEnv EMBPERL_COOKIE_PATH "/" PerlSetEnv EMBPERL_SESSION_CLASSES "MySQL Semaphore" PerlSetEnv EMBPERL_SESSION_ARGS "DataSource=dbi:mysql:session UserName=** Password=**" ---- Hope this helps Met vriendelijke groet, Hans de Groot Quoting Heath Morrison <[EMAIL PROTECTED]>: > Hello, > > First, let me say that I've been using Embperl 1.x since 1999 with > incredible success. I've used it in virtually all my web-based projects > since then. Thanks Gerald for something that truly is exactly what I've > needed for years and years. > > I've decided to make the push from 1.3 to 2.0. I'm having some trouble > with the table parsing (something that I've always felt was best left > disabled) in 2.0. Since I cannot disable it in 2.0 I've been working > around it, but I've hit a bit of a wall that I don't know how to get > past. Please advise why the following HTML fails to parse successfully, > > [$ if (0) $] > <table align='center' width='50%'> > <tr><td align='center' bgcolor='#66AA66'> > [$ endif $] > > Test! > > [$ if (0) $] > </td></tr> > </table> > [$ endif $] > > This generates the following crash message: > > Error (no description) Unstrutured forward jump > > ...notice that those 'if' blocks should not be entered. If I set those > conditions to '1' instead of '0' everything works as expected. If I > remove the if blocks (or comment them out with [# #]) everything works > as expected. > > My actual HTML is of course much more involved, but suffers > from the same problem outlined here. Please let me know if you guys > have any suggestions. In particular, if anybody can suggest a means of > disabling table parsing that would probably make me happiest :) > > Thanks again! > > Heath > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
