I can't order the field list, as you see the attach image. When I debug with js, the process can't go to drupal ajax js, even misc/ajax.js or bootstrap/js/misc/ajax.js. So the page can't send request to system/ajax.

Comments

bdanin’s picture

I am also having this problem. Additionally, the vertical tabs in Display suite aren't showing up properly. When I convert my admin theme to seven, the problems go away. Also, I did not have this problem with Bootstrap-2.x so it's specific to this release.

bdanin’s picture

I haven't been able to figure out what the problem is, but using display suite, I cannot change any of the field orders, because ajax or jquery stall. Ultimately, I cannot move fields from hidden to other zones unless I turn off javascript and manually make those changes without .js

Anyway, here is a hacked-together solution that allows me to keep using Bootstrap 3.x, and then fail-back to seven for when I need to work with display suite (I don't seem to have problems elsewhere, so I'm not too concerned, but this does need to be fixed):
1) enable theme seven
2) install and enable page_theme (https://drupal.org/project/page_theme)
3) add seven, and tell it to display on this path: admin/structure/types/manage/*/display*

One note, I'm using bootstrap-sass (see: https://drupal.org/node/2116345), so I haven't yet had a chance to test this using LESS to see if that's part of the problem or not.

mkhamash’s picture

Status: Active » Needs review
StatusFileSize
new981 bytes

The problem is that bootstrap_button theme function is turning all input submit to button, in the case of draggable table there is an input id=#edit-refresh that fire the ajax update.

for more information on look at AJAXRefreshRows in Drupal field_ui.js file.

mkhamash’s picture

StatusFileSize
new979 bytes

Sorry, there was an extra whitespace in the patch "1 line adds whitespace errors", re-uploaded.

markhalliwell’s picture

Title: Bootstrap for admin theme has a problem with field ui or ajax » Core JavaScript expects buttons to be input elements
Version: 7.x-3.0 » 7.x-3.x-dev
Status: Needs review » Fixed
Related issues: +#2120849: Decrease Panels IPE CSS & JS specificity to allow "button" elements

Actually the issues lies with the JavaScript. This project should not make exceptions for the "button" element. Normally the offending module should be patched (see related issue about Panels), but this is for core and considering it's fixed for 8.x (can't seem to find that issue ATM, but it is), I doubt it will get backported to 7.x.

Committed 4fede42 to 7.x-3.x:

Issue #2162789 by Mark Carver, mkhamash | quanvm: Core JavaScript expects buttons to be input elements.

bdanin’s picture

patch in #4 seems to fix this issue for me

markhalliwell’s picture

The patch in #4 will not be applied. I have already committed the fix in #5.

bdanin’s picture

when I tried to pull down latest dev branch using drush, it erred:

File bootstrap-7.x-3.x-dev.tar.gz_date=1392651805 is corrupt (wrong md5 checksum). [error]

Also, note that the patch in #4 causes problems in places, specifically in views, the "apply" button disappears

markhalliwell’s picture

If you click on the commit hash link in #5, it will take you to drupalcode.org where you can then download the patch against the repo

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

  • Commit 4fede42 on 7.x-3.x, 8.x-3.x by Mark Carver:
    Issue #2162789 by Mark Carver, mkhamash | quanvm: Core JavaScript...
ryan.armstrong’s picture

Version: 7.x-3.x-dev » 8.x-3.x-dev
Assigned: Unassigned » ryan.armstrong
Status: Closed (fixed) » Needs review

Moving this to the 8.x-3.x branch as it has been committed to that branch. Making sure the fix gets tested in the Drupal 8 release.

  • Mark Carver committed 4fede42 on 8.x-3.x.x
    Issue #2162789 by Mark Carver, mkhamash | quanvm: Core JavaScript...
markhalliwell’s picture

Version: 8.x-3.x-dev » 7.x-3.x-dev
Assigned: ryan.armstrong » Unassigned
Status: Needs review » Closed (fixed)

I'm just moving this back to 7.x. If this needs re-evaluation in 8.x, create a new issue.