Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Thiw warning should appear if you have enabled the built-in file browser.
According to instructions from README.txt, you should set the $cookie_domain variable in sites/default/settings.php so that FCKeditor file browser could authenticate each user that is trying to use it, otherwise FCKeditor file browser will inform you that it is disabled.
This "error" has only just appeared after I upgraded to 2.0-alpha1 from 1.2. In the profile I have IMCE selected for file browser type. See attached image.
I forgot to clarify it better: FCKeditor file browser / connector is used in two situations:
- when built-in file browser is enabled
- when quick uploads are enabled
so if you're using IMCE instead of FCKeditor's file browser, there is still a chance that you're using also quick uploads, am I correct? If you turn them off, you'll probably not get this warning. If you have quick uploads disabled, then it is a bug. Please check your settings and let me know.
Jorge CampoCreditAttribution: Jorge Campo commented
I noticed that if you have other profiles than the default one, you have to be sure that, for the other profiles, "quick uploads" are disable too.
Otherwise you will still get the message.
To tell you the truth, it is quite difficult all this stuff changing things here and there directly in the files without understanding.
Anything that involves changing file line codes, instead of checking or unchecking options makes things difficult for the non-technical people like myself.
Anyway, thanks a lot for those of you who have the patience...
FCKeditor file manager is not designed to work in a Drupal specific environment (e.g. lack of access to Drupal session outside of the root folder without bootstraping and so on), that's why some manual changes in the configuration file are required.
The error appears after upgrading because in FCKeditor 1.4 did not check for this problem while 2.0 does. It occurs when $cookie_domain is not set and you have enabled either quick uploads or the built-in file browser. It may be the case that you had enabled them all along, but never used them. In that case, you should disable them in your profiles. Otherwise, edit the config.php.
If you still have a problem, please submit your config.php. Of course, you should remove your database string and other sensitive parts. You can also send just the section containing $cookie_domain.
from my config, still does not work and the settings in fckeditor connect.php is set to true
/**
* Drupal automatically generates a unique session cookie name for each site
* based on on its full domain name. If you have multiple domains pointing at
* the same Drupal site, you can either redirect them all to a single domain
* (see comment in .htaccess), or uncomment the line below and specify their
* shared base domain. Doing so assures that users remain logged in as they
* cross between your various domains.
*/
$cookie_domain = 'yosemiteforum.net';
also did this as per error message
Read instructions about enabling built-in file browser and add "require_once ..." statement in editor/filemanager/connectors/php/config.php
and still get error message
funny thing is i can upload photos through the "built-in file browser" and quick uploads are disabled
If you get the issue about the require_once line, please attach your config.php. I can only help if you supply your config.php. Please be advised that security is not guaranteed when config.php is not set up according to the instructions, because the require_once line is checking permissions.
I have FCK editor installed, and trying to enable FCK file manager.
It tells me that in order to use it, $cookie_domain must be set.
Easy enough, I set it to www.mysite.com. I can log in, register, etc just fine. However I started seeing a number of people get Access Denied after logging in or trying to access any protected area.
Commenting out $cookie_domain, users can get in fine.
I am looking for one of the following:
A. A harmonious answer where FCK file manager and $cookie_domain can be set
-or-
B. An alternative to FCK editor (like CK) that allows in-place file uploading without requiring cookie domain to be set (and interrupting user experience).
Comments
Comment #1
wwalc CreditAttribution: wwalc commentedThiw warning should appear if you have enabled the built-in file browser.
According to instructions from README.txt, you should set the $cookie_domain variable in sites/default/settings.php so that FCKeditor file browser could authenticate each user that is trying to use it, otherwise FCKeditor file browser will inform you that it is disabled.
Comment #2
fishdiy1 CreditAttribution: fishdiy1 commentedI'm not using the built-in file browser, I'm using IMCE.
Comment #3
fishdiy1 CreditAttribution: fishdiy1 commentedThis "error" has only just appeared after I upgraded to 2.0-alpha1 from 1.2. In the profile I have IMCE selected for file browser type. See attached image.
Comment #4
wwalc CreditAttribution: wwalc commentedI forgot to clarify it better: FCKeditor file browser / connector is used in two situations:
- when built-in file browser is enabled
- when quick uploads are enabled
so if you're using IMCE instead of FCKeditor's file browser, there is still a chance that you're using also quick uploads, am I correct? If you turn them off, you'll probably not get this warning. If you have quick uploads disabled, then it is a bug. Please check your settings and let me know.
Comment #5
wwalc CreditAttribution: wwalc commentedFixed in CVS (added better description and link to a profile where filebrowser or quick uploads are enabled).
Comment #6
Jorge Campo CreditAttribution: Jorge Campo commentedI noticed that if you have other profiles than the default one, you have to be sure that, for the other profiles, "quick uploads" are disable too.
Otherwise you will still get the message.
To tell you the truth, it is quite difficult all this stuff changing things here and there directly in the files without understanding.
Anything that involves changing file line codes, instead of checking or unchecking options makes things difficult for the non-technical people like myself.
Anyway, thanks a lot for those of you who have the patience...
Comment #7
wwalc CreditAttribution: wwalc commentedFCKeditor file manager is not designed to work in a Drupal specific environment (e.g. lack of access to Drupal session outside of the root folder without bootstraping and so on), that's why some manual changes in the configuration file are required.
Comment #9
magnum2000 CreditAttribution: magnum2000 commentedHello, I'm using Drupal 6.16 and FckEditor 2.6.5 and although I changed the settings.php, I still receive the error.
Comment #10
yosemite CreditAttribution: yosemite commentedsame here
Comment #11
Jorrit CreditAttribution: Jorrit commentedThe error appears after upgrading because in FCKeditor 1.4 did not check for this problem while 2.0 does. It occurs when $cookie_domain is not set and you have enabled either quick uploads or the built-in file browser. It may be the case that you had enabled them all along, but never used them. In that case, you should disable them in your profiles. Otherwise, edit the config.php.
If you still have a problem, please submit your config.php. Of course, you should remove your database string and other sensitive parts. You can also send just the section containing $cookie_domain.
Comment #12
yosemite CreditAttribution: yosemite commentedfrom my config, still does not work and the settings in fckeditor connect.php is set to true
/**
* Drupal automatically generates a unique session cookie name for each site
* based on on its full domain name. If you have multiple domains pointing at
* the same Drupal site, you can either redirect them all to a single domain
* (see comment in .htaccess), or uncomment the line below and specify their
* shared base domain. Doing so assures that users remain logged in as they
* cross between your various domains.
*/
$cookie_domain = 'yosemiteforum.net';
Comment #13
renenee CreditAttribution: renenee commentedfollowing this issue
Comment #14
yosemite CreditAttribution: yosemite commentedalso did this as per error message
Read instructions about enabling built-in file browser and add "require_once ..." statement in editor/filemanager/connectors/php/config.php
and still get error message
funny thing is i can upload photos through the "built-in file browser" and quick uploads are disabled
Comment #15
somewhere2go CreditAttribution: somewhere2go commentedsame here
Comment #16
christo CreditAttribution: christo commentedThe issue with upgrades causing the "cookie_domain" and "Read instructions about enabling built-in file browser and add "require_once..." still exist as of this date. The cookie_domain error is well explained by the error message from the FCKeditor module in the status report. I just pinned down the "require_once..." nonsense. See: #324053: I get the error message "error creating folder /www/drupal/sites/all/default/files/ cannot create directory" but im using IMCE
Post #8
Comment #17
Jorrit CreditAttribution: Jorrit commentedIf you get the issue about the require_once line, please attach your config.php. I can only help if you supply your config.php. Please be advised that security is not guaranteed when config.php is not set up according to the instructions, because the require_once line is checking permissions.
Comment #18
scottsawyerUncommenting the cookie_domain variable and setting to my domain worked like a charm. Imagine that!
Comment #19
kevinquillen CreditAttribution: kevinquillen commentedI have FCK editor installed, and trying to enable FCK file manager.
It tells me that in order to use it, $cookie_domain must be set.
Easy enough, I set it to www.mysite.com. I can log in, register, etc just fine. However I started seeing a number of people get Access Denied after logging in or trying to access any protected area.
Commenting out $cookie_domain, users can get in fine.
I am looking for one of the following:
A. A harmonious answer where FCK file manager and $cookie_domain can be set
-or-
B. An alternative to FCK editor (like CK) that allows in-place file uploading without requiring cookie domain to be set (and interrupting user experience).
Comment #20
Jorrit CreditAttribution: Jorrit commentedAre your users accessing your site using multiple host names?
Comment #21
kevinquillen CreditAttribution: kevinquillen commentedNo, for right now its just www.mydomain.com.
It has a second site ready to be launched in a few months which will be www.myotherdomain.com.
I have the .htaccess rule uncommented so it goes to www. if not provided.
I am using Domain Access if that helps.
Comment #22
Jorrit CreditAttribution: Jorrit commentedTry this:
Comment #23
kevinquillen CreditAttribution: kevinquillen commentedThis worked for me (Domain Access is installed):
Comment #24
Jorrit CreditAttribution: Jorrit commentedThat's great to hear.
Comment #25
anne1960 CreditAttribution: anne1960 commentedI cannot access the admin part anymore when I uncomment and put my website name in it -$cookie_domain = 'www.example.com';???
Comment #26
Jorrit CreditAttribution: Jorrit commenteddo you use multiple (sub)domains on your site?
Comment #27
anne1960 CreditAttribution: anne1960 commentedyes, I do
Comment #28
brayo4 CreditAttribution: brayo4 commentedon line 169 (# $cookie_domain = 'example.com';)
un-comment this line by removing # mark
Comment #29
alca11 CreditAttribution: alca11 commentedThis helped for me:
Apparently you also have to also have to uncomment $base_url and input your website in the previously mentioned file.
As described here