Active
Project:
IMCE Tools
Version:
7.x-1.2
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jun 2012 at 20:15 UTC
Updated:
19 Sep 2016 at 00:25 UTC
Jump to comment: Most recent
I've applied several of the patches which removed the various errors I was getting when trying to search. However, my search still returns no results for strings which ought to give results.
Comments
Comment #1
mdallmeyer commentedBump. Is this module still being maintained? No updates for Drupal 6 since 2011...
Comment #2
tekante commentedWhat do you get when you try to access the following path on your site /imce_search_callback? You should see a JSON response with a message embedded similar to "Invalid search criteria, please specify a search". You can try the searching directly using a path of the form /imce_search_callback/1/TEST (replacing test with a search string). This will perform a case insensitive search.
Also, note that this searches your files table so if you have files on the filesystem uploaded in a manner that does not result in an entry in the files table those files will not appear in search results.
Comment #3
inversed commentedI was having a similar problem on version 7.x-1.2 which may have been related to the original poster's issue. The end result was that the loader icon for the search kept spinning and no results or errors were being shown ()other than a JS error in the console).
For me, the problem was that the Devel module's footer was being injected into the JSON output of the callback function. According to the the devel.module's devel_shutdown_real() function, it is supposed to suppress this if the header content type is JSON (among other things).
I put a fix in place to manually disable the footer on the callback page but I think the right solution would be to correctly set the header in the IMCE search callback results.
Edit: Looks like changing "drupal_json_encode" to "drupal_json_output" solves the problem in the right way. I'll try to post a patch when I get a chance.
Comment #4
ladybug_3777 commentedI think this is the same error I'm seeing! The javascript error being spit out is
"class is a reserved identifier"
And it appears to be pointing to the response HTML of
I'm going to try your solution inversed
Comment #5
ladybug_3777 commentedBummer, changing it to...
...did not work. Instead it gave a new error.
However, going into Devel's config and turning off the option for "Display page timer
Display page execution time in the query log box." does make the error go away.
Not ideal, but will work in a pinch for me right now.
Comment #6
goldHmm... I'm having a similar issue to the OP but in my case the issue appears to be that the search isn't firing. I'm on 1.2 and the "search" button is an HTML Button. The JS that processes the click is fired from the form submit.
I get the JS running in 2 different scenarios;
Either of these should work. I am however getting a JS error on these though.
I'm going to switch to the dev branch and start fixing this. I should have a patch soon.
Comment #7
goldFindings;
The 7.x-dev branch appears to be working with jQuery Update and the devel "Display X" options disabled. This is what I've found;
jQuery 1.4 (Drupal core)jQuery 1.5With this in mind, is this still an issue?