Title: [Plugin: afterRead] header already sent
Last modified: August 19, 2016

---

# [Plugin: afterRead] header already sent

 *  [reboltutorial](https://wordpress.org/support/users/reboltutorial/)
 * (@reboltutorial)
 * [16 years, 5 months ago](https://wordpress.org/support/topic/plugin-afterread-header-already-sent/)
 * Broken cause of this message.
 * [http://wordpress.org/extend/plugins/afterread/](http://wordpress.org/extend/plugins/afterread/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [Daniel](https://wordpress.org/support/users/warll/)
 * (@warll)
 * [16 years, 3 months ago](https://wordpress.org/support/topic/plugin-afterread-header-already-sent/#post-1345124)
 * Somehow extra spaces got added to the begining of afterread.php, if you remove
   those it will work.
 *  [Daniel](https://wordpress.org/support/users/warll/)
 * (@warll)
 * [16 years, 3 months ago](https://wordpress.org/support/topic/plugin-afterread-header-already-sent/#post-1345137)
 * Ok I figured out what was causing it, sort of.
 * I had set the character encoding to unicode on the main php. It would appear 
   that this was causing problems on some hosts. I have since changed the encoding
   to ASNC.
 * I can’t say I am too happy about having to use an obsolete encoding, but I suppose
   there isn’t much of another option.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘[Plugin: afterRead] header already sent’ is closed to new replies.

 * 2 replies
 * 2 participants
 * Last reply from: [Daniel](https://wordpress.org/support/users/warll/)
 * Last activity: [16 years, 3 months ago](https://wordpress.org/support/topic/plugin-afterread-header-already-sent/#post-1345137)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics