By wisemas on

Hi all,

I am currently working on a site for a client, and the images are not showing. After looking around the site, I have come across the following error under reports/status report:

You are using a feature that requires $cookie_domain to be set, but it is not set in your settings.php (either built-in filebrowser or quick uploads are enabled in the Advanced profile).

Here is what I have done:
* Upgraded the modules
* Turned off quick uploads
* Turned on quick uploads
* Disabled IMCE
* Tried using the built-in file browser

Currently the site contains no images, as all the links to these images are currently broken.

Any help or suggestions would be greatly appreciated.

Thanks in advance,

Wisemas

⋅ Categories: Drupal 6.x

Comments

wisemas’s picture

wisemas commented

I assume I am on the right track by enabling the $cookie_domain in the settings.php file.

I now get the following message on the report page " You are using a feature that requires manual integration into config.php (either built-in filebrowser or quick uploads are enabled in the Advanced profile). Read instructions about enabling built-in file browser and add "require_once ..." statement in editor/filemanager/connectors/php/config.php."

matkeane’s picture

matkeane commented

Hi,

If you're installing FCKeditor, it really helps to read the READ-ME.txt in the module folder, as it explains all the steps involved in configuring file uploads. Because you are activating a nice UI that will allow users to potentially upload almost anything to your server, you have to jump through quite a few hoops in order to get everything working. It probably could be easier but I think the module developers prefer that you don't open up a any holes by accident.

From memory, once you've added the cookie domain in settings.php, and modified the connector config.php file, you can go back to the drupal UI and set permissions, roles that can use FCKeditor uploads and on which pages the editor should be displayed.

wisemas’s picture

wisemas commented

Hi Mat,

Thanks for your reply. In terms of the site in general, it has been live for the last 8 months and this is the first time this issue has occurred. I had configured FCK editor to work with IMCE before the site went live.

Is there any possibility that I would have needed to configured the cookie domain settings in php before I enabled the fck editor?

Thanks

Wisemas

matkeane’s picture

matkeane commented

Hi,

That's strange - I thought the cookie_domain setting was a prerequisite to getting FCKeditor and file uploads happening. I wonder whether the error messages in your site reports page were added in an update to the FCKeditor module - that might explain why you're only seeing the errors recently.

wisemas’s picture

wisemas commented

Hi Mat,

On another issue, I was talking to someone else in the drupal community last night regarding my site, and they said to remove the .htaccess file which is stored in the root directory, which I have done, and now cannot view my site at all.

Any suggestions?

matkeane’s picture

matkeane commented

Ermm, the .htaccess file which comes as part of the drupal distribution? I'd be tempted to put it back! You won't get clean URLs or www-to-non-www redirects without it. If you have a problem with a particular part of the .htaccess, or need to adapt it to a specific host (There have been a lot of posts over the last 24 hours about a particular host changing their server config), then by all means modify it (carefully).

wisemas’s picture

wisemas commented

Hi Mat,

Thanks for that. I had backed up the site before I removed the .htaccess file. It turns out the company I was hosting the site with, was doing some maintenance on their servers, but had not advised me of this. The site is back up now, and the images are working fine.

I didnt have to change the $cookie settings in the settings.php file.

Thanks for your help,

Wisemas

matkeane’s picture

matkeane commented

It's been so long since I did an FCKeditor install, I thought I'd check the README to see if things have changed. It still mentions the cookie_domain setting, but that is required to get the FCKeditor built-in file browser working. If you're using IMCE to deal with image uploads, you might not need it, but perhaps recent versions of FCKeditor warn you if it's not set anyway.