[mapserver-dev] Undocumented changes in PHP MapScript

[Alan Boudreault]

Mike, 

Yes I'd like a test case to reproduce the issue. Could you also try your test 
case in normal CGI mode rather than the fcgi. 

Alan

On April 25, 2011 02:02:00 pm Mike Leahy wrote:
> Hi Alan,
> 
> That's the main problem I had when I ran into this - I don't get useful
> error messages:
> 
> [Mon Apr 25 13:56:37 2011] [warn] [client 127.0.0.1] (104)Connection reset
> by peer: mod_fcgid: error reading data from FastCGI server, referer:
> https://localhost/myapp/
> [Mon Apr 25 13:56:37 2011] [error] [client 127.0.0.1] Premature end of
> script headers: index.php, referer: https://localhost/myapp/
> [Mon Apr 25 13:56:37 2011] [error] mod_fcgid: process /usr/lib/cgi-
> bin/php5(13148) exit(communication error), get unexpected signal 11
> 
> Usually, PHP will give me errors with line numbers for me to inspect, but
> I'm guessing this is a segfault.  As you can see, I'm running PHP as CGI -
> could that be an issue?  Is there something you'd like me to try to debug
> this?
> 
> Mike
> 
> On April 25, 2011 13:34:25 Alan Boudreault wrote:
> > Hi,
> > 
> > The methods setXY and setXYZ are still present. What do you mean? What
> > error message do you get when you try to use it? Not sure what you means
> > about the error message of setXY method... could you point me the error
> > message you got?
> > 
> > 
> > Alan
> > 
> > On April 24, 2011 12:06:02 am Mike Leahy wrote:
> > > Hello List,
> > > 
> > > I have just given the 6.0 beta 7 a try, and overall the migration guide
> > > made most changes that affected my application very easy to deal with,
> > > and from my tests MapServer and PHP MapScript are working as expected.
> > > I'm looking forward to the final release.
> > > 
> > > I'm just wondering if there are any additional changes to PHP MapScript
> > > library that are known, but not yet documented in the migration guide. 
> > > I seem to have encountered at least one change that is not covered,
> > > which tripped me
> > > 
> > > up briefly.  As the migration guide notes:
> > > > Object properties can be set like all other php object. ie.
> > > > myObj->myProperty = 10;
> > > > 
> > > > NOTE: The set/setProperty methods are still available.
> > > 
> > > However, it seems that the pointObj->setXY() method is no longer
> > > present. This was easily substituted by directly setting the x/y
> > > properties (e.g., $oPoint->x = $x). I recognize this particular issue
> > > is fairly trivial, but since this change isn't covered in the guide. 
> > > I'm wondering if there might be other differences.  There's no mention
> > > of any methods other than 'free' being removed from the pointObj
> > > class.  In my case, the PHP code did not fail gracefully when it setXY
> > > method, and I had to hunt for a bit to find where in the code that the
> > > error was happening. In other cases, using removed methods produced
> > > useful error
> > > messages...so maybe something else has gone wrong specifically with the
> > > setXY method.
> > > 
> > > Best regards,
> > > Mike

-- 
Alan Boudreault
Mapgears
http://www.mapgears.com