Enabling the latest htmlArea in 4.4 causes these header output areas.

It is due to some misconfiguration on my part? I upgraded an existing system rather than installing from scratch.

warning: Cannot modify header information - headers already sent by (output started at c:\pathtodrupal\htdocs\modules\htmlarea.module:464) in c:\pathtodrupal\htdocs\modules\user.module on line 674.

warning: Cannot modify header information - headers already sent by (output started at c:\pathtodrupal\htdocs\modules\htmlarea.module:464) in c:\pathtodrupal\htdocs\includes\common.inc on line 230.

Comments

jon’s picture

i'm doing the same thing (and trying to update the module itself so it is compatible). how did you go about upgrading?

it is my understanding that core modules of drupal have to be patched in order for the module to work. have you done this yet? i did a dry run of the patch and as expected, much of the patch would fail.

i'm working on fixing that, as of course the core modules have changed.

speaking of: this kind of thing perplexes me, as i come from a background where you don't create modules that require a patch of core functionality--but i dunno if this is a module design issue or a drupal design issue, or php limitation, yet.

why should a module *require* that you patch core functionality? why isn't drupal designed with pluggable text area functionality? or better yet, is it? (because i'm hoping the answer is yes--i'm rusty enough at php to not know whether it offers an easy way to define an interface as opposed to concrete classes(functions/whatever)).

anyway, help us! :)

j.

---
Jon Madison, Consultant
Thought For Food Tech, LLC
http://www.tfftech.com/