Not to minimize your point, it is a valid one, but Runrev has limited
resources, and if they really fully documented everything as well as we would
like, and make it as easily accessible as we would like, we might not see a lot
of development work getting done.
As for the web root access, that
Thanks Andre, Mike, and Phil,
I have it straight now. Stacks go in the web server's root and only legacy
stacks will work. Thank you also for your patience. My Internet coding
abilities are primitive to say the least.
If only the RunRev people would write documentation with some clarity. It
Ok, my mistake, I can't get it to read from my desktop either so ignore
this! Apparently it was reading the old file from the directory also (which
is just plain weird.)
I did create a folder in the server root called stackfiles, made sure the
permissions were correct and was able to hit it from t
I can get it to work outside my web folder (from my desktop) but I have
permissions set so that owner is me with full permissions (rwx) ,group _www
is read (r) (_www on moutain lion server is the www group) it would also
matter what permissions are on the containing folder of course. It is most
li
Gregory,
You can't place files outside of the webserver root folder because that
would be a security risk. You don't want web clients to access your private
data from your home folder. Everything that the web server serves is inside
the DOCUMENT_ROOT.
cheers
andre
On Wed, Aug 29, 2012 at 12:19 P
Hi Mike,
Thanks for the error handling suggestion. I have not tried your test stack yet
but I finally got mine working. But it only works when I place the stack in
the Library/Webserver/Documents, that is, in the same folder as the web file
that calls it. Yet, I left the path in that web fil
Is it possible that the web server user doesn't have read permissions on
the stack file?
Also, though its probably correct in your lc server script, it should be
start using stack "/path/to/stack"
not
start using "/path/to/stack"
On Wed, Aug 29, 2012 at 8:46 AM, Gregory Lypny
wrote:
> Hi Phil,
>
Hi Phil,
Thanks, but no go. I put the stack on my desktop and used
start using "/Users/gregory/Desktop/ParetoServer (Legacy 2.7).livecode"
and from the name of the stack, you can see that I took Mike Bonner's advice
and saved it in legacy format.
Gregory
On Wed, Aug 29, 2012, at 10:2
If other things are working (puts, etc) then returning empty on that line
means there are no stacks in use.
Here is a stack you can test with.
https://dl.dropbox.com/u/11957935/mytest.livecode It has 1 handler in the
stack script, save it next to a test lc script. THe file is saved in 2.7
legacy f
Hello everyone,
When I try
put the stacksInUse
it comes up empty. Could there be something missing in y httpd.conf file (Mac
OS X Mountain Lion)? The only two lines that I have added under are
AddHandler livecode-script .lc
Action livecode-script /cgi-bin/livecode-s
And don't forget you can't use 5.5 version stacks with lc server so any
stacks you use must be saved in legacy format or lc server can't load them.
(file, save as, choose file type at the bottom of the window, 2.7)
On Tue, Aug 28, 2012 at 3:21 PM, Phil Davis wrote:
> Hi Gregory,
>
> Try using th
Hi Gregory,
Try using the full path to the stackfile in your "start using"
statement. That should work. Like so:
start using "/Users/me/Documents/mystackfile.livecode"
Best -
Phil Davis
On 8/28/12 1:54 PM, Gregory Lypny wrote:
Hello everyone,
I've got LiveCode server up and running
before that try to output:
put the stacksInUse to make sure your stack is there.
On Tue, Aug 28, 2012 at 5:54 PM, Gregory Lypny
wrote:
> Hello everyone,
>
> I've got LiveCode server up and running on my Mac (OS X Mountain Lion).
> I'd like to be able to store a bunch of handlers in the stack sc
Hello everyone,
I've got LiveCode server up and running on my Mac (OS X Mountain Lion). I'd
like to be able to store a bunch of handlers in the stack script of a library
stack, but I am not sure where to place the stack and how to refer to it from
within web pages.
Suppose I have a simple tes
14 matches
Mail list logo
