Make it obvious who controls the layout

Page Manager offers a contextual link if a panel is utilizing a page. I don't know that there's anything else that can be offered. What Panels does is completely unrelated to content types, so sending links there wouldn't make any sense at all.

After using panelizer successfully on several sites, I understand what Isolesen is talking about. Especially regarding the panelized "node/%node"s, it's easy to lose track of which nodes are panelized and which aren't (across your site). Is there some overview list or something?

It would be so useful to have a filterable and sortable administrative overview page of all panelized nodes, so you could see which ones have which settings.

Even better if there was a way to (panelize/choose layout/revert) in bulk, like VBO.

There is pretty extensive views integration of Panels in the latest 2.x -dev (probably not in a release yet).

In Panelizer 3.x, there is now a panelizer overview page that makes it much easier to determine if the entity is panelized and if it's a local or global panelizer.

Also, Panelizer now has tabs in the actual bundle config (i.e, in the same location as 'manage display') that makes it easier to see the global panelizer configuration for the bundle. I think that's about as good as we can make this.

What would be your thoughts on overriding the default admin/structure/types/manage/CONTENT_TYPE/display/VIEW_MODE page provided by Drupal to indicate "This view mode is being controlled by Panelizer. Click here to modify it's configuration".

This is how Display Suite handled the problem (http://drupal.org/files/images/panel-edit.png) because it helps to prevent the confusion that comes about where you change settings on the standard "Manage display" page and don't see any changes because Panelizer overrides them.

What's interesting is that the page is still relevant. If you use the "Node content" pane for that view mode inside that view mode, it will still pass through and show you those fields.

Maybe putting in some kind of message, though, might be a good idea, to let people know that Panelizer has control of the view mode.

Good point around #10 which will effect how "Full Page Override" works, however for the standard view modes (default, teaser, etc) if Panelizer is managing the view mode the field UI wont have any effect as far as I can tell. How about for this issue we just keep it simple. How would you feel about a patch that replaced the Field UI controls in cases where that View Mode is explicitly managed by Panelizer with this language:

The display settings for this view mode are being managed by Panelizer. Visit the Panelizer settings page to change the configuration for this view mode.

Actually it's true in any view mode. You can panelize the view mode, and then add the node: content pane for that view mode and get the fields as they are configured. Perhaps that is silly but you can, in fact, do that. (Only with the -dev, though; if you try to do that with -rc1 it will crash due to a recursion problem).

This might require a separate issue, but I don't see the logic here. If I use Panelizer to control the view mode for a particular view mode (say the teaser), why wouldn't I expect that Panelized version to show up *everywhere* that view mode is used?

Would you be OK with a solution that made the "Rendered Entity" use the Panelized view as well? Then we could replace the Field UI (similar to how DS use to do) with the proposal from #11.

Because if you use the view mode inside the view mode, you'd get an infinite loop. At some point we have to fall back on default behavior.