I'm trying to get this running but keep getting the error "folder <path> does not exist". I've tried various folder locations, with different pemissisions and ownership, but to no avail. I'm trying to set this up on a CentOS box.
What else should I try?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you give a bit more details, like: which paths have you tried?
Can you ensure that you are using the full path? Can you ensure that you've edited both paths (normal and local (2 lines underneath)). If you're setting ecoder up on a local server, and thus browsing to it from the same machine, it will use the second path. Can you try to use PHP's DIRECTORY_SEPARATOR instead of hardcoded (back)slashes (although that shouldn't cause a problem on linux systems, afaik)?
Good luck!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I must say this is quite a strange bug. Could you check whether there's a file called .ecoder_permissions_check.txt in /home/scotty/files/? Also, is the files folder of a special kind (link, for example?)?
Sorry for the inconvenience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there any way you can confirm that the folder in your $code setting exists - if your server control panel provides a visual file browser perhaps you can send a link to a screenshot - showing all the folders open from your domain root to the files that you want to edit with ecoder?
If not, the problem might be that you are trying to reference a symbolic link - perhaps due to how your server is set-up - is there any way you can ask your host to provide the full file path to the folder you want to edit?
good luck
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a box that I am root of. The Apache is set up with mostly defaults and isn't doing any virtual hosting or anything. I can verify that the folder exists and isn't symbolic link. I could take a screen shot of my terminal window, but it would look like this:
$ pwd
/home/scotty/files
$ ls -lah
total 12K
drwxrwxr-x 2 apache apache 4.0K Jan 14 23:10 .
drwx---- 26 scotty scotty 4.0K Jan 15 11:38 ..
I realize that this should be a not problem, but I just can't seem to get over this hump. I can verify that php, with a file_exists, can find it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On CentOS it will not work in local mode (at least not my installs). Are there any extra php functions that you are using in this? The default install of php on CentOS only installs the basic/default options of php. If one needs BC or Pear or something else, it has to also be installed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-02-28
I'm having a similar problem, but it's possible that I misunderstood the instructions for how to set the file path after installing, and how ecoder can be used.
I installed it through Dreamhost's web panel, and then edited code.php to point the root to a subfolder in the install folder on my server, since what I understood the description of ecoder as being able to do and what I want to be doing is have the files on a folder on the server so I can access them from anywhere. But all I get is "folder <path> does not exist" and then "error creating home tab". I might have misunderstood what sort of path I'm supposed to put in, but I've tried a few things and nothign works. And I'm getting the same ///home.txt thing as djpolstee.
I'm completely stumped.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, could you try the new version (available for download via tags on our github). Also, we'll be closing this page soon. Our new support forum is on this google group.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to get this running but keep getting the error "folder <path> does not exist". I've tried various folder locations, with different pemissisions and ownership, but to no avail. I'm trying to set this up on a CentOS box.
What else should I try?
Hi djpolstee,
Could you give a bit more details, like: which paths have you tried?
Can you ensure that you are using the full path? Can you ensure that you've edited both paths (normal and local (2 lines underneath)). If you're setting ecoder up on a local server, and thus browsing to it from the same machine, it will use the second path. Can you try to use PHP's DIRECTORY_SEPARATOR instead of hardcoded (back)slashes (although that shouldn't cause a problem on linux systems, afaik)?
Good luck!
wimtibackx,
the paths I've tried have been
/home/scotty/files
/home/scotty/ecoder_files
/var/www/html/ecoder/files
files/
I tried with the DIRECTORY_SEPARATOR but got the same results.
I am trying this in a non-local environment, meaning I'm setting this up on a development server and trying to access it from my workstation.
Thanks for your suggestion. Got any more to try?
Hi djpolstee,
Have you tried the paths you specified like that (without trailing slash)? The trailing slash is required.
No, I had the trailing slash. I just didn't type it out in the message.
If it helps, in the current home tab, where $code = /home/scotty/files/ it reads
/home/scotty/files///home.txt
Hi djpolstee,
I must say this is quite a strange bug. Could you check whether there's a file called .ecoder_permissions_check.txt in /home/scotty/files/? Also, is the files folder of a special kind (link, for example?)?
Sorry for the inconvenience.
Hi djpolstee,
Is there any way you can confirm that the folder in your $code setting exists - if your server control panel provides a visual file browser perhaps you can send a link to a screenshot - showing all the folders open from your domain root to the files that you want to edit with ecoder?
If not, the problem might be that you are trying to reference a symbolic link - perhaps due to how your server is set-up - is there any way you can ask your host to provide the full file path to the folder you want to edit?
good luck
Loveunit,
This is a box that I am root of. The Apache is set up with mostly defaults and isn't doing any virtual hosting or anything. I can verify that the folder exists and isn't symbolic link. I could take a screen shot of my terminal window, but it would look like this:
$ pwd
/home/scotty/files
$ ls -lah
total 12K
drwxrwxr-x 2 apache apache 4.0K Jan 14 23:10 .
drwx---- 26 scotty scotty 4.0K Jan 15 11:38 ..
I realize that this should be a not problem, but I just can't seem to get over this hump. I can verify that php, with a file_exists, can find it.
Hi djpolstee,
I'm pretty stumped - can you install it locally - perhaps there is some problem with the code you've downloaded?
On CentOS it will not work in local mode (at least not my installs). Are there any extra php functions that you are using in this? The default install of php on CentOS only installs the basic/default options of php. If one needs BC or Pear or something else, it has to also be installed.
I'm having a similar problem, but it's possible that I misunderstood the instructions for how to set the file path after installing, and how ecoder can be used.
I installed it through Dreamhost's web panel, and then edited code.php to point the root to a subfolder in the install folder on my server, since what I understood the description of ecoder as being able to do and what I want to be doing is have the files on a folder on the server so I can access them from anywhere. But all I get is "folder <path> does not exist" and then "error creating home tab". I might have misunderstood what sort of path I'm supposed to put in, but I've tried a few things and nothign works. And I'm getting the same ///home.txt thing as djpolstee.
I'm completely stumped.
Hi, could you try the new version (available for download via tags on our github). Also, we'll be closing this page soon. Our new support forum is on this google group.