the surest way to insure that you don't get "good support" is to appear on the list and start dissing the project. I don't know what this particular problem is, but from a quick look it looks like you have screwed something up in your install - possibly a unix/windows line ending problem. People here are more than generous with their time and advice and the idea that "support is unusually thin" is laughable. Please don't go spreading FUD about this project. Also - you are in the wrong forum - you should be in "support" not on the dev list. People are trying to get a new release out.
Quick and easy support is something people pay for, and even then it's
often neither quick nor easy.
I'm a strong PHP programmer and I don't generally need that much help, but Drupal code is unusually hard to follow and the support is unusually thin - even for an open source project. I'm certainly not the first person to say this - I've seen a lot of threads about this in the Drupal forums.
I like Drupal's capabilities, but I can't just stay dead in the water like this. Pretty soon I'll have no choice but to find another CMS program to use.
If that warning comes with no message ahead of it, it most often means
that some included file, such as a module or something, has whitespace after the ?> at the end of the file. Check your contributed modules and custom code to make sure there is no whitespace there.
Thanks, I'll look.
-----Original Message----- From: development-bounces@drupal.org [mailto:development-bounces@drupal.org] On Behalf Of Earl Miles Sent: Sunday, December 18, 2005 4:52 PM To: development@drupal.org Subject: Re: [development] authentication hooks - PLEASE HELP
Sheryl (Permutations Software) wrote:
Ugh. I'm still getting the error message:
warning: Cannot modify header information - headers already sent
Honestly... This is so frustrating. I think it would take less time to
write
my own CMS. How come there is not support?
Quick and easy support is something people pay for, and even then it's often
neither quick nor easy.
If that warning comes with no message ahead of it, it most often means that some included file, such as a module or something, has whitespace after the ?> at the end of the file. Check your contributed modules and custom code to make sure
there is no whitespace there.