Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

The function [keyExists] does not exist in the String

Description

Trying to import config settings into a bleeding edge Lucee server

Result:

❯ cfconfig import D:\Temp\serverconfig.json

ERROR (6.1.0+00813)

The function [keyExists] does not exist in the String.

\modules\commandbox-cfconfig\modules\cfconfig-services\models\providers\Lucee6Server.cfc: line 282
280:          for( var datasourceName in configData.datasources ) {
281:             var datasource = configData.datasources[ datasourceName ];
282:             if( datasource.keyExists( 'password' ) ) {
283:                datasource[ 'password' ] = 'encrypted:' & passwordManager.encryptDataSource( datasource.password );
284:             }
called from \modules\commandbox-cfconfig\modules\cfconfig-services\models\CFConfigService.cfc: line 301
called from \modules\commandbox-cfconfig\commands\cfconfig\import.cfc: line 147
called from \system\services\CommandService.cfc: line 443
called from \system\services\CommandService.cfc: line 225
called from \system\Shell.cfc: line 865
called from \system\Shell.cfc: line 680
called from \system\Bootstrap.cfm: line 165

To enable full stack trace, run config set verboseErrors=true

Attachments

1

Activity

Show:

Brad WoodFebruary 25, 2025 at 6:32 PM

Actually, comparing line numbers-- the code I posted above is in the portion that reads the config from Lucee itself. The error, however happened when writing config to the server. The “psq” key is expected in Lucee’s bastardized version of CFConfig that it writes into its server home, but not in CFConfig’s actual JSON format. It would appear what happened is you took a JSON config file from inside a Lucee Server Home and tried to use it directly for CFConfig. Unfortunately, since Lucee stuck so loosely to the CFCOnfig format, you can’t do this You must always “export” Lucee’s config via the CFConfig tool to get a proper CFConfig formatted JSON file. Clean up on his extra keys such as psq are a prime example of the cleanup and massaging I have to do on the Lucee version of the JSON.

Brad WoodFebruary 25, 2025 at 6:25 PM

No, his config is valid. For some crazy silly reason, Lucee started storing random datasource-related stuff inside the datasource struct. This should have been fixed 7 months ago however, according to my Git commit history. Can you verify if you are on an older version of CFConfig perhaps.

Jon ClausenFebruary 25, 2025 at 4:43 PM

Excellent. Glad you were able to get it working again!

Harry KleinFebruary 25, 2025 at 4:28 PM

Works now, thanks!

Harry KleinFebruary 25, 2025 at 4:22 PM
Edited

Strange, this is the result of cfconfig export and worked fine before.
But thanks, I remove this line and hope that it works now

Cannot Reproduce
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Priority

Sentry

Created February 25, 2025 at 1:37 PM
Updated February 25, 2025 at 6:32 PM
Resolved February 25, 2025 at 4:43 PM