I think that's your browser. The code just makes it white.

Oh, okay. I'll go hunting. Thanks.

Another possible solution to the email validation thing: Put the user name and user ID as separate (hidden) fields on the form. When the form gets submitted, just validate the email address. Then concatinate them when the email gets sent.

Edit: If the user accepts the default, then the value of the radio button would be the user's email address (that's stored in the system). In that case, the extra hidden field with the user's name would be used.

tommy, seriously, look at my voting pages. IIRC, that's exactly what I do.

I looked at one of your voting pages last night. I didn't notice the extra hidden user field, though. I prolly just didn't look close enough.

(edit: I was under the impression that your solution was similar to my "let's ditch the user id entirely" one, so I just looked at enough to confirm that in my head.)

I did notice on your page that you kept the user's email address surrounded by < & > - that makes sense now.

There's no way to search for a specific user's profile unless you know their user id, right? This would be a useful feature. Gus?

I don't know if it's Gus you're looking for, P-C, at least wrt the feature requests. Am Chau is the keeper of that list.

Well, Gus came through with the Buffista map, so I figure he can do just about anything.

Yeah, but the Buffista map's not actually integrated into the site (yet). And when it is, it'll be done by me or one of the other volunteers.

Am Chau maintains a prioritised list of requests, and everything's behind the filter right now. Also behind the switch to PostgreSQL, I'm thinking, since that's coming along so well.

P-C, the feature request list is here. You can also find the list by going to the first post of this thread.

ita, am I right to assume that if/when the switch to PostgreSQL happens, it'll be at a different server? Because I ran into a problem with the switch to PostgreSQL, and my solution was... how should I say, inelegant. I'd like to redo part of it, but if we're on a server that has a later version of PHP the problem will magically go away.

it'll be at a different server?

I was thinking we'd road test it here first,to make sure all was good and we could move to a later server.

What version of PHP do you need? Is it one of the stable shipping ones? I had to write around a couple things when we moved here too, and i-Strata said the version that we'd been using wasn't ready for prime time, and that the version here was latest stable. But that was a million years ago now. Sure, we can upgrade on our own, but if they're willing to do it as part of the features package, we might as well do that.

Sorry, P-C, for talking about the magical list and not mentioning it's linked to in the thread header.