two galleries nested for a index.html whith log problems. Possible solution? two galleries nested for a index.html whith log problems. Possible solution?
 

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

two galleries nested for a index.html whith log problems. Possible solution?

Started by friisco, May 07, 2008, 10:51:13 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

friisco

Hello!  I did install two galleries under name myfavorites.dk linked between each other whith different database and everything works perfect besides that I can´t figure out how to make a unique log in that works for both.

How I did organize is:

index.html that links to index.html inside gallery1 that have a gallery2 inside

to be able to see gallery1 I did set that user have to log in so the can enter the gallery, but if they go to gallery2 thru gallery1 the are not log in.

I would like to know if it is a possibility to set a unique log in that reads in both side so user don´t have to login 2 times?

Maybe someone have a solution to my problem ???

I would be glad for that....

Thanks for the help.... ;)

Joachim Müller

I can't see the point of two galleries on one site, but anyway: that's your decision. But be warned: because it is not a bright thing to do, doing what you did goes largely unsupported.
Quote from: friisco on May 07, 2008, 10:51:13 AM
I would like to know if it is a possibility to set a unique log in that reads in both side so user don´t have to login 2 times?
Yes, that's possible. It has even been asked and asnwered before, so you better search the gallery. You basically edit include/init.inc.php of one gallery (beware: core file modification - not a bright idea!) and change reference to the members table accordingly; look for the section$CONFIG['TABLE_PICTURES']   = $CONFIG['TABLE_PREFIX'].'pictures';
$CONFIG['TABLE_ALBUMS']     = $CONFIG['TABLE_PREFIX'].'albums';
$CONFIG['TABLE_COMMENTS']   = $CONFIG['TABLE_PREFIX'].'comments';
$CONFIG['TABLE_CATEGORIES'] = $CONFIG['TABLE_PREFIX'].'categories';
$CONFIG['TABLE_CONFIG']     = $CONFIG['TABLE_PREFIX'].'config';
$CONFIG['TABLE_USERGROUPS'] = $CONFIG['TABLE_PREFIX'].'usergroups';
$CONFIG['TABLE_VOTES']      = $CONFIG['TABLE_PREFIX'].'votes';
$CONFIG['TABLE_USERS']      = $CONFIG['TABLE_PREFIX'].'users';
$CONFIG['TABLE_BANNED']     = $CONFIG['TABLE_PREFIX'].'banned';
$CONFIG['TABLE_EXIF']       = $CONFIG['TABLE_PREFIX'].'exif';
$CONFIG['TABLE_FILETYPES']  = $CONFIG['TABLE_PREFIX'].'filetypes';
$CONFIG['TABLE_ECARDS']     = $CONFIG['TABLE_PREFIX'].'ecards';
$CONFIG['TABLE_TEMPDATA']   = $CONFIG['TABLE_PREFIX'].'temp_data';
$CONFIG['TABLE_FAVPICS']    = $CONFIG['TABLE_PREFIX'].'favpics';
$CONFIG['TABLE_BRIDGE']     = $CONFIG['TABLE_PREFIX'].'bridge';
$CONFIG['TABLE_VOTE_STATS'] = $CONFIG['TABLE_PREFIX'].'vote_stats';
$CONFIG['TABLE_HIT_STATS']  = $CONFIG['TABLE_PREFIX'].'hit_stats';
and modify it accordingly.