Quote:
|
Originally Posted by Brian It uses that info, so that's why I said it would work as long as you have the files uploaded and your config options set. Is there any reason you can't change the Coppermine config file and set the proper db/username/password there? |
Yes. I can't find what file '{$DFLT['cfg_f']}') refers to, and none of the files in the filesystem appear to contain either the Coppermine config variables (such as "$CONFIG['dbserver']") or the values to which those should refer (in that example, localhost) on a search for files containing the text.
This is a Coppermine install that was working on another host and server under PostNuke and was transferred directly to a new server -- not expecting it to act as a working install -- with the file system structure left intact and the SQL tables imported with no changes except renaming to remove the nuke_ prefix and owner_id of the photos changed to reflect the owner's userid under
vB instead of PN. It is not possible to install this script on the old server with PostNuke and Coppermine -- we left that host for very good reasons including reliability and uptime issues.
There appears to be no way to set the script to work with the relevant values, and there is no way to set them as "config options" in the import script as it currently exists.