Apex web control app with simple button UI

I get:
Parse error: syntax error, unexpected '}' in /home/mydomain/public_html/mydomain.com/apex/index.php on line 51
I suspect that you replaced the whole section I quoted... replace JUST the last line (containing the die function)
 
Insomniac and Russ - thanks! Bugs fixed in the copy at the above link as of now.

Mike - after seeing your description of your setup, its got to be a file permissions problem. The web server user must have write permission on the directory where the files are stored. In your case, the files are in a public_html directory. This is probably owned by your user, rather than the web server user. You need to figure out a way to give the web server write permission. The simplest way (although not good in steady-state, its a security hole) is to make the directory (not just the files in the directory) be world-writable. A better way is to use groups to do this.

For example, for the web server I am running (ubuntu linux running apache2), the web server user is www-data. So that user has to have write permission on the directory the files are contained in.

HTH,
Dave
 
Just confirmed the bugfixes. Looks good. I do have one other issue which doesnt seem to be permission related (I believe i've confirmed all permissions are correct). If i create a setData.xml file placeholder i get no errors on the first page launch . After first page launch, the file is deleted and I get the following:

"Warning: unlink(C:/Program Files (x86)/EasyPHP-5.3.6.0/www/apex/setData.xml) [function.unlink]: No such file or directory in C:\Program Files (x86)\EasyPHP-5.3.6.0\www\apex\index.php on line 10"

This is repeatable.

Thanks again for this. I love not having to confirm the change and having quick access to all the primary functions. Good code makes for a happy and lazy reefer :D

Edit:I know it still points at write permissions, just not sure why. I'll try and figure out why later.
 
Last edited:
Nevermind. I just realized that it must be something with my php implementation or how windows grabs the xml file. It doesnt seem to write the file at all. Just keeps it in memory. If i remark line 10 out, all is well.

Brain farts...
 
OK - I rewrote the application to not write any files... probably should have done it this way in the first place :spin2:

Since it doesn't write any files, there should be no file permissions issues...

Grab the latest copy above :spin1:

Dave
 
Back
Top