Drupal6-latest stable version of FCKeditorinstalled.

Just putting a new site up-FCKeditor worked in a development site - no problem

I have installed FCKeditor exactly the same in the live site - I now get the following when trying to browse the server
'There is no valid directory specified for the file browser!'

Doesn't seem to matter what I do - this persists - using IMCE.

Any ideas anyone, please. Pulling my hair out with this.

Cheers!

Mike

Comments

Eugene Dubois’s picture

did you define your files directory in the system module?

wmike’s picture

Hi,

In file system i have - 'sites/default/files'

frost’s picture

i am having the same problem, drupal 6.x new install with fckeditor and imce. i think it might be related to directory permissions. if i log in as admin it works fine but when logged in with user who has imce/fckeditor rights i get the same error.

frost’s picture

i solved this by filling in missing configuration info for IMCE:

admin/settings/imce/profiles - edit whatever profile is appropriate

under the Directories heading, fill in the folder name and give whatever permissions you want. you cannot leave the folder name blank because then the permissions aren't saved (that was what i had done).

najibx’s picture

can but only for root user. For others, you must create a folder under the file system.

drvdt’s picture

in "admin/settings/imce/profile/edit/" you set diretcory/diretcory path:
add "dot" (.) in box "site/default/site"
check: including...; browse; upload; thmbnails; .....

OK ok
Good luck

My sites: Medicare

strellman’s picture

"To specify file system root, just enter .(dot) character."
So you can't leave the path blank or it won't save the settings for this profile. If you are using a i18n_ variables for file_directory_path you may need to save these settings for each language.

deepsoulstarfish’s picture

The settings for the files directory location in IMCE module settings and ckeditor module settings have to match.

escoles’s picture

Two additional notes on this problem:

First, this is an IMCE problem, not an editor problem. You'd have it no matter what you were integrating IMCE with.

Second, and this is important: not all users will see this problem. I've just gotten done debugging it in a scenario where some users could see it, and others could not. E.g., I was never able to replicate the problem, logging in as a user with identical permissions. In my case, this meant that I was able to configure the system initially without adding correct directory specification info, and never realize there was a problem until users pointed it out to me.

mikedotexe’s picture

Adding the dot under:
admin/config/media/imce/profile/edit/[X]

for the "directory path" worked for me. thanks guys.
makes sense but I wouldn't have thought of it immediately

Hakuna Matata