elfinder - unable to connect to the backend [#1787812]

Hi,

I am trying to use the elFinder as a block content on a page and getting the error "unable to connect to backend".

I have attached a screenshot for review.

In my connector.php its looking for a files directory. I am guessing its looking for /sites/default/files which does exist.

What am I missing or doing wrong?

Thanks for your help.

Comment	File	Size	Author
	2012-09-18_0859.png	25.95 KB	gjaswal

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

gjaswal CreditAttribution: gjaswal commented 19 September 2012 at 00:59

Update:

When I navigate to http://localhost/site/?q=elfinder I get the "Unable to connect to the backend".

I followed the ReadMe instructions but I cannot administer the backend.

Any help would be much appreciated.

Thanks

Comment #2

bancarddata CreditAttribution: bancarddata commented 19 September 2012 at 18:38

I was having the same issue with "unable to connect to backend". I fixed it by making sure I am using the latest dev build, and then also getting the latest elfinder library code. This seems not to work with the 2.0rc1 which is the recommended download.

I actually went to https://github.com/Studio-42/elFinder and hit the "ZIP" button to get a zip file of the latest code. The contents of this zip file get extracted to your sites/all/libraries/elfinder directory (I would delete the older version from that directory first). Then, for security purposes you should delete a few files from that directory after you extract the files, i.e. elfinder.html, php/connector.php, and php/connector.minimal.php (you will get warning messages about this if you don't).

The direct link to the zip download is https://github.com/Studio-42/elFinder/zipball/2.x

Hope this helps - worked great for me.

View changes

FWIW same problem found by downloading latest Library from sourceforge, to match 2.x-dev...

Comment #7

gaurav.goyal CreditAttribution: gaurav.goyal commented 17 March 2015 at 07:30

I am also having the same issue, and behavior is random, sometimes it works but most of the time is shows the error.

Thanks.

Comment #8

wOOge CreditAttribution: wOOge commented 5 March 2016 at 00:45

I had the same issue — was using elFinder Module 7.x-2.x-dev (2015-Aug-24) — but after downloading elFinder v2.1.7 from here: https://github.com/Studio-42/elFinder/releases the error seems to go away.