Coldbox/ContentBox Setup Error
Description
Attachments
- 03 Dec 2020, 11:57 PM
- 03 Dec 2020, 11:57 PM
- 03 Dec 2020, 11:57 PM
- 03 Dec 2020, 12:18 AM
- 03 Dec 2020, 12:18 AM
- 03 Dec 2020, 12:18 AM
- 02 Dec 2020, 06:28 PM
- 02 Dec 2020, 06:28 PM
- 02 Dec 2020, 06:28 PM
- 02 Dec 2020, 02:43 PM
- 02 Dec 2020, 02:43 PM
- 02 Dec 2020, 02:43 PM
Activity
Michael EdwardsDecember 5, 2020 at 5:08 PMEdited
Luis, we want this to use Lucee, not ColdFusion. We have a very old version of cold fusion current, CF9. We want to migrate away from CF. I submitted payment, next steps?
Luis MajanoDecember 4, 2020 at 2:56 PM
@Michael Edwards I have to point out that Adobe 2021 has major issues still with running our BOX products. Therefore, having ACF2021 on production is not recommended as it won’t run any of our products yet. So either you use Lucee 5 latest, or Adobe 2018 or 2016.
Michael EdwardsDecember 3, 2020 at 11:57 PM
Luis,
Does the command box setup of Lucee install Lucee as it normally would If I downloaded Lucee and installed natively? The reason I am asking is because I see it installs in the windows user.administrator folder with each website as it’s own instance. Should I just go through the Lucee setup separately and then install content box/command box? Or, is the issue I am having still does not matter if it was running through coldfusion or lucee?
Michael EdwardsDecember 3, 2020 at 12:18 AMEdited
The server.json file already had that syntax in there.
The IIS rewrite rules were added during the installation process when it asks you if you want to install them.
The rules are now there when I look in the IIS rewrite module.
Do i need to do the following still? server start --rewritesEnable
Update: i did server start --rewritesEnable, same issue exists.
After much reading, i was not aware that lucee is a full alternative to CF. Given such, obviously i want to migrate to it, but for this website specifically how do i get it to point to the lucee server? Like you said, it appears that it is being run through Coldfusion instead of Lucee?
Luis MajanoDecember 2, 2020 at 3:36 PM
Ok, few pointers.
If you are using JUST CommandBox as both your CFML and Web Server. Then you won’t need any rewrite rules, since CommandBox supports that. Just make sure in your server.json you have something like this:
{
"web" : { "rewrites" : { "enable" : true } }
}
Now, if you are using CommandBox as ONLY your CFML engine and have IIS/Apache/Nginx in front as a web server, then the web server needs to do the rewrites. Here are some examples:
https://coldbox.ortusbooks.com/the-basics/routing/requirements/rewrite-rules
https://coldbox.ortusbooks.com/the-basics/routing/requirements
The full rewrite capability is done by the web server, either nginx/apache/iis or commandbox.
I am in the process of setting up contentbox and after i created the DSN, i am getting the following error when continuing the setup process. I am using MicrosoftSQLServer and updated the application.cfc accordingly. I see in the lucee admin the datasource, both in web and server. I do not see it in my coldfusion administrator. I am guessing these are separate and unique? Eitherway, unable to complete the setup process.
Lucee 5.3.7.47 Error (Builder.BuildCFCDependencyException)
Message Error building: SettingService@cb -> could not execute query
.
Detail DSL: , Path: contentbox.models.system.SettingService,
Error Location:
C:\websites\CommandBox\mytestsite\modules\contentbox\modules\contentbox-deps\modules\cborm\models\CriteriaBuilder.cfc:254
C:\websites\CommandBox\mytestsite\modules\contentbox\models\system\SettingService.cfc:693
C:\websites\CommandBox\mytestsite\modules\contentbox\models\system\SettingService.cfc:247
Stacktrace The Error Occurred in
C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Builder.cfc: line 180
178: detail = "DSL: #thisMap.getDSL()#, Path: #thisMap.getPath()#,
179: Error Location:
180: #reducedTagContext#"
181: );
182: }
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Injector.cfc: line 402
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\scopes\Singleton.cfc: line 70
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Injector.cfc: line 370
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Builder.cfc: line 614
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Builder.cfc: line 436
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Injector.cfc: line 897
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Injector.cfc: line 653
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\scopes\Singleton.cfc: line 78
called from C:\websites\CommandBox\mytestsite\coldbox\system\ioc\Injector.cfc: line 370
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\InterceptorService.cfc: line 350
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\InterceptorService.cfc: line 341
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\InterceptorService.cfc: line 275
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\ModuleService.cfc: line 573
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\ModuleService.cfc: line 574
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\ModuleService.cfc: line 441
called from C:\websites\CommandBox\mytestsite\coldbox\system\web\services\LoaderService.cfc: line 59
called from C:\websites\CommandBox\mytestsite\coldbox\system\Bootstrap.cfc: line 98
called from C:\websites\CommandBox\mytestsite\Application.cfc: line 85