When you enable front-end editing of blocks, aloha copy's all html in that block when you save. So, contextual links are also copied.
This should be filterd some how if contextual module from drupal core is enabled.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | Screen Shot 2012-03-13 at 13.23.06.png | 319.58 KB | muhleder |
Comments
Comment #1
muhleder commentedOn my copy (using omega theme) the contextual links are not in the same block as the content. Perhaps your theme doesn't make the separation between block links and content?
The place to fix this would be in the module's aloha.js
Somewhere in
we could add another line which removes any known tags we don't want to be added to the content. I've got a feeling this should be initialised as a setting something like
Drupal.settings.aloha.removedTags = ['.contextual-links']
so that site builders can add to this setting if they have other tags that also need to be stripped.
Comment #2
Frederic wbase commentedYes indeed, it would be wunderfull if this is an extra setting. For the moment i will seperate the contextual links from the content area so that the problem is solved for the moment.
Our themer just loves a clean html output. Thats why we removed the extra divs (btw, we use boilerplate based theme)
Comment #3
muhleder commentedOk, have just pushed an update which should enable this. From the documentation added to the README
Bit annoying having to add a new namespace within settings, but if we tried to use something like Drupal.settings.aloha.elementsToStrip then it gets zapped when the module adds the aloha settings. So in order to keep the code visible within the js file we need to add a new namespace.
If you could check whether this works for you with your original theme that would be great. Should be available from git now, and from the dev tarball after the next packaging.
Comment #4
Frederic wbase commentedWow, thanks for the quick respone and fix an this one!
I will test is this afternoon and report my feedback in this issue.
grts
fre
Comment #5
muhleder commentedMarking this one as fixed. Please reopen if you are still experiencing issues with the latest release.
Comment #6
Frederic wbase commentedIts seems to be fixed now, thanks m8!