Last week, I attempted to update my dev machine from 6.2.4.24 to 6.2.5.48, and I ran into a few issues.
The first was that the content of the file “[lucee]\tomcat\lucee-server\context\context\graph.cfm” had been replaced with the content from either “.\formtag-form.cfm” or “.\form.cfm” (they only differ by comments and slight differences in “prv.validateEmail”). I replaced graph.cfm from a backup, and it seemed to work fine.
The second was that, on booting up the next day, my "[lucee]\tomcat\lucee-server\context" folder and, therefore, my entire lucee config had been completely wiped. I wrestled with it for a while to reinstate the configuration and re-update to 6.2.5.48 (it kept dropping back to the bundled version). I eventually found the core issue, which appeared to be the updating of cfspreadsheet from 3.0.3 to 3.0.4. After downgrading that back to 3.0.3, everything else was stable. Initial testing of cfspreadsheet right after the 3.0.4 upgrade seemed to run fine.
There were some other extensions that didn’t work (image extension 3.0.1.0 and Lucee Form Tags 2.0.0.6), but they didn’t cause the same config wipe when restarting Lucee. They just gave a ‘jakarta.servlet.http.HttpServletRequest lucee.runtime.PageContext.getHttpServletRequest()’ error. Other full-version number updates seem to work fine (PDF Extension for Jakarta EE Lucee 7+ 1.2.0.12->2.0.1.0 and OWASP 2.6.0.1->3.0.0.14). I’ve only briefly touched upon the jakarta vs javax switchover that’s taking place, so I don’t know if these issues are due to misconfigured extensions or if I would need to update something in my own setup to get them to work.
Any clarification on extension compatibility with Lucee 6 would be appreciated.
The Image and Form extensions are working great! Thanks!
I’m still having the same context wipe issue with the 3.0.5 cfspreadsheet extension. I don’t know if it matters, but I run Single Mode with only “local” file access. Prior to restart, when testing it I had to add [lucee]\tomcat\lucee-server\context\components\org\cfpoi\spreadsheet to the custom directories before it would work. (Side note: the custom directory “[lucee]\tomcat\lucee-server\context\temp” is always appended to the list when Security > Access is updated, even if it’s already in the list.)
I think I will end up just refactoring to simplicity spreadsheet as we really only have one process left relying on this extension, but is there a log file or anything I can send to help?
