Legacy CFForm-CFSelect Errors Arose

dev
1

I’m hesitant to delve into this because I’m not sure I found a true solution versus an accidental work-around, and because this is for legacy code that really should be eradicated but we have too many instances of it right now.

I recently updated my Lucee extensions of Lucee Form Tags from 1.0.0.9 to 1.0.0.10 and S3 Resource Extension from 2.0.1.25 to 2.0.2.21 on the Production server as we’ve been using those versions in test and staging without an issue for months.

Almost immediately I was getting reports of errors stating that the CFSELECT command needed to be nested inside of a CFFORM command.

Checking the code, I see that they were all, indeed, nested properly.

I reverted Productions Lucee Form Tags to 1.0.0.9 and the first area that had been a problem was no longer erroring. After contacting the customer, she reported that, indeed, that problem went away, but it still existing on other similar areas.

I returned Form Tags to 1.0.0.10 and the original problem returned. Next, I reverted S3 Resource back to 2.0.1.25 and some areas now worked while others errored.

I upgraded S3 to 2.0.2.19 and again, some areas worked while others that were working now failed. I then brought Form Tags back to 1.0.0.9 and got more of the “some worked that didn’t, some did not that did” issue. Same-same when I reverted S3 to 2.0.1.25 while leaving form tags at 1.0.0.9.

So now I’m stuck as to why this is happening, since the versions are all back to where I was before this all started to blow up, but some areas that were not a problem before are now erroring on me.

Even harder, I’m not sure what more anyone here can do to test this. Have a CFSELECT inside of a CFFORM in Lucee 6.1.0.243 with Java 11.0.22 64 bit.

I’m open to suggestions on how to further debug this problem!

2

Are the production servers using inspect=never, could be a template caching issue ?

Did you try a restart after changing the extensions? Alas, that’s often quite helpful

3

I am not familiar with “inspect=never”. Where do I find that?
Searching tells me: Server/Web Administrator: Settings → Performance/Caching

I have Inspect Templates set to Auto (Optimized performance).

As for a restart of the server, I will be doing that tonight after normal hours in order to not interrupt customers.

4

Do you have any of the error stacktraces?

the change in the form extension between 1.0.0.9 and 10.0.0.10 was a very minor one liner

https://luceeserver.atlassian.net/browse/LDEV-2370

1 Like
5

Restarting server now. We shall see if that was all it was.

6

I just ran through three of the scenarios that were causing us errors, and all were successful. I will have the end customer test tomorrow, but so far it looks like the restart of the server fixed it.

Thanks for the suggestion to do that!