error when posting videos
Permalink Browser Info Environment
I just did a clean install on an apache server and am running snow leopard and using concrete 5.4. When I go to add this block it gives me this error message: Warning: fopen(/Library/WebServer/Documents/files/videos_playlists/vp_1277472648.xml): failed to open stream: No such file or directory in /Library/WebServer/Documents/packages/moortown_flashvids/blocks/moortown_videos/controller.php on line 150 can't open file
any idea what this means and how to fix it?
any idea what this means and how to fix it?
| Type: | Discussion |
|---|---|
| Status: | New |
I see no such file /Library/WebServer/Documents/files/videos_playlists/
When I go to that path and I get to the files folder, all I see are lots of folders with numbers that contain the files.
I will say Library/WebServer/Documents/packages/moortown_flashvids is read only- does this need to change to read/write?
Do I need to create an empty folder called video_playlists and give everyone read/write access?
Right now files is also read only by everyone- should I change that to read/write or just the new playlist folder I create? Perhaps I should just uninstall and reinstall the package.
When I go to that path and I get to the files folder, all I see are lots of folders with numbers that contain the files.
I will say Library/WebServer/Documents/packages/moortown_flashvids is read only- does this need to change to read/write?
Do I need to create an empty folder called video_playlists and give everyone read/write access?
Right now files is also read only by everyone- should I change that to read/write or just the new playlist folder I create? Perhaps I should just uninstall and reinstall the package.
The folders need to be readable and writable by the Apache user, but for the sake of simplicity "everyone" will work. However, it can be argued that this is a security hole.
If you can upload files via the File Manager, do not adjust the permissions on the ~/files folder.
If ~/files/videos_playlists doesn't exist, I assume something went wrong when the package was installed. Never-the-less, create said folder and grant "everyone" "read" and "write" permission.
Ideally, you should set the owner of the ~/files and ~/files/videos_playlists folder to the Apache server user and set the permissions so that only that user can read and write.
Side note: On my Ubuntu server I have multiple virtual servers set up. Each virtual server has it's own apache user. Or rather, each user runs it's own apache service.
There are many benefits to this, one being the permissions sets. This tightens up any security issues. An other benefit is resetting specific instances of apache as to not interrupt other instances.
If you can upload files via the File Manager, do not adjust the permissions on the ~/files folder.
If ~/files/videos_playlists doesn't exist, I assume something went wrong when the package was installed. Never-the-less, create said folder and grant "everyone" "read" and "write" permission.
Ideally, you should set the owner of the ~/files and ~/files/videos_playlists folder to the Apache server user and set the permissions so that only that user can read and write.
Side note: On my Ubuntu server I have multiple virtual servers set up. Each virtual server has it's own apache user. Or rather, each user runs it's own apache service.
There are many benefits to this, one being the permissions sets. This tightens up any security issues. An other benefit is resetting specific instances of apache as to not interrupt other instances.
that did it! thanks so much!
You are correct in assuming that this is not a "read" permission error. If the file existed, but the Apache user did not have permission to "read" the file, you would get a different error.
This is what the server is saying:
I "failed to open stream" because "No such file or directory" exists, consequently I "can't open file".
In lame-mans terms:
"/Library/WebServer/Documents/files/videos_playlists/vp_1277472648.xml" doesn't exist at all.
My assumption is that either of the folders "/Library/WebServer/Documents/files/" or "/Library/WebServer/Documents/files/videos_playlists/" do not have "write" permission.
If you have successfully added a file through c5's File Manager, then "/Library/WebServer/Documents/files/" does allow "everyone" to "write" to it. So I would assume that "/Library/WebServer/Documents/files/videos_playlists/" is the offending folder.
What I would do first is check to see if that folder exists. If it doesn't, create it. If it does (or after your create it) make sure "everyone" has "read" and "write" access.