I also tracked down why it looks like this, you know I am personally sick of hearing that you guys can’t duplicate the most simple problems, please don’t read into that too much. But if you want to test, then maybe doing so on a clean machine instance would help greatly.
I have found why this new release can’t be installed, which now introduces another error once we get past the DSN-Installer and too be honest, all it took was a clean machine too find this bug.
The problem is that ContentBox V2 when trying to install has ContentBox as a DSN hardcoded and doesn’t use the DSN entered.
May I suggest when doing testing, you deploy a staging server that can be fired up that is a clean instance that you can do your testing on, but personally the amount of simple bugs that I am forced to find because the developers here are too lazy to actually do proper clean installs for testing is beyond a joke.
If it is not correctly installed, the redirection that has been employed is way off. The following is the culprit.
// Asset root assetRoot = "../contentbox-admin";// Create or Use
if( action eq “process” ){
// Process or create?
if( dsnCreated ){
// Update datasource
request.cfHelper.updateAPP( dsnName );
// Relocate to installer now
location( url="…/…/index.cfm", addToken=“false”);
}
// Create new DSN
else{
results = request.cfHelper.createDSN(cfmlPassword=cfpassword,
dsnName=dsnCreateName,
dbType=dbType,
dbHost=dbServer,
dbName=dbName,
dbUsername=dbUsername,
dbPassword=dbPassword);
// Check for errors?
if( !results.error ){
// Update APP DSN Now!
request.cfHelper.updateAPP( dsnCreateName );
// Relocate to installer now
location( url="…/…/index.cfm?cbInstaller=true", addToken=“false” );
}
else{
// Mark Errors
errors = results.messages;
}
}
}
