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.
Using the base Omega 7.x-3.0 theme, I have a Panel page set as the homepage (latest dev branch of Panels) and using the Contextual module with D 7.7. When I'm on the homepage the page body is wrapped in <div class="contextual-links-region">
, and the contetxual menu ends up showing over the system messages block. Here's the relevant output:
<div id="zone-content-wrapper" class="zone-wrapper zone-content-wrapper clearfix">
<div id="zone-content" class="zone zone-content clearfix container-12">
<div id="messages" class="grid-12">messages</div>
<aside class="grid-3 region region-sidebar-first" id="region-sidebar-first"></aside>
<div class="contextual-links-region">
<div class="panel-display omega-12-twocol-9-3" id="homepage">page content..</div>
<div class="contextual-links-wrapper contextual-links-processed">links..</div>
</div>
<aside class="grid-3 region region-sidebar-second" id="region-sidebar-second"></aside>
</div>
</div>
See attached for where the contextual menu ends up
Comment | File | Size | Author |
---|---|---|---|
omega-contextual-displaced.png | 40.13 KB | DamienMcKenna |
Comments
Comment #1
DamienMcKennaComment #2
marcoka CreditAttribution: marcoka commentedhm could you check what omega is messing up in the css?
Comment #3
marcoka CreditAttribution: marcoka commentedComment #4
himerus CreditAttribution: himerus commentedI'm not sure what/how to fix this issue... I "think" the CORE CSS is actually placing the data at the top right of whatever contextual link container, which in this case (not sure if it is correct) is the ENTIRE content region, which seems wrong, since many items can appear in the region (obviously)
Not sure of a solution on this one.
Comment #5
mist CreditAttribution: mist commentedSame here
the #region-below-content is above all other divs in zone.
Comment #6
kay_v CreditAttribution: kay_v commented@flo81 noted a potential solution in a related issue discussion on drupalcommerce.org:
Not sure if this solution has other implications, but at the moment it looks reasonable to me. Noting it here in case it's of use to other folks.