warn about incompatible extensions when downgrading


given all these problems users have been experiencing, there needs to be a better solution

there is a minversion in the build.properties file

It doesn’t seem this ever gets checked / enforced / warned?

i.e under the server admin

  • on the update page, when an older version is selected to downgrade to, check the installed extensions and warn about any potential incompatible installed extensions

  • on the applications page (i.e. extensions) show a INCOMPATIBLE banner, like the UPDATE ME (obviously that is only going to be useful once it’s implemented, i.e. older Lucee versions will still have the problem)





Michael Offner
May 16, 2019, 2:37 PM

the admin warning could be a nice addition, but have in mind that you can downgrade Lucee also for example by copy the .lar to /deploy .

Michael Offner
May 16, 2019, 8:44 PM

added a fix https://github.com/lucee/Lucee/commit/85e27a066593c1bccdbf05c2a75de3f575bfc725

of course this fix only works from the version onwards, so downgrade to an older version will still fail.

when you will downgrade to any version that is or bigger, Lucee will check if all extension are still valid for that core version.

If not that invalid extension get uninstalled, but then it check if that extension is defined as required extension with a different version with that core, if so that extension version then get installed.

So let say we will add 2 new extensions to Lucee 6:

  • “Susi 1.0” that needs at least Lucee

  • “MSSQL 10.0“ that needs at least Lucee

when you know downgrade from Lucee 6 to Lucee, lucee checks the minimal version of of all extension installed.

It will detect the 2 above and uninstall them, but it will also detect that MSSQL is a required extension in version 4.0.2206.100 and install that version.




Michael Offner
May 16, 2019, 8:45 PM

this will need some more testing before we can set to deployed.



Michael Offner


Zac Spitzer




Fix versions