Hullo--
Not entirely sure if this is an actual problem, or whether I'm just being really silly.
However, I created a cookie-based member login system, just a core at first, and it worked just fine. Recently I decided to expand the scripts and make them robust, and thought the best way was to split it up in small tasks to keep the code clearer. First off, I added a file including a function that checks for reserved/in use usernames. Now it seems that this function is somehow disabling sending html headers -more specifically the cookie- to the user. So I pop out from new user flow to check if the given name is in use (by include 'resn.php'; \n CheckName($newname)😉.. this seems to go ok. However, as the prog gets to the point where it's supposed to send the cookie, it states that it can't because the headers have already been initiated in 'resn.php', more specifically it's ending line ('?>').
This is probably a newbieish question, but if anyone could give a reason why (or a solution.), I'd be glad.
Thanks,
E
