Panels: 7.x-3.3
Panelizer: 7.x-2.0
Ctools: 7.x-1.2
Page Manager: node_view page enabled

I enabled panelizer and went to the panelizer configuration page (admin/config/content/panelizer) to panelize one of my node types. However when I selected a node-type and hit 'save' I was greeted with the following message:

"The user template page is currently not enabled in page manager. You must enable this for Panelizer to be able to panelize users."

If I go to page manager and enable the user_view page then I'm able to panelize a node-type, however I found this confusing since I'm attempting to panelize a node-type and not the user.

Comments

caschbre’s picture

caschbre commented

FYI... my work-around is to enable the user_view page, make my panelizer config changes, then disable the user_view page.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

That warning was just a superficial notice and didn't affect your ability to do things, so enabling/disabling the user view was not necessary.

That said, the warnings had not been properly updated for the change to view modes. I updated the code, and now it will correctly only warn you if you attempt to enable the "Full page override" view mode for objects that need it.

r2integrated’s picture

r2integrated commented
Version: 7.x-3.0-rc1 » 7.x-3.0
Status: Fixed » Needs work

Looks like this warning is showing up in admin/reports/status as well because panelizer_requirements needs updating. Let me know if I should make this into a separate issue.

I was going to patch this but it looks like it's a bit more complicated than I can tackle right this moment. The issue is that the fix applied to the form validation function is in the definitions for the PaneliserEntity classes and makes use of instance variables that wouldn't be available in the hook_requirements implementation.

merlinofchaos’s picture

merlinofchaos commented

You know, I think that check can be completely removed now; the dependency on page manager is *much* less now, and I don't think that warning is as meaningful there.

merlinofchaos’s picture

merlinofchaos commented

And it should probably be a separate issue, indeed.

r2integrated’s picture

r2integrated commented

Submitted patch in separate issue.

http://drupal.org/node/1909820#comment-7034384

merlinofchaos’s picture

merlinofchaos commented
Status: Needs work » Fixed

Moving back to fixed with a separate issue.

Thanks!

Status: Fixed » Closed (fixed)

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