elfinder: Unable to open '#' Folder not found.
See original GitHub issueWhen opening the elfinder, i am getting the following error in JS console:
elfinder debug: [error] [elfinder] Unable to open "#".<br>Folder not found.
I am using the following disk:
'uploads' => [ 'driver' => 'local', 'root' => public_path('uploads'), ],
Somehow an empty string is given as folder, therefore the ‘#…’, any ideas?
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (4 by maintainers)
Top Results From Across the Web
ElFinder in NewsPublisher - Unable to connect to backend 404
“Unable to connect to backend. Backend not found. HTTP error 404.” I have installed NewsPublisher from scratch on the live site.
Read more >php - How to show a specific folder when the interface opens ...
Is there a way to open a specific folder when the elFinder interface opens? I want to set the folder, either by a...
Read more >Class not found for elFinder(Open-source file manager for ...
Hi, I'm using elFinder(Open-source file manager for web) in Codeigniter 3, works fine but in Codeigniter 4.1.3 i can not integrate it and ......
Read more >elFinder giving error and how to prevent ... - JoomlaWorks
I noticed that the there is no issue on the backend K2 image tab, ... using elFinder, I cannot prevent bloggers accessing only...
Read more >Demo:elFinder - Web File Manager - GitHub Pages
elFinder - file manager for Web - open source project under the 3-clause BSD license.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi,
I had the same problem and after searching for a while, I’ve successfully tracked the problem.
On the line 3457 of
elfinder.full.js
, the is an event bound on thewindow
called message which call an additional request. When calling a new request, it aborts current requests of typeopen
.Now, the problem was one of my extension installed on Chrome, Grammarly in my case. That extension was triggering
message
on page load, aborting the initial request of elFinder. When it was doing the.sync
, thetarget
param sent inget
was empty, causing the error.From what other users are saying, they might have the same problem. Elfinder works on other browsers since they probably have no extensions.
Now, the fix was easy, disabling the extension solved everything, but it is not practical. In the end, the problem is not with CRUD, nor Laravel-Elfinder, it is in elFinder itself. I’m relatively new to Github, so if someone could reference this issue to elFinder (or even better teach me), it would be nice!
The question to elFinder authors is: Would using a prefix for the event instead of a namespace be possible? It would solve that problem at least.
@kagagnon thanks a lot for sharing your findings. It makes a lot of sense now - for it to be a Chrome extension 😃
Here’s the elFinder repository - https://github.com/Studio-42/elFinder
Cheers!