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.
This issue is about the right-hand drop down menu widget that is displayed when the browser window is resized to a smaller width or the page is viewed on a smaller screen such as a mobile (for responsive design).
The menu widget when clicked on does not display the menu options. Seen this on Chrome and Firefox on Mac OS X.
Comment | File | Size | Author |
---|---|---|---|
#15 | jquery_update.png | 45.1 KB | ShaunDychko |
#4 | Screenshot_24_06_2013_14_48.png | 3.96 KB | therobyouknow |
#3 | Screenshot_24_06_2013_14_48.png | 3.96 KB | therobyouknow |
Comments
Comment #1
markhalliwellPlease make sure you're running the correct jQuery Update version per this project's documentation. If you're still having issues, please provide a screenshot or even a better description of what's happening, your message is a little vague.
Comment #2
therobyouknow CreditAttribution: therobyouknow commentedThanks for the solution - JQuery update (2.3) reports that I was running Jquery 1.5 when at time of writing the minimum for bootstrap is 1.7. So the solution was to change the setting in Jquery update to use jquery version 1.7.
By the way, by "right-hand drop down menu widget" I meant:
Comment #3
therobyouknow CreditAttribution: therobyouknow commentedComment #4
therobyouknow CreditAttribution: therobyouknow commentedComment #5
markhalliwellComment #6
giorgio79 CreditAttribution: giorgio79 commentedCould we add the dependency on jquery_update to the info file? drush will download it auto then. :)
https://drupal.org/node/542202
Comment #7
wundo CreditAttribution: wundo commentedHi Giorgio,
I've added a warning on the settings page to remind the user about the jQuery Update, next time, please create a new issue.
Comment #8
wundo CreditAttribution: wundo commentedComment #9
markhalliwellThe committed code should use
module_exists('jquery_update') && version_compare(variable_get('jquery_update_jquery_version', 0), 1.7, '>=')
Comment #10
markhalliwellAlso need backport.
Comment #11
wundo CreditAttribution: wundo commentedNice catch! fixed.
Comment #12
wundo CreditAttribution: wundo commentedBackported to 7.x-2.x too.
Comment #13
markhalliwellComment #14
valkum CreditAttribution: valkum commentedComment #15
ShaunDychko CreditAttribution: ShaunDychko commentedjQuery 1.7+ caboshes the dropdown in Rules configuration, so I needed to add updated jQuery using hook_js_alter in the subtheme's template.php file, as shown:
But an error is still displayed on the theme settings page due to the following lines in ../theme/settings.inc
even though jQuery is just fine for the theme that's using Bootstrap. jquery_update shouldn't be a formal dependency of the Bootstrap theme since there are other ways of adding updated jQuery. I'm not sure how to query in the theme settings page for which jquery version is being used. Perhaps this error notice can be removed altogether in favour of a bold notice in the theme documentation to update jquery somehow, recommending the jquery_update module, but not requiring it as is currently being done.
I've attached a screenshot of the issue with Rules, using jquery_update with 1.7.
Comment #16
ShaunDychko CreditAttribution: ShaunDychko commentedComment #17
markhalliwellPerhaps we can add a "Suppress jQuery Warning" checkbox in the Advanced tab of the theme settings for things like this.
FWIW, the message says minimum jQuery 1.7, meaning the Rules dropdown would probably work with jQuery 1.8. Regardless, if there's something that isn't working in a module because of a jQuery versioning issue, it should be addressed in that issue. Something like... "Hey your module doesn't work with jQuery 1.7 (using jquery_update module)".
Also FWIW, I don't think we're going to get rid of this message, mainly due to the number of issues we get from people who actually don't read the documentation. This is an effort to help eliminate the confusion of why JavaScript doesn't work on just a plain install of this project.
Comment #18
markhalliwellAlso, please create new issues referencing the "fixed" issue (instead of re-opening). It helps track regressions and where/why code was introduced.