Error on attempting to load an image to content

I cannot find anything on this in the forum. On attempting to load an image using either FCK or tinyMCE I get to the point where I click the upload button and I get an error message;"error"failed to upload file, internal error . . ."
I checked the permissions on the DB and I am good for read/write on all tables. Any Ideas on this?
Thanks,
HalD

I found the problem - an invalid path to the assets folder. In Tools->configuration->Interface & Features->resource URL and Tools->configuration->Interface & Features->Resource path and Tools->configuration->file manager-> file manager path both had an incorrect path. Since I use Apache and not IIS, I thought it would have been changed automatically when I upgraded to MODx 0.96-rc1 and didn’t think to check it until now. I changed those 3 to the correct path and now images upload correctly.
HalD

Quote from: hald at Mar 25, 2007, 02:42 PM

I found the problem - an invalid path to the assets folder. In Tools->configuration->Interface & Features->resource URL and Tools->configuration->Interface & Features->Resource path and Tools->configuration->file manager-> file manager path both had an incorrect path. Since I use Apache and not IIS, I thought it would have been changed automatically when I upgraded to MODx 0.96-rc1 and didn’t think to check it until now. I changed those 3 to the correct path and now images upload correctly.
HalD

Ummm, well I checked what you said, and everything seemed to be pointing to the right place.
Here is a screen capture of what I am seeing when I try to upload a file *shrugs*. This is getting old.

That’s because you don’t completely understand the permissions involved here. To upload a file to your site root using a script (and the file manager is a script), you site root has to be set to world-writable, since the directory is owned by "you", while the script is running as the Apache user. No hosting will do that, it is extremely dangerous. You might be able to change the settings if your ftp client lets you go above your site root in your "home" directory, but I repeat, that is extremely dangerous. You are quite likely to have some hacker insert an index.html file which will override the index.php file, and your site is "owned".

Only the directories that are specified in the installation should be world-writable; assets/images etc.

Well I read your post I see the light. Boy did I make this way harder than it had to be *shrugs*

Susan, I realize you made your comment that assets/images should be word-writable five years ago.

I had been using an images directory with permissions of 777 to accommodate PHP running as user "nobody" having the ability to upload files and also dynamically create thumbnails for FTPed images.

Two weeks ago the images directory was hacked and the hacker wrote a few php scripts which sent out some obscene spam from our domain.

The server administrator caught this fortunately and changed the images directory to 755.

All that having been said, I'm now back to being unable to upload to images. I can FTP necessary images but the MODx editors are unable to create thumbnails for me.

Now that it's 5 years later, is there any relief available in MODx to accommodate PHP running as "nobody"?

Thanks ... Sam