Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Using entity_embed with a Bootstrapped derived theme breaks the AJAX handling. Switching back to Seven, it works again. No errors are generated, so I'm not able to figure out what's going on.
| Comment | File | Size | Author |
|---|
Comments
Comment #2
seanrComment #3
StevenWill commentedNot sure if this is the same issue, but when I try to add a image to a image field using the entity Image browser I get a cache error. If I change the admin theme to use seven to error goes away and the image is added to the field.
Comment #4
markhalliwellI'm tempted to say this is a bug with entity_embed since its likely not using theme independent selectors in its JS. A module should be able to work in any theme.
Comment #5
markhalliwellP.S. using a core theme isn't a very good basis to test whether or not it's another theme's "fault". If anything, it just means that the module in question likely based it off markup that was present in those themes, which is very bad practice. A module should implement it's own selectors/data attributes that it knows will be there regardless if other classes or markup changes.
Comment #6
slashrsm commentedWould be great to have more info for reproduction (theme that is used, steps to get to the AJAX error, ...).
Comment #7
dave reidIs it possible this would be fixed by #2778355: TypeError: Drupal.theme.bootstrapModal is not a function?
Comment #8
seanr@Dave Reid, no, I don't get that error. However, I do note that if I disable the Bootstrap modal stuff, it starts working again.
Comment #9
rachel_norfolkI think I am seeing behaviour that sounds related.
So, I have an entity_embed button and, on the second stage of the embedding form, I couldn't understand why I was only seeing a "Next" button but not the "Back" and "Embed" buttons that are created by the entity_embed module.
Seems, when I use the admin account AND the bootstrap subtheme, I CAN see the buttons and they work correctly but the are in the main content of the form not the footer of the modal. See images
entity_embed:
entity_embed with an admin account:
Now - we can see that the buttons are not being moved into the footer. Not even sure where the extra "next" button is coming from at all yet...
Comment #10
rachel_norfolkA little more digging shows that the buttons ARE on the form but set, via css, to zero size.
Interestingly, this time I opened an embedded entity that I had already put onto the page and the footer did contain the buttons. It's as though they cannot be determined when the modal is made during creation but are there on reopening. So, once I remove the css zero-ing the buttons, I have two sets!
Erm - just making buttons zero size has to be a TERRIBLE accessibility solution, doesn't it????
Comment #11
rachel_norfolkBringing this back to Bootstrap - the entity_embed js that does exist isn't related to this issue, it seems.
Comment #12
dave reidYeah, I'm guessing this might be more related to #2826277: Rework/update dialog JavaScripts
Comment #13
dave reidActually it looks like #2838190: Fake modal buttons in footer aren't being replaced during AJAX update is the actual issue.
Comment #14
dave reidI'm going to go ahead and close this as a duplicate of #2800221: Breaks entity_embed AJAX since it's definitely the bug at play here with Entity Embed, with more details.
Comment #15
rachel_norfolkYeah - I'm happy with that
Comment #16
rachel_norfolk