The readme has this:

The actually difference between the two
are quite subtle: Placement of the title is different, and the comment form
will not appear in the default view mode but it will appear in the full page
override.

Aside from the typo in the second word ;-), I'm still not clear on the exact differences between the two and could use a more detailed explanation. For example, how is the title placement different? Why is the comment form on one but not the other? Are there any other differences? And, most importantly, how do I know which is better to use in a given situation - are there examples of when one should be used versus the other?

The differences between different Panelizer displays.
Default
  • Purpose:
  • Scenarios under which it will be used:
  • Requires Page Manager: No
  • Will not be used if Page Manager is installed, the entity's display (e.g. node_view) is enabled, and "Full page override" is enabled.
  • Does not require anything to be enabled via the entity's display settings.
Full page override
  • Purpose:
    • A configuration for the standalone display of an entity, e.g. a node page or a taxonomy term page, that is dependent upon Page Manager.
  • Scenarios under which it will be used:
    • Page manager is enabled, the entity's main display is enabled in Page Manager (e.g. "node_view" for nodes), the Panelizer variant is higher than any other appropriate display variants for that entity display (e.g. there isn't a node display higher up the node_view list than Panelizer), the entity is panelized and the "Full page override" view mode is panelized.
  • Requires Page Manager: Yes
  • Requires the entity's "view" display, e.g. "node_view", be enabled in Page Manager.
  • Does not require anything to be enabled via the entity's display settings.
  • Does not get used when an entity is embedded elsewhere, e.g. via Views or an EntityReference.
  • Modifications to the title field take effect.
Full content
  • Purpose:
    • A configuration for the standalone display of an entity, e.g. a node page or a taxonomy term page, that does not use Page Manager.
    • Because it is triggered by a normal entity_view() call, it may be the display used when the entity is embedded in another entity.
  • Scenarios under which it will be used:
  • Requires Page Manager: No
  • Will not be used if Page Manager is installed, the entity's display (e.g. node_view) is enabled, and "Full page override" is enabled.
  • Requires the "Full content" view mode be enabled via the entity's display settings before it can be selected.
  • Is used when an entity is embedded elsewhere, e.g. via Views or an EntityReference, when the "Full content" view mode is selected.
  • Modifications to the title field do not effect anything.

Comments

miromarchi’s picture

miromarchi commented

subscribe

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: Difference between Default and Full Page Override? » Document differences between Default, Full Page Override and Full Content displays
Component: Documentation » User interface
Category: Support request » Task
Issue summary: View changes

And there's also the "Full content" display.

Lets turn this into something more productive.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Parent issue: » #2155813: Plan for Panelizer 7.x-3.2 release
kepford’s picture

kepford commented

The main differences I have seen are that "Full Page Override" allows you to disable the default node title and instead render it in a Panel pane. "Full Content" renders the node title as it would with a normal node display. "Full Page Override" allows you to use page manager node view page to control defaults.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes

I've started compiling details in the issue summary.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes
damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Issue summary: View changes
marvoey’s picture

marvoey commented

I may inaccurate, but I believe that these are tied to the entity view modes, which you can toggle on and off in the content type structure. Then you can change how the various fields are displayed i.e. format, label locations, hidden fields etc. What I found to be the most useful is with the image rendering. With entity view modes you can assign different image styles so your panelizer will display various entities differently. In addition, what appears in the content plugins will also vary based on these view modes.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Status: Active » Fixed

The changes I made in #2147795: Update UI / documentation to indicate view mode displays must be enabled before they can be Panelized should answer these questions.

Status: Fixed » Closed (fixed)

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

cmonnow’s picture

cmonnow commented

While I'm using an old version of Panelizer and I haven't read the latest info nor much into Panelizer in general I thought I should stress for Googlers that (I believe it might still be true) while node comments will appear if you add them to a "Default" Panelizer mode the corresponding pager will not function correctly (which may cause a lot of frustration). You need to set a Full Page Override.

It may appear to work on the surface when few node comments exist but once they exceed the comments per page settings as set in the original content type you'll notice that they can't move past the first "page". The ?page=1 GET variable (where 1 refers to comment page 2) won't do anything since the comments shown actually have a pager ID of 1 (and not the default of 0), meaning their pager $_GET request comes after a comma i.e. ?page=1,1 but this won't be reflected by the URLs of the unrelated pager below the comments.

muschpusch’s picture

muschpusch commented

The new/ upcoming readme explains this really well: #2151837: Update README.txt file

UTAN_dev’s picture

UTAN_dev commented

Kepford wrote:

The main differences I have seen are that "Full Page Override" allows you to disable the default node title and instead render it in a Panel pane. "Full Content" renders the node title as it would with a normal node display. "Full Page Override" allows you to use page manager node view page to control defaults.

Can you give a couple of scenarios showing why someone would use one or the other?

asghar’s picture

asghar commented

Here is my findings which might be help to others

Full page override

Description: Work for node detail page only.
Purpose: Alter the node title and content structure
Conditions: Node template must be enabled.
Precedence: 1

Full Content

Description: Work for node detail page and full content view mode. If Full page override is enabled then Full page override work for node detail page and Full Content will work for render as full content mode.
Purpose: Alter the node content only.
Conditions: Full content must be enabled.
Precedence: 2

Default

Description: Work for node detail page and full content view mode. If Full page override is enabled then Full page override work for node detail page and Default will work for render as full content mode.
Purpose: Alter the node content only.
Conditions: Full content must be disabled.
Precedence: 3

Low precedence value has high priority.