A question that might be best answered by merlinofchaos: is there a specific reason to use a Panelizer default configuration rather than a Panels node_view configuration? Another way of considering it - why are there two separate ways of doing this rather than Panelizer just inheriting from the Panels node_view configuration, or using Panelizer's default as an alternative path to the node_view configuration?

Comments

What is a node_view configuration?

I updated the issue to clarify I was discussing the Panels node_view system.

I'm still not understanding what you're asking.

i think he means Panelizer panel config vs Panels node view variant,

in that maybe Panelizer could instead use Node View variant supplied as optional default/optional configs, along with custom config built by the user on the moment. i've thought on this before.

example,
A -> content type page
B -> content type blog
C -> content type forum

Panels node view:
- default variant A0 [enabled], weight=1
- optional variant A1 [enabled], weight=2
- optional variant A2 [enabled], weight=3
- optional variant A3 [enabled], weight=4
- optional variant A4 [disabled], weight=5
- optional variant A5 [disabled], weight=6
- default variant B0 [enabled], weight=1
- optional variant B1 [enabled], weight=2
- optional variant B2 [disabled], weight=3
- optional variant B3 [disabled], weight=4
- optional variant B4 [disabled], weight=5
- default variant C0 [enabled], weight=1

Panelizer config (select which node_view variants for each content type):
- content type A (page): check A0 + A1 + A2 + A3 + A4[disabled] + A5[disabled] + custom config
- content type B (blog): check A0 + B1 + B2[disabled] + B3[disabled] + B4[disabled]
- content type B (forum): check C0

results:
- when creating a page, the user would have a default variant available, as well as optional variant A1, A2 and A3, plus option to create custom config. remaining variants are disabled at node view;
- when creating a blog, the user would have a default variant available, as well as optional variant B1. remaining variants are disabled at node view, including custom config;
- when creating a forum, the user would have a default variant available. remaining variants are disabled at node view, including custom config;

default variant could be set with the weight, or manually at Panelizer.

Title:Panelizer default configuration, or node_view configuration?Panelizer configuration vs Panels node_view variants?
Version:7.x-1.x-dev» 6.x-1.x-dev
Component:Miscellaneous» Code
Category:support» feature

changed title/etc

Version:6.x-1.x-dev» 7.x-1.x-dev

I think this issue at least partly solves my problem: #1290452: Make Panelizer show after the other Page Manager handlers

Status:Active» Closed (duplicate)

Category:feature» support
Status:Closed (duplicate)» Active

Now that #1268902: Selection rule doesn't seem to be a selection rule solves a bug (that I thought was a feature X-) ) there are two different ways to define the default for a specific content type. This brings up a question that should be answered in the README.txt file and project page: is it better to use the Panels node_view variants with a selection rule filtered to a specific content type, or in Panelizer assign a default for the content type?

Status:Active» Fixed

Well. Panelizer is used primarily if you want to allow individual nodes to have their own layouts, something node_view can't do. So I think the decision hinges largely on that.

Also, you have to throw display suite into the mix as well, which is like node_view but using the field ui and use panel layouts and content for massive awesome.

The main difference between the three approaches involves how the administrators make changes. So you want to pick the method that will be the easiest to train.

Status:Fixed» Closed (fixed)

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

Merlin, sorry to bother,
i'm writing / counseling on this topic.

You think Panels node_view, user_view, term_view, along with Panel Nodes, will end up being phased out in favor of Panelizer?

Not entirely. There are some things you an do with node_view, et al, that you can't do with Panelizer, particularly if you want to select based on things like taxonomy terms. Also, the way term_view works, for example, some things are rendered outside of the entity_view, so the term_view is needed if you want to change that behavior.

Any time you use the 'page_manager' view mode, that view mode is being rendered with one of those modes. I think these will be kept, but we will counsel people not to use them unless they have really advanced needs, or very very simple needs and Panelizer ends up being too much to deal with.

Issue summary:View changes

Clarification that I was discussing Panelizer vs Panels.