Anyone else experience PHP and Apache prepending a byte-order mark to output after upgrading to PHP7? I feel like there's some configuration bit I missed, but I can't seem to google my way there.
-
-
Any whitespace characters at the beginning or end of files?
-
I'll go check
End of conversation
New conversation -
-
-
Closing ?> tags at the end of library files usually cause problems like that
-
Will investigate; thank you!
End of conversation
New conversation -
-
-
Aha! I started seeing these a day ago, and tweaked my scripts to throw away the BOM and hope everything was fine.
I figured it might be a transient thing you’d fix. -
Yeah, trimming the output before parsing works fine. I just want to understand where it got introduced.
- Show replies
New conversation -
-
-
php 0.1 on ms-dos is a very charitable way of justifying the choice :b
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Had the same issue. Pretty sure it was a php.ini issue. Try with new fresh config
-
That’s likely due to the default_charset setting. Default changed to UTF-8 from ISO-8859-1 in 5.6.
End of conversation
New conversation -
-
-
Definitely remove closing tags from the end of any file that isn't supposed to output, and check for extra spaces before opening tags. PHP will automatically output strings outside of PHP tags as that used to be the default way PHP worked (PHP embedded in HTML files).
-
Even if that doesn't resolve your BOM issue, it's generally a good idea.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.