Hello
They have upgraded the server to 4.3.10 (php) and suddenly login does not work?? I log in but nothing happens.. I can not see the admin panel, it still wants me to login??? please assist.
Cheers
Matt
Link, with non admin test account, please.
Hello & Thank you
Here is the link: http://www.pekjon.com/cp/
Cheers
Matt
You didn't post a test user account. If you can't make one via Coppermine, use phpMyAdmin to add a user to the cpg133_users table.
Hello
It is really funky.. it used to function great on the old server, since they upgraded to new platform it went all sideways?
I think it is server installation problem, save_path? here is the pw and un (both same): pgdm
You can not login? it does not remember..
Thanks
Matt
where did you get your coppermine package from? There's something fishy with it, after trying to log in, there's a session id attached to the url that is not suppossed to be there. Did you modify anything?
Hello
No I got it from here I mean from sourceforge and I did not play with the script at all/ no modification..
They have just moved my sites to new servers.. and since than all my logins in all .php scripts acting the same way and they say it is because of the script... and I say it was working fine and now it does not, so check your installation??
Could you tell me what is the fishy part that you mentioned? please Ihave been dealing wiht these guys for almost 2 weeks..
Why do you think, login would be a problem? I have the same /exactly the same CPM installed on my local server and works like a magic and I love it.
Thank you for your support, I would really appreciate if you could tell me why this would happen?
Cheers
Matt
if all logins of all your web based apps behave the same way, then this certainly is not a coppermine issue, but a server setup issue. The usual behaviour of coppermine is not to add the session ID var to the url in the address bar of the browser, so this is something either you or your webhost has done deliberately. As you claim not to have changed the package, it must have been your webhosts fault. Tell them to view this very thread, they should know what to do.