I'm testing out rc2 (pretty slick!) but am getting the following error anytime I try to panelize the content (ex /node/1/panelizer/default/content)

Fatal error: Call to undefined function panels_get_layouts() in /Users/gusaus/Sites/panopoly/panopoly-7.x-1.0-rc2/profiles/panopoly/modules/contrib/panels/includes/common.inc on line 480

Assuming this is a panopoly issue 'cuz it was working on previous releases.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ericras’s picture

I can confirm. I modified with module_load_include as follows:

function panels_common_get_allowed_layouts($module_name) {
  module_load_include('inc', 'panels', 'includes/plugins');
  $available_layouts = panels_get_layouts();
beeradb’s picture

Project: Panopoly » Panels
Version: 7.x-1.0-rc2 » 7.x-3.x-dev
FileSize
506 bytes

Moving to the panels queue.

I was able to reproduce this issue with just the 3.x issues of Panelizer and Panels installed independently of Panopoly. The attached patch does indeed fix the issue.

BenK’s picture

I've just tested the patch in #2 and it works well for me... the issue is solved.

--Ben

Letharion’s picture

Assigned: Unassigned » merlinofchaos
Status: Active » Needs review
merlinofchaos’s picture

This is panels. We use ctools_include, not module_load_include().

In this case, ctools_include('plugins', 'panels')

populist’s picture

FileSize
485 bytes

Here is a patch which switches the code inclusion to ctools_include().

Anonymous’s picture

successfully patched. thanks

beeradb’s picture

Status: Needs review » Reviewed & tested by the community

I kind of feel dumb for not thinking about using ctools_include. I should know better by now :)

Either way, patch in #6 fixes for me. It's a fairly trivial fix, so going ahead and moving to RBTC.

gusaus’s picture

Tested and works for me. Thanks all!

merlinofchaos’s picture

Status: Reviewed & tested by the community » Fixed

Committed and pushed.

merlinofchaos’s picture

Committed and pushed.

Status: Fixed » Closed (fixed)

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