in reply to Mac::AppleScript::Glue in CGI script

See the CGI Help Guide. Amongst your issues is not printing a valid header (500 Internal Server Error). However if you did have a valid header and it runs on the command line the problem is almost certainly permissions as a CGI runs as the webserver user (nobody or apache typcially) not user you. Add this to see what the problem is: 

BEGIN {
    $|=1;
    print "Content-type: text/html\n\n";
    use CGI::Carp('fatalsToBrowser');
}

[download]

cheers

tachyon

Replies are listed 'Best First'.
Re^2: Mac::AppleScript::Glue in CGI script
by Cody Pendant (Prior) on Nov 13, 2004 at 08:44 UTC
    I'm sorry not to have pointed out, I didn't just take the script above and try to run it as a CGI.

    I printed a valid header and used CGI::Carp and that didn't help. It still died silently at the line noted.

    Here's a script which works in the command-line and not in the browser: 

    #!/usr/bin/perl
use CGI::Carp qw(fatalsToBrowser);
print "Content-type:text/plain\n\n";
require Mac::AppleScript::Glue;
print "started\n";
my $BB = new Mac::AppleScript::Glue::Application('BBEdit')
  || die "$!";
print "success creating Applescript Glue App object\n";
my $results = $BB->check_syntax(file =>
'path:to:file')
  || die "$!";
print "success checking syntax\n";

    [download]

    It gets as far as the first success message, and then, if the file exists, just stops.

    If I try it on a file which doesn't exist, then yes, I get a failure from AppleScript and CGI::Carp does its thing. But if there is a file at that location, then it just stops.

    What can I investigate in terms of permissions?


    ($_='kkvvttuubbooppuuiiffssqqffssmmiibbddllffss')
    =~y~b-v~a-z~s; print
[reply]
[d/l]
      Take a dummy file, chmod it to 777, then point your script at it. 777 is world-writable so if it works you know you have a permissions problem. If it doesn't work then it's probably something else. Either way, delete the file after you run your tests.
[reply]

      In addition to the chmod 777 test file check you should switch debugging on. The syntax is a bit clunky but you do: 

      $Mac::AppleScript::Glue::Debug{SCRIPT} = 1;

      [download]

      Where SCRIPT can be SCRIPT,RESULT,PARSE,INIT,AUTOLOAD. This should get you more output if it is not a simple perms issue (which I still think it is). When you say stops there is stop and STOP! Is it hung or exited? Is it using 100% CPU or 0% cpu? Does it timeout eventually?

      cheers

      tachyon

[reply]
[d/l]

In Section Seekers of Perl Wisdom