Steve Daniels wrote:
> On 08/10/2007, Haris Zukanovic' <[EMAIL PROTECTED]> wrote:
>>  To be sincere, I can't imagine PHP being the source of the problem.
>>  Can anyone hypothesize on how it could be related to PHP?
>>
> 
> I had a quick glance at one of Pookey's error messages in the thread
> he quoted earlier you can see that the error was caused by an
> additional comma at the end of a line. 

You didn't' look closely enough I'm afraid :)

For the sake of otehrs, here's the code

1633 catch (Exception $e)
1634 {
1635   if (sfConfig::get('sf_test'))
1636   {
1637     throw $e;
1638   }
1639   try
1640   {
1641         $sfException = new sfException();
1642     $sfException->printStackTrace($e);
1643   }
1644   catch (Exception $e)
1645   {
1646     header('HTTP/1.0 500 Internal Server Error');
1647   }
1648 }
1649
1650 'action',
1651     ),
1652     3 =>
1653     array (
1654       'module' => 1,
1655       'action' => 1,
1656     ),
1657     4 =>
1658     array (
1659     ),
1660     5 =>
1661     array (
1662     ),
1663     6 => '.html',
1664   ),
1665 )
1666 );


You'll see that this is completely invalid PHP, it looks like perhaps
some code is missing, line 1650 should obviously be inside a $var =
array( or something like that.


-- 

Ian P. Christian ~ pookey.co.uk

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to