Hello -

I have CPP 2.7 installed on my virtual domain resource.neuronnet.ca which 'points' to http://www.neuronnet.ca/resource (aka: /home/neuronnet/domains/neuronnet.ca/public_html/resource). I've my settings.php set as $CookieDomain=".neuronnet.ca"; & $CookiePath = "/"; My sysadmin has configured the server to run PHP regardless if .php or .html-extensions.

I can add, remove, update users at whim fr admin.php . My difficulties is with members.php ... once I've inputted a new pwd & chose submit, I see 'changes saved' ... but my subsequent attempts to navigate through my protected pages kick me back indicating "invalid login" ... so I must log back in with the new password I've just saved.

My question is twofold:
- how do I 're-write' the session cookie once the user has updated their details (so they are not kicked-out)?
- how do I re-direct to a confirmation page on submission/update?

Though I've not tested File Protection, I am incredibly impressed with this solution. After more than 3 weeks of googling, I feel this is clearly the best package I've found.

I can e-mail an username & password if you would like to see a demonstration.

There are no need for you to send us login names and passwords because we know about that issue. It's hard to do anything about because when a user changes the password the cookie must be changed too, but since cookies can't be changed on the same page there will be problems even if you change the cookie.

Hello Bylla -

Thank you for the quick reply.

This is unfortunate as my client base are home PC users that may or may not understand/view this as unprofessional. Of course, I've updated the respective pages to reflect a notice of this need, but, well...

Will this prehaps be addressed in a future version of CPP? I would like to formally request such.

Thank you,
- Andrew

I would really like to say that I will have a fix for this until next version, but I have tried finding a solution since version 2.2......

Ouch. Would I guess correctly no browser would allow an 'over-write' method be executed as it would be too much of a security risk?

Oh well. Prehaps a major update in the technologies used would allow such. Until then, my users will just have to deal with it.

Cheers,
- Andrew