I've noticed

$variables['no_panels'] = !(module_exists('page_manager') && page_manager_get_current_page());

in template.php that seems to result in a node panelizer page defining no_panels as True. This means the content region doesnt have the container class, and the content goes right to the edge. Is this intended? Ideally I would expect a panelizer page to be considered a panels layout :)

Comments

pirog’s picture

pirog commented
Status: Active » Needs work

This seems to be working correctly and adding containers to panelized entities... can you give me some more info here?

mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented
Version: 7.x-3.0-rc2 » 7.x-3.x-dev
Component: User interface » Code
Category: Support request » Bug report
Status: Needs work » Active

There's no patch...so setting to active.

We have this occurring where $no_panels is incorrect on Panelizer nodes. It's adding containers incorrectly. I'll see if I can get our theme developer to post more details here.

JakeWilund’s picture

JakeWilund commented

Line 203 of page.tpl.php includes $no_panels, but due to $no_panels missing panelizer panels, the Bootstrap container class is being applied to #content of panelized nodes. This is causing nested .container classes, and thus, display issues.

<div id="content" class="column <?php $no_panels ? print 'container' : ''; ?>">
  <?php print render($page['content']); ?>
</div> <!-- /.section, /#content -->
pirog’s picture

pirog commented

Hey there! We are actually trying out a new workflow for Kalatheme on github. We encourage you to post your issue there and submit a pull request!
https://github.com/drupalprojects/kalatheme