If I might make two quick suggestions...

1. I really like the old censor feature from Classic. Type in a word and it's get "starred out *****" regardless of whether someone adds any characters before or after it. Nice and simple, and does the job.

2. Forgotten passwords. Do the passwords have to change every time someone tries to retrieve them? What's the upside, security? The downside is that people sometimes type in other users' data just as a prank, so because of such jokers people end up having to access their email just to be able to log in again. Maybe allowing users to switch this off in the Member Profile would do the trick.

Conrad, the current censor should work exactly as you describe in your first point.

For your second point - the password emailed is a temporary password that is stored separately from the normal password. Sending a temporary password won't log a user out or anything.

>Do the passwords have to change every time someone tries to retrieve them

Passwords are stored in the database in an one way encypted way, that's why it is not possible to to send you your old one password if you forget it.

OKay, so all your integration is at the database level, not the code level? Or do you actually include the Threads libraries in the rest of your pages?

I have main.inc.php called on almost every web page, which is about the only thing I need to include for authentication. From there I can use any number of functions in the Threads libraries...good stuff. So you could say I do both.

One thing you helped me remember was that I always meant to code a bit of a referrer so that a use could log in to the "site" (ie Threads) from any page I have the login code, and then be returned to that page instead of My Home or Index.

Might work on that today!

Ah, okay... then I have some good news and some bad news for you.

Good news number one - the new login code can automagically redirect you back to where you came, as long as you're on the same domain name.

Good news number two - you can still just include main.inc.php to get the environment, as well as everything you need to authorize the user, etc.

Which is the bad news - the code is now much more intrusive, and will try to reconfigure some PHP settings on the fly, and do some other things that might not play well with your existing code. But that is sort of to be expected.

Not worried at all - looking forward to tinkering with the new code and functions to see what I can get it to do. A lot of my stuff is templated, so I should be able to reconfigure things fairly quickly.

But great to hear about the login code redirect and main.inc.php!

Would be nice if the CP would allow not only backing up the database but also restoring it. Seems like a small php file will do the job - I tried the first one mentioned in this thread and it worked perfectly. Would be great if something like this was already included in the CP, which currently only backs up the database but won't import it in case something goes wrong or if someone moves servers.