[eluser]tonanbarbarian[/eluser]
turning on full error reporting in PHP would have found the issue in this case
it would have come back with something like unexpected T_STRING
this assumes that the error was caused by something like
Code:
$x = array(
'first'=>'value1',
'second'=>'value2'
'third'=>'value3'
);
If however you mistakingly had a full stop rather than a comma it would not have been able to be found anyway except for a code review
There are a few rules that ALL PHP developers should use when developing
1. set error reporting to E_ALL, and fix or resolve all error, i.e. do not use @ to suppress an error if possible
2. disable asp and short tags in PHP.ini to ensure you always use full PHP tags, i.e. <?php ?>. This ensures that the code you write will function on any PHP configuration
3. optionally try setting your memory_limit in PHP down as low as possible. For code that might run on old hosting servers try setting this back to the PHP 4 default of 8M.
This last one is probably controversial but if you code for the least amount of memory possible your site will run fast and should run on any server config.