I have a view, with "page_1", "page_2", and "page_3". If I want to point the pager at "page_2", how would I do that?

CommentFileSizeAuthor
#8 custom_pagers-views_display-554210-8.patch1.98 KBphenaproxima
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Marko B’s picture

Marko B CreditAttribution: Marko B commented

I want to ask the same question. Is it possible to refernce specific display in view or does it only use default view?

kruser’s picture

kruser CreditAttribution: kruser commented
Title: Use a specific page within a view? » Select which display within a view?

I have the same question - in a view with multiple display, how do you choose which one custom pagers uses? Is it using Default by default?

nonsenz’s picture

nonsenz CreditAttribution: nonsenz commented

+1

mattcasey’s picture

mattcasey CreditAttribution: mattcasey commented

In the dev version at least, Custom Pagers is using its own display which is hidden from the Views UI

bchristensen’s picture

bchristensen CreditAttribution: bchristensen commented

Which display is Custom Pager's own display based on? I have a view with multiple displays, each of which pulls in a different set of nodes, and selecting this view doesn't seem to be working for me.

13rac1’s picture

13rac1 CreditAttribution: 13rac1 commented

It is based on the master View. I suggest you make a new view for your pager.

mkmaroon’s picture

mkmaroon CreditAttribution: mkmaroon commented

I also would like to request this, to be able to select specific displays within a view, this would help me, at least, for my particular scenario, tremendously.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima commented
FileSize
custom_pagers-views_display-554210-8.patch1.98 KB

I have wanted this functionality for a long time, and I find the requirement to use the Master display incredibly inconvenient and conducive to having too many views kicking around just to appease this weirdness on custom_pagers' part. So I wrote a quick patch - this was written for Custom Pagers 7.x-1.x-dev, but it shouldn't be too difficult to backport to 6.x.

This patch does two things:

1. It modifies the pager editing form so that the View select list is divided up into optgroups by view, and the actual options are the individual displays which use fields.
2. When actually building the pager, overridden options from the source display are cloned into the special display that custom_pagers creates programmatically. This only happens if the source display is NOT the master display.

P.S. This is my first time using the "official" patching method (with git and all), so please accept my apologies if I screwed up the patch-making process.

phenaproxima’s picture

phenaproxima
he/him
Primary language English
Location Massachusetts
CreditAttribution: phenaproxima commented

Regarding my patch in #8 - for reasons I can't yet explain, line 43 in custom_pagers.views.inc breaks the patch:

'uses fields' => FALSE,

The solution is to change 'uses fields' to TRUE. Just in case the first person to try this patch wonders why the hell it's not working.

squarecandy’s picture

squarecandy CreditAttribution: squarecandy commented

Thank you so much phenaproxima - this module was not working at all for me in the 7.x branch until I applied these changes.
All good now...

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

The patch didn't work for me. I get duplicate pagers on the default view and displays ok on "page_1" . Although the key has shows "0" instead of the correct number of products.

I had these patches applied to it prior. Will this have anything to do with this?

https://drupal.org/node/1288368#comment-8493605