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.
After changing Exposed form style to use BEF, I am met with the following warning in my browser.
A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Script: /misc/jquery.js?v=1.4.4:101
Thoughts?
Comment | File | Size | Author |
---|---|---|---|
#4 | bef_test_view.txt | 6.15 KB | andiart |
Comments
Comment #1
doliveros CreditAttribution: doliveros commentedI'm also getting this warning using the latest BEF dev build, and selective filters, after selecting a filter. Sometimes the page crashes and I need to force quit firefox.
Comment #2
nigelw CreditAttribution: nigelw commentedClosing #1823796: BEF settings issue with jQuery as dup of this issue.
Comment #3
mikeker CreditAttribution: mikeker commentedCan someone seeing this issue attach an export/feature of the view in question or give instructions on how to repro this in a new View?
Based on #1823796: BEF settings issue with jQuery it sounds like his may be related to adding a BEF Datepicker on a date filter... But I wasn't able to repro this using that basic case.
Thanks.
Comment #4
andiart CreditAttribution: andiart commentedMy findings are that the error occurs when attaching a display to the view and inheriting it's exposed filters. I will attach the export here and tomorrow can try out some more things.
Some settings in text for everyone:
* bef elements as checkboxes
* displays: panel + attachment
Thanks.
/// Edit: This happens with drupal core 7.17
Comment #5
andiart CreditAttribution: andiart commentedComment #6
andiart CreditAttribution: andiart commentedComment #7
andiart CreditAttribution: andiart commentedI switched off the jquery plugins module and it's working fine again for me.
Comment #7.0
andiart CreditAttribution: andiart commentedtypo
Comment #8
Neslee Canil PintoHi, there will be no more future development for 7.x branch. If you see this issue in 8.x, feel free to file an issue. Closing this as Closed(wont fix).