Odd one.
Users can register and activate fine. They can even
log in the very first time via the activation process;
however:
1) Users can then not log out until
a) I did some commenting out in the index.php (yes, the
sessions junk) but EVEN THEN, (when users finally
dind't get a blank screen) users could not logout if
using Firefox as when it takes you back to the
homepage, you are actually still logged in.
NOTE: I haven't tested this in IE yet, just Firefox.
The only way to actually get logged out is to manually
go into firefox cookie settings and delete all of the
specific domain cookies. In my testing scenario, I had
to go in and delete all test domain cookies except the
admin cookie, which I left in once I realized that I
could log the admin in and out with no problems (as
it's not part of CNB_YA).
NOTE: I think there are far too many cookies being
generated by CNB_YA and the automated mechanisms to
remove them at logout needs some serious work. While I
can appreciate the attempts to make this work with
things like Oscommerce, I believe that should be
considered a seperate issue with a seperate script as
it is not part of the needs for the baseline Nuke
Community and thus, those functions should be removed
from the baseline code. Just my 2 cents there.
2) Next, Users cannot log back in, once they have been
logged out. Not via either any login block, nor the
secondary login screen. I have reworked the
functions.php substantially to eliminate a few hundred
compliance and coding errors, and am hoping I didn't
miss a value in there somewhere in the process, but it
would be nice to know if anyone else is having this
problem.
3) Next, once logged in, users are not able to go to
any Your_Account sections. I get redirect limit
reached errors. I have no idea what is causing this.
I can browse userinfo from an admin ID, but I can't
even go to the YA index page as a user.
Finally, I now have all admin screens pretty much fixed
100% W3C Compliant after a substantial amount of
recoding. It would be nice if there was a place where
I could post this code so that it could be examined for
any problems, which there appears to be one or two with
the editing users from listnormal. From the admin
search, everything works great, but under certain
circumstances in the listnormal, I am brought to the
browse screen when trying to go to the edit or other
screens. It's hard to explain the process of what
makes that happen, but without writing a novel, I'll
simply say that it is related to what happens and what
is accessable (certain IDs) after deactivating or an
account.
I have also started working on the user screens again
and have managed to get the userinfo and a few other
screens 100% W3C Compliant and bug free.
Logged In: YES
user_id=1291247
Sorry about this guys.
When I got up this morning, I was trying to do a refresh of
the bugs screen since it was down last night and apparently,
it reposted.
Ooopsie.