Gerald Richter wrote: > > > > > Ok, I have received Embperl-2.0b5_dev-1 from you. With it, I still get > > the error above. Here is some more detailed information, if it helps: > > > > These info doesn't look very nice, also I can't reproduce any of there here. > > I have just uploaded 2.0b5, please try this, also I don't expect any changes > for your problems.
It seems a little better but still doesn't work perfectly with the more intensive EmbperlObject scripts we have. > > 7/ When Apache starts up, I get this message in the error log: > > > > [20042]SES: Embperl Session management enabled () > > > > Yet, whenever %udat or %mdat is accessed (e.g. from base.epl) the > > request stops. Ie, no more output, but no errors/warnings either... kind > > of strange... I don't have any sessioning configured in httpd.conf or > > startup.pl. > > > > 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? 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) $] 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? Still getting some other strange things as well that are scaring me... forever loops... When I change EMBPERL_DEBUG to what you said, /tmp/embperl.log ballooned pretty quickly. 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. 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)? It appears that the written parser is either a little more picky or a little less picky in some areas. -- Regards, Wim Kerkhoff, Software Engineer Merilus, Inc. -|- http://www.merilus.com Email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
