Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the '10.5: Remove the 'downloaded file' warning flag' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Remove the 'downloaded file' warning flag
Authored by: crisses on Dec 25, '07 12:42:39PM

Hi, David,

I beg to differ. Ok, perhaps .php is a potential executable but not when I'm trying to open it in a text editor. Example: I download ZenCart, expand it, look at some of the .php files in SubEthaEdit, and this warning comes up. For every .php I'm opening in a text editor. I could run them in Apache localhost (only because I've gone through the trouble to enable a MAMP stack on localhost), and I'll bet they execute without warning. How helpful (or secure) is that?

I'm going to find the disabling of this feature a definite time-saver. Most of my work is in web application programming, and I'm not new to the internet (obviously) -- I'm aware that things that come via the web are potentially dangerous. I need to disable this feature in order to work quickly, sanely, and with the least abuse of my hands possible. For me, one more click per file I open actually matters, not to mention that this is a change from my prior workflow habits that I would have to get used to. Next I need an automator action that will recurse a directory dropped on it and remove this flag so I can get on with my work when I download client files from a live server.

[MacOSXHints: Thanks for the script!]


Liberate Your Website

[ Reply to This | # ]