> > Looks like you have Apache::SessionX installed, but not configured properbly? > > Doh! Yup, that's what it is. Just me being brain dead at midnight :-( > Maybe its possible to put something in the error log if the session > isn't accessible? >
I have tried to improve session handling and error reporting, but there is still something left to do ... > Disovered something else as well. Another of my developers had a line of > code like this: > > [$ foreach $h @$head $] > > Embperl2 barfs on it... had to change it to > > [$ foreach $h (@$head) $] > Yes, README.v2 contains a section called "The following difference to Embperl 1.x apply:", you will find this and other necessary modifications there. > Also, I have several objects that contain pieces of the layout (e.g. > sidebar.inc, sidebar_close.inc, etc). In sidebar.inc a <table> is opened > and the nav is put in a left table cell, leaving a <td> open for the > content which comes from Execute(*). Unless I put [$ syntax > EmbperlBlocks $] at the top of sidebar.inc, it automatically closes the > open table by adding </tr></table>. NOT what I want... Is there an > option for this? > [$ syntax EmbperlBlocks $] is the only option for that right now, also I plan to make table handling a little smarter, because you are not the only one for whom this is an issue. The problem when that all tags that Embperl parses, must be properly closed inside one file. If Embperl doesn't parse it, Embperl doesn't care. With [$ syntax EmbperlBlocks $] you simply turn off parseing off all HTML tags, while with $optDisableTableScan you where able to turn off only parsing of table tags in 1.3.x. The result stays the same. Due to the totaly different architecture of 2.0, it will not be possible to support $optDisableTableScan without any modifications of your source in 2.0. Maybe in the future something like [$option DisableTableScan off $] could work. I have to think about it. > Still getting some other strange things as well that are scaring me... > forever loops... That isn't nice... > When I change EMBPERL_DEBUG to what you said, > /tmp/embperl.log ballooned pretty quickly. Yes, that's what I exptected. > What I'm going to try later > is make some smaller test cases of what works and doesn't, and send > separate log files for each. That would of course even better. > I'll try setting up Embperl2 on another > server in a "clean" environment as well. > > In theory, are all Embperl 1.3.x scripts supposed to run under 2.0 with > little modifications, other then removing the old tags (optRawInput, > optDisableTableScan, etc)? Yes, it should run after the modfication mentioned in README.v2 > It appears that the written parser is either > a little more picky or a little less picky in some areas. > Yes, it works totaly different, by that giving totaly new possibilities, but some of the thing that were possible in 1.3.x can not work anymore. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
