Imagemanager and wysiwyg browsing broken (permissions?)

[Hare]

I just installed 1.05 on a new host and I'm having big problems.

I have set up the permissions as described in the installation docs (and the way I've done a dozen times before on different installations). Installation went fine and everything seems to work but...

If I try to open the image browser in the content menu it just loads the admin-home in the iframe (with menus and all).
Also when editing content with TinyMCE I can't see any images if I click the browse button.

If I click on the site preferences and press the test permissions button I get an error. I've tried different file creation masks (002, 022, 018)

I don't think this is a problem with the paths in config.php since filebrowser works fine and also displays the files in the images-directory.

Any ideas what could be wrong? Any ideas would be much appreciated since I was supposed to publish this site tonight (it's 21:55 here in Finland).

[Hare]

bump

I just switched to fckeditor and now I get an error message if I click on the browse server button:

I can't see the top of the alert-box, but the visible part says:

Requested URL:
  http://mydomain.com/modules/FCKeditorX/...
Response text:
  <!DOCTYPE... and it displays the source for the main admin-page.

What on earth is going on? I just reinstalled fckeditor and tried different paths in the config.php but I can't figure this one out.

I just checked out PHP's php_info. Document_root is correct and the uploads etc paths are ok too. I just can't understand why imagemanager displays the admin-page while the built in filemanager works ok.

Any ideas would be much appreciated.

Thanks

Edit: btw what does the "test permissions" button actually do? I can't pass the test. I believe it tests the file creation mask, but where does it try to write a file? uploads? I've given full permission (777) to uploads folder but I can't pass the test. PHP safe_mode is off.

[Hare]

Ok this is getting weird.

I just installed CMSMS 1.05 to another directory. Didn't work any better so I'm now trying to remove it BUT I can't remove tmp directory.

It seems that files created by PHP are nobody/nobody and I can't delete these with my ftp-account. I just downloaded filethingie (php app) to let me delete files with apache/php priviliges. But still I can't delete this directory. Filethingie says that the directory contains one file but I can't see it with filethingie or my ftp-client. Weird?

I've never dealt with this host but it seems that they have serious issues with privileges?

EDIT: I just did a complete reinstall (including db tables) and imagemanager just doesn't work. Again it loads the main admin-page in the iframe. I have no idea why.

[Hare]

Still troubleshooting.. I made a subdirectory and uploaded 1.02 and it seems to work. Imagemanager and all.

I replaced the newly uploaded 1.02 with 1.05 and imagemanager and wysiwyg browsing are broken again. I quess I have to downgrade. I have no idea what breakes the newer version but I quess I should be happy if I don't have to tell my client to change hosting. It seems that the problem is NOT with my hosting after all. I think there may be bugs in the newer releases that manifest only with certain hosts.

[calguy1000]

The file creation test in site preferences does this:
a) tests to make sure that the test directory "[root_path]/tmp" is writable.
b) creates a test file in that directory
c) retrieves the ownership and the permissions of the file for display
d) removes the file.

If this fails it'll fail for two reasons:  a) the tmp directory is not writable, or b) it can't create a file (safe mode issues?).

If it succeeds it will display the owner, and permissions of the file so you can see how things are created.

If you can't get this function to succeed, then you will probably have problems with uploaded files (images, etc), and the image manager, or using XML module files, or XML themes.

If you're having these problems you need to read up on:
a) PHP safe mode restrictions
b) unix permissions
c) the file creation mask (umask).
and make sure you have a thorough understanding of it.  These are not problems with CMS Made simple, these are restrictions placed on CMSMadeSimple by the hosting environment and the way they have configured their hosts.

[Hare]

Thanks for your reply.

The funny thing is that safe_mode is off and I've given 777 permissions to these directories. I can also upload files and install modules via the module manager.

I quess I need to further test the file creation mask (I've tried 002, 022, 018, 000 etc). I find it quite weird that 1.02 works but 1.05 doesn't. I'm fairly familiar with file permissions and how they apply to apache. I've also done many installations before but this is the first time I've had issues.

I'll start troubleshooting the file creation mask. Thanks for the file creation info.

[Hare]

I just did a clean install of version 1.02 and everything works perfectly.

Before that I tried 1.05 and 1.04 but I had problems. Now with 1.02 everything is peachy. I'm extremely pleased that I didn't have to resort to host switching or other gimmicks. I just uploaded 1.02 and did the exact same thing as before -> gave 777 permissions to tmp etc. Works like all the other installations before (on different hosts).

Maybe this helps if someone else is having problems. I have no idea what broke things but at least this is how I fixed my installation. Now to finish the backend and release the admin section to my client. Thanks!