Issues
- when a file in the deploy folder isn't supported, log and move to the failed to deploy folderLDEV-5374Resolved issue: LDEV-5374Pothys - MitrahSoft
- invalid LUCEE_EXTENSIONS should be fatal on startupLDEV-5272
- Scheduled tasks aren't loaded from CFconfig.json via deploy folder until restartLDEV-5169Resolved issue: LDEV-5169Pothys - MitrahSoft
- importing an empty CFConfig property should create an empty property structLDEV-5044Resolved issue: LDEV-5044Zac Spitzer
- when an extension can't be downloaded, log out the invalid urlLDEV-4986Resolved issue: LDEV-4986Zac Spitzer
- CFConfig: Engine is not initialized, you must first call getInstance(ServletConfig)LDEV-4985Resolved issue: LDEV-4985Michael Offner
- .CFConfig.json should be a pleasure to work withLDEV-4984Michael Offner
- add placeholder {lucee-config-file} for .CFConfig.json file pathLDEV-4982Resolved issue: LDEV-4982Zac Spitzer
- .CFConfig.json missingLDEV-4945Resolved issue: LDEV-4945Michael Offner
- in single mode, configImport(type=web) doesn't work, doesn't throwLDEV-4928Resolved issue: LDEV-4928Zac Spitzer
- regression .CFConfig.json datasources which work with 5.4 don't work with 6LDEV-4927Resolved issue: LDEV-4927
- invalid lucee.base.config paths / files should be fatal on startupLDEV-4894Resolved issue: LDEV-4894Zac Spitzer
- NPE with a .cfconfig.json datasources without class or dsn using configImport, singleMode type="web" doesn't workLDEV-4889Resolved issue: LDEV-4889Zac Spitzer
- extension without id get ignoredLDEV-4882Resolved issue: LDEV-4882Michael Offner
- Wrong webroot being used with script-runner / JSR-223 / cliLDEV-4881Resolved issue: LDEV-4881Michael Offner
- add configImport and configTranslate to Lucee 6LDEV-4504Resolved issue: LDEV-4504Michael Offner
- configImport needs to understand datasource allowedselect etcLDEV-4485Resolved issue: LDEV-4485Zac Spitzer
- configImport isn't importing custom args for datasourcesLDEV-4255Resolved issue: LDEV-4255Michael Offner
- .cfconfig fails to import custom-tag and component mappingsLDEV-4221Resolved issue: LDEV-4221Michael Offner
- NPE getBaseComponentPage, CFconfig lucee.additional.config=trueLDEV-4189Resolved issue: LDEV-4189Pothys - MitrahSoft
- add support for .cfconfig.json importing on startupLDEV-4168Resolved issue: LDEV-4168Michael Offner
- log out any unsupported options after importing a CFconfig fileLDEV-4148Resolved issue: LDEV-4148
- add function ConfigImportLDEV-3790Resolved issue: LDEV-3790Michael Offner
23 of 23
when a file in the deploy folder isn't supported, log and move to the failed to deploy folder
Fixed
Description
relates to
Details
Assignee
Pothys - MitrahSoftPothys - MitrahSoftReporter
Zac SpitzerZac SpitzerLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
Priority
New
Details
Details
Assignee
Pothys - MitrahSoft
Pothys - MitrahSoft
Reporter
Zac Spitzer
Zac SpitzerLabels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
Priority
NewCreated 5 March 2025 at 12:54
Updated 28 March 2025 at 10:11
Resolved 6 March 2025 at 10:29
Activity
Show:
Pothys - MitrahSoft28 March 2025 at 10:11
I have tested this with Lucee version 7.0.0.157-SNAPSHOT. It creates a error log for the unsupported file in the deploy folder, and it works fine.
Zac Spitzer14 March 2025 at 16:01
I manually ported this to 7.0 can you check it again plz?
Zac Spitzer14 March 2025 at 16:00
Pothys - MitrahSoft6 March 2025 at 10:28
I have tested this ticket with Lucee version 6.2.1.48-SNAPSHOT. When I tried to add the unsupported file to the deploy folder, it automatically moved the unsupported file to the failed_to_deploy folder and created error logs in the deploy.log file. It works fine now.
Zac Spitzer5 March 2025 at 14:11
and
in addition, any unsupported files are also moved to the failed-to-deploy folder
previously, Lucee would simply just process known files, skipping unknown ones
move any unsupported files to the
failed_to_deployfolder and log it outlog out when importing a
.CFconfig.jsonorconfig.jsonfrom the deploy folder