.cfconfig fails to import custom-tag and component mappings

Description

None

Environment

None

Activity

Pothys - MitrahSoft 
16 November 2022 at 11:38

I've checked this ticket with lucee fixed version 5.3.10.94-snapshot. Now importing config from .CFConfig.json using configImport() works fine and no error occurs.

Pothys - MitrahSoft 
16 November 2022 at 06:49

Michael Offner 
15 November 2022 at 17:55

Actually the current implementation is not make to work for every possible setting, it only works for a limited set with very specific syntax. But i did improve the code so it can handle the input better. Also i did make sure, that in case an input cannot be read, it will not stop the execution of the rest. so please give it another try

Michael Offner 
15 November 2022 at 17:52

Pothys - MitrahSoft 
15 November 2022 at 08:32
(edited)

I've checked this ticket with lucee fixed version 5.3.10.93-SNAPSHOT. I create mapping, component mappings, and customTag mappings in lucee 6 admin. Then import the config from .CFConfig.json using the configImport function didn't import the mappings, component mappings, customTag mappings and It throws an error like Can't cast String [path:{lucee-config}/logs/datasource.log] to a value of type [Struct].

So I removed the logging configuration in the config.json file and tried it again, it correctly imports the mapping, component mapping, and custom tag mapping and It throws the error file or directory [] does not exist.

Stacktrace:

I think, if there is an error in any configuration, it simply throws an error and ignores the other configuration.

Fixed

Details

Assignee

Reporter

Priority

Fix versions

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

Affects versions

Created 7 October 2022 at 12:23
Updated 16 November 2022 at 17:22
Resolved 16 November 2022 at 17:22