I'm using my site's default theme as the administrative theme. Every time I try to save the configuration for a menu block, it reports an error:
An illegal choice has been detected. Please contact the site administrator.
In fact, the interface in general seems to be broken. When the block config page is first loaded, and advanced options is already selected, selecting basic options causes the form to collapse on itself as you would expect. However, selecting advanced options again does not expose the advanced options.
When I specify a different theme to be the administrative theme, everything works fine though, which makes me think it's an issue with my theme, though I can't imagine what would be causing it the conflict. I am using the Twitter Bootstrap JavaScript file, and that is the only script file that my theme references.
Comment | File | Size | Author |
---|---|---|---|
#4 | 2013 09 19 menu_block not clear on valid setup options.png | 158.74 KB | therobyouknow |
Comments
Comment #1
lpeabody CreditAttribution: lpeabody commentedI can confirm that the Twitter Bootstrap JavaScript file breaks the menu block configuration interface.
Comment #2
JohnAlbinComment #3
JohnAlbinComment #4
therobyouknow CreditAttribution: therobyouknow commentedConfirming the same problem, using Bootstrap (to be precise our subtheme of it) - see screenshot:
Comment #5
therobyouknow CreditAttribution: therobyouknow commentedThis work around worked for me (doesn't fix problem, but gets your menu block saved):
By attempting saving the block in step 2, this results in the form being return with the options reset in step 3 so that the second save block in step 5 can be achieved successfully.
I might suspect that this specific bootstrap issue might be the extra amount of markup, divs, that are breaking the jquery; similar issue in autocomplete_deluxe widget, in that situation, a remedy was to remove amount of nesting - https://drupal.org/node/1944436#comment-7858151
If this can be done for menu_block admin here, it might also solve the problem here, perhaps
Comment #6
JohnAlbinSorry for not responding sooner!