Looking at the docs here: https://docs.lucee.org/guides/cookbooks/application-context-basic.html#onrequeststart, the method signature for

onRequestStart

is:

boolean function onRequestStart(string targetPage)

Should that not be

required string targetPage

? That's the signature for ColdFusion, and is there any circumstance under which that value is not passed in, so therefore the implementation has to consider it optional? As far as I can determine, a value for the

targetPage

parameter is always passed..?

If I request

/index.cfm

, and somewhere in the bowels of the app code I have

writeDump(callStackGet())

, should it not be my expectation that the resultant output will always start with

index.cfm

? What I'm seeing is a single entry in the dump that is the file I have the dump in. Nothing else. There were quite a number of files / methods / etc being called between

index.cfm

and where I'm doing the dump.

the windows installer now supports side by side installs, now that you can specify a custom service name https://luceeserver.atlassian.net/browse/LDEV-4468

https://trycf.com/gist/56e3cc737649a446bc5a05f7b2aa3e79/lucee5?theme=monokai Note the error message "null can not be casted to a Struct" There's a coupla grammar issues there. "cast" is the past tense of "cast": "casted" isn't a thing. Secondly: if one was in there to fix it, consider also tweaking "cannot" to be "can not". Whilst both are correct; one would tend to use "can not" to emphasise the "not" part when appropriate, and is perhaps not the better of the two options here. "cannot" is by far the more common spelling of this.

what side effects should i be aware of if i were to consider moving from the regular lucee docker image to the light version?

-light

(optional) is a build with the Lucee "Light" JAR file, WITHOUT any extensions (users must install extensions separately, this includes database drivers, ORM, ESAPI, S3, image handling, etc)

i'm experimenting with the light version of the docker image. i don't have the administrator extension installed, yet, i can access the administrator web interface. is that normal?

the 5.3 build is blowing up on github actions, wonder if it's related to this? 5.4 and 6.0 aren't but they use the s3 ext v2.0 https://aws.amazon.com/blogs/aws/heads-up-amazon-s3-security-changes-are-coming-in-april-of-2023/

updated mysql (8.0.33) and postgres (42.6.0) extensions are available (older versions had CVEs)

Question re the docs here https://docs.lucee.org/guides/Various/FAQs/technical-FAQs/database-session.html#tip-manually-check-cf_session_data-table-for (about the

cf_session_data

table...

sql qqq -->

I am having an issue with the MongoDb extension for Lucee (not the Ortus one). I install it and try to use it to create a MongoDb cache and I get the following error: cannot load class through its string name, because no definition for the class with the specified name [org.lucee.mongodb.cache.MongoDBCache] could be found caused by (java.lang.ClassNotFoundException:org.lucee.mongodb.cache.MongoDBCache not found by lucee.core [49];java.lang.ClassNotFoundException:org.lucee.mongodb.cache.MongoDBCache;) How could it possibly not be able to find the class specified since it's in the extension that was installed? My installation is running Lucee 5.3.10.120 under CommandBox 5.9 (but this was happening using CommandBox 5.8 as well). To throw a wrench into this, we have a version of Lucee running in a static web app on Azure that works perfectly! We install the MongoDb extension up there and I am able to create a cache using that MongoDb driver just fine, no errors what so ever. That installation is using a slightly different build of Lucee but still 5.3.10.x but I downgraded my local Lucee to the same version and it still failed locally. Does anyone have any ideas why this is happening?

Hi, has anyone been able to run a Lucee Dev enviroment using github codespaces and know how to set it up?

@Jack can you try this one: https://www.ortussolutions.com/products/commandbox

next release of my performance analyzer has a thread type filter (java,cfml.all), thanks for the suggestion @domwatson https://github.com/zspitzer/lucee-performance-analyzer/issues/12

If you’ve ever used dump() abort; to debug.. you should install https://github.com/softwareCobbler/luceedebug A colleague spent 4 hours debugging an issue to no avail, and was then resolved in 20 mins after using the step debugger.. Next level awesome!

anyone having s3 problems with ACLs on objects, several lucee tests have started to fail recently more info here https://luceeserver.atlassian.net/browse/LDEV-4474

Who here has tested their applications on Lucee 6 ?? as we count down to release would be great to get a sense of overall feedback

I am developing a custom app on lucee 6. There are no major issues that I have found so far.

We’re testing our services on L6 too, nothing major currently

been playing with ULIDs vs UUIDs https://luceeserver.atlassian.net/browse/LDEV-4481?focusedCommentId=53652 performance wise nothing amazing with a 10000 row test set, but the table size is 0.5mb vs 1.5mb!

OMG

Probable Lucee6 bug...

Another probably Lucee6 bug http://localhost:8860/lucee/admin/server.cfm?action=server.compiler (which one gets to via Language/Compiler in server admin

Message	key [externalizeString_1] doesn't exist
Stacktrace	The Error Occurred in
/admin/server.compiler.cfm: line 160
called from /admin/web.cfm: line 508
called from /admin/server.cfm: line 7

Also: why's it calling stuff relating to web admin from server admin? odd.

Default option now for lucee 6 is single context

No web and server

Just a single one

Much better for dockerised deployment

Potential grammar improvement in Lucee Admin:

Lucee compiler settings, this affects how the Lucee Compiler parses the source code. Changing this settings flushes all existing class files and triggers a recompilation.

That's not great English. Recommend:

Lucee compiler settings. This affects how the Lucee Compiler parses the source code. Changing these settings flushes all existing class files and triggers a recompilation.

You can set to old behaviour though if you want admin

And multi context