File Manager problem

For questions and problems with the CMS core. This board is NOT for any 3rd party modules, addons, PHP scripts or anything NOT distributed with the CMS made simple package itself.
Post Reply
nbc
New Member
New Member
Posts: 7
Joined: Mon Dec 29, 2008 10:28 pm

File Manager problem

Post by nbc »

Not sure if the file manager is considered part of the core or an extension - please let me know if this question belongs somewhere else...

I was running version 1.5.1 and just upgraded to 1.5.4. This problem has been happening with both versions...

I have created a number of photo albums and uploaded several hundred photos using the file manager without any problem.
I created a new album, went to the file manager and tried to upload a set of photos and it tells me that the photos failed to load.
The error is "File xxx.jpg failed to load successfully". I tried a different file from a parallel directory and it loads just fine. The difference is that the file that loaded correctly came from my Dad's camera and the one that failed came from my camera. Both were installed on my system (Ubuntu 8.x) using the F-spot photo manager - My files were named DSCxxxxxx.JPG and his were img_xxxxx.jpg but other than that, I see no difference.  Permissions are not the problem, since one set of files loads correctly. I can open my files with GIMP and they look fine.

I tried renaming my files to img_xxxxx.jpg but that did not help.

Can someone give me a hint as to what I need to do to import these files? When I hit the troubleshooting link under the error, it goes to this page - which doesn't seem to relate to what I'm doing at all...

==============
* An error occurred while trying to create the directory (Troubleshooting)


Ownership issues So you just came in from this link? Well this could happen due to many reasons, but it you tried everything in the forums (maskes/rwx/etc) in short it'll most likely boil down to a permissions issue of ownership. Most likely to be as fallows...

User as ftpUser / Group as psacln(etc) made a file as not able to be edited by the User as apache / Group as apache.

and at that point (after you ssh in to the root and chown() the folder making it so User as apache / Group as apache could rwx) but now you could see the reverse where a file created by User as apache / Group as apache is such that the User as ftpUser / Group as psacln(etc) can't rwx the files/folders just created, even with masking, or/and a sticky bit as this is a chown() issue...

Plesk setups are ones that have this weakness.  etc. etc. etc.
==============

Thanks in advance,

nbc
Post Reply

Return to “CMSMS Core”