problems with logging in problems with logging in
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

problems with logging in

Started by sharky, October 26, 2007, 10:14:06 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

sharky

hi all!

sorry if i open many different threads but unfortunately i need many times help.. :)

i already used the search function but found the solution only for the version 1.3 of coppermine.

my problem is that i bridged the gallery with phpbb 2.0.22 but sometimes it does not recognize that i am logged in. i cant post the URL because i am on a local installed webserver.
so if i am in the Board (logged in) and go then to the gallery then very often i am not logged in there. i need to go back to the board, log out, go to the gallery, click on the login button, wich directs me to the login on the board, login, and then i am redirected to the gallery again. tried to clean cookies, to change cookie name but still nothing. is the issue known or do onli I have it? is there a way to solve it? thank you

igor

sharky

ok i have set up a dyndns.. here is the url:

gallery: http://sharkyenergy.dyndns.org/gallery
phpbb2: http://sharkyenergy.dyndns.org/phpBB2

username: sharky
pass: admin

this is only a local test account so no problem if you mess up something. the user has admin rights

Nibbler


sharky

Fixed localhost thing! sorry...

for me it works now on my local serve, but online i have EXACTLY the same settings (only server url is different) and there it does not work.


sharky

another thing i forgot to say. as you see the cookie domain is empty in the phpbb. i tried on the online version to set .mtbs3d.com as cookie domain ant wasnt able to login anymore even on the board. i had to revert it trough the database. could this empty field be the cause of it?