Extensions, cfconfig and restarting?

dev support
1

I saw this in the latest 6.2.3.35 Stable changelog:

“extension defined in cfconfig need a restart to work”
https://luceeserver.atlassian.net/browse/LDEV-5798

But testing this I don’t see that behavior.

To work around this in earlier versions I’ve been adding “checkForChanges”: true to my cfconfig which seems to correctly install, and uninstall extensions according to my cfconfig.

I just updated my container to use 6.2.3.35, rebuilt and when looking in the admin I still see MySQL 9.3.0 despite having 9.4.0 in my config. Also the MSSQL and other extensions I don’t want are still installed. This occurs with checkForChanges true and false.

image
image1325×670 122 KB

If I roll back to 6.2.2.91 (with checkForChange=true) the behavior is correct

image
image1286×732 138 KB

Sample of my cfconfig showing versions:

  "extensions": [
    {
      "id": "7E673D15-D87C-41A6-8B5F1956528C605F",
      "name": "MySQL JDBC Driver",
      "version": "9.4.0"
    },
    {
      "id": "CED6227E-0F49-6367-A68D21AACA6B07E8",
      "name": "Lucee Administrator",
      "version": "1.0.0.6"
    },
    {
      "id": "D46D49C3-EB85-8D97-30BEC2F38561E985",
      "name": "Lucee Documentation",
      "version": "1.0.0.5"
    },
...
1 Like
2

I’d like to thank @Jim_Priest for identifying this issue. It appears that the problem is still not fully resolved.

The MySQL JDBC Driver was imported successfully and is displaying correctly in the Administrator.
However, some other extensions — such as the Chart extension — are still not updating or functioning as expected.

I’ve reopened the ticket for further investigation.

3 Likes