I can’t enable PHP on the template that contains my Safecracker form if the form has this in it:

None of the PHP is parsed. If I remove that, the PHP works fine. Any ideas why putting the above lines in would kill the ability for the template to have PHP enabled?

Also, as a general question, for displaying the Safecracker File field at all, does it have to be inside the custom_fields pair? It’s the only custom field I have within that pair because I couldn’t get it to display at all otherwise.

Safecracker 1.0.3
Safecracker File 1.0.3

PHP on input or output?

To use any field outside of the custom_fields loop, you can use the {field:your_field_name} syntax, which does the same thing {display_field} does inside the custom_fields loop. The custom_fields loop parsing can be a little wonky, so I bet using the field: syntax will solve your problem.