Howdy... We updated Lucee 6.2.0.321 to the 2.0.2.21 S3 extension last night, and now every attempt to "browse server" from Mura 7.1.476 throws this error in the CKEditor "Browse Server" modal:

org/lucee/extension/resource/s3/info/NotExisting

do you have the full stack trace? can you describe your install / stack / update history?

from the log

The stacktrace will always (99%) tell you what template causes the exception

Thanks @zackster - I see that at least 15 templates are mentioned in my StackTrace.txt above. Is the root cause typically in the first (lowest) or last (highest) mentioned template?

You read the stacktrace from the top down. I realise you're trying to debug an extension error - so this isn't an exact match for THIS scenario - but for illustrative purposes of visually reading an error stacktrace... What I do is : Read from the top down and look for the first (and second if it exists) mention of a CFM or CFC - that I notice is "mine". Afterall, it is ALWAYS MY code code that is the issue!!! In that: I am doing this troubleshooting because it WAS working then I made some changes - and now it is not. QED "MY" code change broke something. Granted a bug could exist in the Lucee code or an external library / framework / extension - but the most likely culprit is MY code... Anyway - the CFM/CFC code listed from the top/down - will help you out. Be aware that the line number mentioned along with the stacktrace, on occasion - can be a few lines off... That is: I have certainly had a stacktrace say the exception occurred in FRED.cfc at line 100 - but line 100 is either whitespace or a comment... so the offending code might be a couple of lines "off" - but 99.9% of the time - the line number, in the stacktrace is correct. Oh - and the reason I look for the first couple of CFM/CFC entries in the stacktrace - is because the first one might be erroring because the one before it is sending the first, the wrong TYPE of data, or an unexpected value... Eg I sent it a value of "A" and the code mentioned in the first encountered CFM?CFC only allows for "B" or "C" and I have been lazy / overlooked the need to check for other / unexpected values - and so fixing the value used by the second - or fixing the code in the second - can sometimes get the first mentioned CFM/CFC to work correctly - and thus resolve the issue at hand.

Thanks! I have noticed that once I can find where the "real" error is, some of the subsequent items in the trace are often reacting to an invalid type. After all, they are getting an [error] and not a [integer] or [query], etc... that they're expecting.

Yeah restarts often help! What was the older version you're upgrading from?

2.0.1.25