I meant irev scripts. I want to have some functionality be hidden from
people with access to the scripts on a web site (say, a funciton that
uploads things to my ftp site, so contains my ftp username and password).
If I was using CGI I could password protect that stack - but then the
other people would need LC to be able to do anything to the CGI scripts.
Therefore I need to use irev so the other people can edit simple irev
text files (in reality, so they can edit the html parts of the irev
files :-) But that doesn't allow me to protect the usernames/passwords.
OK, I can work around it by using both a .irev and a CGI script, and
POSTing the data from the irev to the CGI stack, so I have both
user-friendly .irev files to edit *and* protected stacks; but that's
extra complexity that I'd really like to avoid.
-- Alex.
On 19/02/2011 01:29, J. Landman Gay wrote:
On 2/18/11 6:48 PM, Alex Tweedly wrote:
and some features are just unavailable
- can't use password-protected stacks, so you cannot protect stack
scripts on clients' sites
But we can't use stacks at all in iRev yet. Or did you mean for CGI?
For old-style CGI you should be able to use password protected stacks,
but you'll have to protect them with the 3.5 engine. The password
scheme was changed in 4.0, and the 3.5 engine doesn't work with it.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
