Flippy is a content type-specific plugin -- that is, it will only allow someone to page through nodes that belong to a specific content type. However, designers often use plugins like views or panels to place specific content type nodes in fixed places on a page -- for example, creating a block view that places the most recent node of a content type in a specific area on the front page.
When a designer uses a view to display a node, Flippy will not display in that node. This works at cross-purposes: Flippy's advantage is it lets visitors page through the archives of a specific content type, but that advantage is not present when a view is used to make that content type accessible on a given page (front page, subsection, etc.)
The specific request is to modify Flippy so that if a view (or, for example, a panel area) is configured to display a block containing a content type node that uses Flippy, Flippy will display the appropriate pagers.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | Screen Shot 2012-10-17 at 12.01.58 AM.png | 90.18 KB | quinns |
Comments
Comment #1
cluke009 commentedI am not sure about views but I am currently using flippy with panels by overriding the "node_view" template. Maybe that will work for you as well.
Comment #2
ubersoft commentedHow do you override the node_view template? I'd like to try that.
Comment #3
BeaPower commentedsame here, how?
Comment #4
quinns commentedWhen using panels, there is a "pager" element available in the "Node" section of panel options. See attached example.
Comment #5
fadecomic commentedI posted a workaround here: http://drupal.org/node/1928372
Comment #6
jacqueschoquette commentedI am not seeing the pager element in the node section of my panel options as per quinns screen shot? Any idea why it's not showing up for me?
Comment #7
avillian commentedHey guys just make sure you clear cache in Drupal Configuration -- Performance -- Clear Cache and the Pager should show up in Drupal Panels currently using Panels 7.x-3.3 and Flippy 7.x-1.0.
Cheers.
Comment #8
grevil commentedThe Drupal 7 branch will only get bug / security fixes. As of the D7 issue smashing initiative in #3309846: Check and sort out old Drupal 7 issues, I will close this issue.