http://coldfusion.com logo
Join Slack
Powered by
Testing our code for compatibility with ACF 2025, ...
# adobe
n
Testing our code for compatibility with ACF 2025, and ran into an issue I can't seem to find any info about. We have a virtual directory at the root of a drive, mapped to a document library on another server. ACF 2021 recognizes the virtual directory path as a directory, and directoryExists() comes back TRUE for it. ACF 2025 is seeing it as a file (I assume looking at the symlink) and directoryExists() comes back FALSE for it and any subfolders. This seems to be an undocumented change in behavior. Does anyone have a fix or a workaround?
j
Something to try, I am not using ACF but does it work if you also specify it as a mapping under the ACF administrator?
n
Thanks for the idea, @jfrobishow. Unfortunately, no, you can't make a mapping like that
b
Have you changed your web server setup
Lucee doesn't recognize virtual directories in IIS because they aren't passed back to the servlet (well they are if you use BonCode, but they aren't used by Lucee)
Adobe always handled this with their "magic" connector and passed that information back to CF, which uses it to expand paths
👍 1
If you're using another web server, perhaps it doesn't support that.
Or, maybe CF removed or broke that feature?
n
Probably should clarify that this is a virtual directory in Windows, not IIS
b
Ahh, those aren't called virtual directories 🙂
I assume you mean a symlinked folder?
n
But I did my comparison between 2021 and 2025 on the same server and copy of IIS
Sure 😄 I thought symlink was more a Linux term. But in any case, Yes
b
Well, if you are talking about symlinks, then forget everything I said, because symlinks have nothing to do with your web server
👍 1
"symlink" is a linuxy term, but Windows I think just calls them "link"?
I assume you're talking about the things you use the 
MLINK /D
command to create
👍 1
linked dirs can be a pain to handle in Java. I'd file a ticket with a reproducible example. They prolly changed some code to a version that doesn't follow links
n
Yeah.... Just hoping I wasn't the first one to run into this. Thanks for the input!
b
Symlinks aren't super common in deployments and 2025 is still somewhat new
n
Oh trust me, this is a system I inherited, not one I chose the setup for!
simple smile 1
😄 1
Gonna have to create a ticket, but just in case anyone has any more ideas, I did some playing and learned a little more: the issue seems to only be with symlinks to folders on the network. Symlinks to folders on the same local machine (same drive letter or different) show up as directories in CF.
b
On linux there are different types of links. You could check and see if Windows has the same and if it affects the behavior
n
From what I've read, Windows does have soft and hard symlinks, but it will only create only soft ones for non-local targets
m
Definitely please put in a ticket. @priyank_adobe for visibility
👍 3
2 Views
Open in Slack
PreviousNext
Powered by