Home ›
Parse error and other problems with include file- due to bad encoding or somethingParse error and other problems with include file- due to bad encoding or something
Submitted by Benjamin Melançon on October 15, 2007 - 5:55am
Searched words:
TextWrangler
Parse error: syntax error, unexpected $end in /Users/ben/workspace/repos/agaric/agaric-modules/place/5/place/taxonomy_location/taxonomy_location_admin.inc on line 1
renamed file and started a new one with Mac line endings instead of Unix:
evil_textwrangler-inserted-bad-characters-taxonomy_location_admin.inc
The new file worked. But very soon, a new problem:
warning: Cannot modify header information - headers already sent by (output started at /Users/ben/workspace/repos/agaric/agaric-modules/place/5/place/taxonomy_location/taxonomy_location_admin.inc:1) in /Applications/MAMP/htdocs/joeaustin/includes/common.inc on line 311.
Putting the functions in the main problem and dropping the include solved the problem, so it was definitely an encoding or a Macintosh-vs-Unix line break issue.
Yeah, they have problems with character encoding:
TextWrangler
a product of Bare Bones Software, Inc.
version 2.2.1 (186) of Wed, 14 Feb 2007
copyright ©1992-2007 Bare Bones Software, Inc.
Registered to Benjamin Melan?ßon
Resolution
More like this
- White Screen of Death due to taxonomy parent-child infinite loop
- Wireless Problems on HP Pavilion dv6000: Ubuntu or bad hardware?
- Load a node for a template file- in exactly the same way a node object is presented to a theme
- Parse syntax error unexpected T_SL caused by Subversion conflict
- Agaric wants Eclipse to flag the entire file prominently, not just a line, when it has a parse error
Comments
Post new comment