PROJECT: Coppermine to eFiction bridge AUTHOR: Goku Girl (Miyako Jones) INFO URL: http://www.efiction.org/forums/index.php?topic=4486.0 UPDATED: January 01, 2009 DESC: Coppermine will share the user database of eFiction (version 3.0), which will result in a single account being used with both sites. ADDL INFO: The eFiction archive is already bridged with another eFiction archive, which means that it shares the second archive's user information. PROBLEM: There are numerous issues, most of them SQL database-related. SOLUTION: There were several issues with the original bridge file (on Calic0cat's website). It was set up for her particular configuration and not a general one. 1) Her Coppermine gallery is in a subdirectory of her eFiction installation and mine are parallel in the root folder. I had to change the _BASEDIR variable (v3.3+) to reflect this structure. Otherwise, the bridge wouldn't be able to find the config file. 2) Around line 110 there was a problem with the $sql variable being passed to the function. If it's incorrect, the bridge can't find the author (user) table. The error being printed was very vague (an unnamed fatal error). I added "echo $this->usertable;" to the file to return the value of the variable and discovered that another setting was wrong. If the settings prefix in eFiction's config.php file is the default (settings) then the $sql variable won't be set correctly. It can be fixed by adding a line before the database connection settings. "$settingsprefix = 'PREFIX';", where PREFIX is the prefix of the author table (minus the "fanfiction_" part). 3) Part of the table prefix for eFiction was being left out if you were using a custom settings prefix. I had to add "fanfiction_" to the IF statement that determined what data was to be associated with the "prefix" array key. The ELSE part was fine. 4) When I login to eFiction, it doesn't carry over to Coppermine. This is the most recent problem. I'm aware that it's cookie-related, but I'm still trying to track down the exact problem. I'm starting to think that I'll have to override the cookie path settings in eFiction to fix it.