As a reminder, if you upload CFML documents that are encrypted, be sure to use binary mode. I spent about an hour trying to figure out why a template was showing it's source instead of running. Turns out my FTP client was uploading all CFMs in ASCII and this was corrupting the encrypted documents.
(This post is more than 2 years old.)
Uploading Encrypted Documents
Hire Me!
I'm currently looking for my next role in developer evangelism and advocacy. I have a long history of helping companies work with developers and love to write, create demos, and present at conferences. You can find my resume to learn more and drop me an email (raymondcamden@gmail.com) to reach out.
Support this Content!
If you like this content, please consider supporting me. You can become a Patron, visit my Amazon wishlist, or buy me a coffee! Any support helps!
Want to get a copy of every new post? Use the form below to sign up for my newsletter.
Archived Comments
Yep, our customers run into this one a lot with our tags.
Why use ASCII in first place? I usually live under Win2k on the client/development side, but most servers are Solaris. I try to keep all text-files in Unix format, and I set my ftp clients to always use binary.
I recently reinstalled my ftp client and it was set to the default.
Yikes. I always hate (and love) those silly small errors. It's always such a pisser to fight with something for a long time only to realize you're saving the wrong file or something. Of course, it's also quite a nice feeling when you realized it was just a dumb error on your part and your code actually was solid!