Skip to main content

CKFinder Installation in the CKEditor for Drupal 7 Module

Please follow the steps below;
 Go to http://ckfinder.com/download and download CKfinder

 Unpack the contents of the installation package into the directory that contains the CKEditor module and place it in thesites/all/modules/ckeditor/ckfinder (or sites/all/libraries/ckfinder) folder. . When the files are unpacked, you should see the following file structure inside the drupal/sites/all/modules directory:

 Now open the CKFinder configuration file (ckfinder/config.php) and introduce the code changes described below.

 Firstly, remove the CheckAuthentication() function (do not worry, this function is defined in filemanager.config.php, see below):

 function CheckAuthentication()       <- remove it
{                                    <- remove it
   //WARNING : DO NOT simply...      <- remove it
   ...                               <- remove it
   return false;                     <- remove it
}

 For CKFinder installed in the sites/all/modules/ckeditor/ckfinder directory add:

 require_once '../../../../includes/filemanager.config.php';
straight below the following line:

 $baseDir = resolveUrl($baseUrl);
For CKFinder installed in the sites/all/libraries/ckfinder directory add:

 require_once '../../../../../modules/ckeditor/includes/filemanager.config.php';
straight below the following line:

 $baseDir = resolveUrl($baseUrl);
Now open the Drupal settings file (sites/default/settings.php) and do the following:

 Uncomment the $base_url variable and set the base URL of your website (without the trailing slash).
Uncomment the $cookie_domain variable and set the domain name of your website.

 Select CKFinder as a preferred file browser in the Administration panel > Configuration > Content Authoring > CKEditor section (for a selected CKEditor profile scroll down to the File browser settings section).
Refernce URL's here 

 In CKfinder documentation
In Drupal documentation

Labels:

Comments

Post a Comment

Popular posts from this blog

Difference between session.gc_maxlifetime and session.cookie_lifetime in Drupal setting.php

ini_set('session.gc_maxlifetime', 200000); This value is for the server. It is a settings for Session Garbage Collection. If the users last visit happened before 200000s then this session is eligible for garbage collection. Since it is GC, the session value may be discarded and not compulsory. If a GC action happens after the session was made eligible for the GC, it will be deleted. ini_set ( 'session.cookie_lifetime' , 2000000 ); This value is for the browser. This is the absolute maximum time till which a browser can keep this cookie active. A 0 value here means immediate or when the browser is closed. Source: 
Post a Comment
Read more

Smart pagination or page break in Drupal 7(CK editor)

1. Install Smart Paging module   Go to Administration › Configuration › Administer Smart Paging settings.   Under 'Default page break method', select "Manual placement of page break placeholder". 2.  Install  'Ckeditor' Module   Go to Administration › Configuration > Ckediotr profiles > Filtered HTML   Edit the settings of the Advanced (Filtered HTML) Profile. Under 'Editor Appearance' section, In plugins check the required options like " Plugin for inserting a Drupal teaser and page breaks. ". 3.  Edit the configuration settings of input formats (Filtered HTML, Full HTML, Plain Text)   Go to Administration › Configuration > Text formats. Edit the required input format. For example say "Filtered HTML". Under  "Enabled filters" section, check the 'Smart Paging' option and uncheck all the remaining checkboxes. 4. Go to Content type 'article' and create new content. We will s...
6 comments
Read more

Difference between webform vs entityform in Drupal 7

Drupal has a lot of modules aimed at helping site builders and users add forms to their sites. What follows is a rough comparison of 2 of them. If there are any I've missed, please add them. Webform Webform is a module designed to allow you to add custom forms to the front-end of your site. Each form is stored against a node, so you add new forms to your site as if you were adding content. It's useful for things like Survey websites or just where you want a couple of forms that differ from the standard contact form. Pros Webform has been around for a long time, its very well established and has a large number of modules that  integrate with it . Webform can make a wide variety of forms with lots of different elements available out of the box. Because Webforms are nodes, they inherit all the functionality that nodes have (scheduled publishing, cloning, access control, etc.). Webforms are lighter-weight and more scalable than entity-based forms. Can handle multiple-p...
Post a Comment
Read more