Inspiring

Open for Voting

ReReplace broke after Update 26

27 replies
731 views
Translate

We are using Coldfusion 2023 Update 26 on Windows Server 22. Yesterday we applied the Update 26 and ended up with bad data in the database, because of “reReplace” no longer working like it used to.

We have a function that attempts to capitalize the first character of a string in case the user does not “case” properly. At the heart of the function is something like this: rereplace(lcase("test"), '^\w|\s\w', '\U\0','ALL')

At update 25, this call would return “Test”, but after applying update 26, it’s returning “UTest”. Because of this, we had lots of data go into our database with letter U prepended. This will be a major pain to fix. I am sure there are other ways to uppercase first letter of a string, but at this point, I haven’t had a chance to look into it. Just thought I’d post this here so other users are aware.

I have filed a bug report with Adobe. Please upvote so this will get noticed and fixed.
https://tracker.adobe.com/#/view/CF-4234761

S

Scott374374019lcz

Participant

Just a random thought: In previous updates formatting swithes for dates became case sensitive. Is it a case of an ironic case sensitive switch switch , e.g. \U to \u causing the issue?

:)

Scott

Translate

DevScreenAuthor

Inspiring

For those looking for an immediate solution, please visit the bug tracker at https://tracker.adobe.com/#/view/CF-4234761 . There is a patch posted which fixes my above particular situation (See comments in bug tracker for additional concerns)

On the right side of the bug tracker, you will see “Attachments” listing 2 jar files. One starting with hf2025 and other starting with hf2023 (which apply to CF2025 and CF2023 respectively). The instructions to install were given by Adobe as:

Copy it to: <Instance_Home>/lib/updates (eg: cfusion/lib/updates).
Stop the instance
Delete the contents of cfusion/bin/felix-cache
Start the instance
Test the behaviour

Someone from Adobe mentioned to me that they will make this fix part of one of their future update. Hope this helps!

Translate

DevScreenAuthor

Inspiring

@Eric318650369eow, @martinc59163932: See my comment above for a jar file patch.

Translate

DevScreenAuthor

Inspiring

@Charlie Arehart: Is there a way for you to make my comment above an “Accepted Answer” so people can quickly find the solution? Thanks!

Translate

E

Eric318650369eow

Participating Frequently

When there will be a new update with the patch ? This update 26 cause major issue with Regex
Does this page will be updated ?
https://guides.adobe.com/coldfusion/en/docs/install-and-configure-coldfusion/coldfusion-2023-release-update-26.html

Translate

M

martinc59163932

Participant

This is also a bug for us - please can we have some clarity on how to reverse this behavior - this is a serious issue, causing errors and unexpected behavior across our production environment

Translate

E

Eric318650369eow

Participating Frequently

Is there anything on this regex issues. We have also issues with Regex and multiline with Colfusion 2023 update 26 ?
It cannot go on production.

Translate

DevScreenAuthor

Inspiring

They posted a couple jar files on the bug report. That seems to have fixed this particular issue. I am not sure what the multiline issue is but if you give me a one-line regex statement, I can run it and tell you what the output was on my server that has this jar file installed.

If you need instructions to install the jar file, scroll down on the bug report close to the bottom for my comment which tells you what to do.https://tracker.adobe.com/#/view/CF-4234761

Translate

E

Eric318650369eow

Participating Frequently

for example it broke with this REMatchNoCase

REMatchNoCase('\{\{(.*?)\}\}',ARGUMENTS.stringToParse)

and to make it work with the update 26 with no additional JAR patch, I had to write

REMatchNoCase('(?s)\{\{(.*?)\}\}',ARGUMENTS.stringToParse)

Same with ReReplace

Try with a multiline content.

Translate

jeffh65754959

Inspiring

There are two jar files (2025 and 2023) attached to CF-4234761 this morning. Unfortunately, no instruction what should be with them, yet. The same files are attached to CF-4234762.

Translate

DevScreenAuthor

Inspiring

That’s a bummer there are no instructions. I have also raised this issue by creating a ticket at Adobe. I got an email Saturday that the issue has been raised with Engineering team. I was hoping they may send me a jar file with instructions but not yet.

Translate

D

Dmitriy34908511m2zg

Participant

I can confirm this is an issue for us as well.

Translate

jeffh65754959

Inspiring

I was able to recreate this issue on CF 2023 HF 26. When I rolled back to HF 25, it worked as expected.

Translate

DevScreenAuthor

Inspiring

Thanks for confirming it. Based on another bug report I saw on tracker.adobe.com, it seems that CF maybe ignoring backslashes from the 3rd argument. I hope they fix it soon.

Translate

jeffh65754959

Inspiring

I looked this up in ChatGPT and it mentioned the bug tracker submission but recommended this format.
reReplace(lcase(“test”),"^(\w)|\s(\w)","\U\1\2\E","ALL");

I have re-applied HF 26 and the results with their recommendation are worse.

Translate

DevScreenAuthor

Inspiring

Someone else reported a similar bug:

https://tracker.adobe.com/#/view/CF-4234762

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.