Steps to Reproduce:
1. Install the Pager module and configure it for a specific content type
2. Create a node manually in the chosen content type.
• Confirm that the node appears in the Prev/Next navigation links of the Pager block.
3. Use the Replicate module (or another cloning mechanism) to create a copy of the existing node.
• The replicated node receives a unique Node ID and is published.
4. View the Pager navigation:
• The manually created node is present in the Pager.
• The replicated node does not appear in the Prev/Next links, despite meeting all the Pager block’s configuration criteria.
Expected Behavior:
Both manually created and replicated nodes should appear in the Pager navigation, provided they meet the module’s configuration settings (e.g., content type, taxonomy terms, etc.).
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Archive1.zip | 5.84 KB | nick pasiuk |
| #4 | Archive.zip | 5.62 KB | nick pasiuk |
Comments
Comment #2
bkelly commentedHi Nick -
I'm guessing it's caching or timestamp issue.
I'll look into it.
-- Bill Kelly
Comment #3
nick pasiuk commentedYeah, it's because of the same timestamp of the original node and replicated node. I improved this locally by adding an additional check of the node ID. Also, it's nice to have taxonomy terms not required in case you just need to have filtration by CT.
Comment #4
nick pasiuk commentedHere is an updated version, it may be helpful.
Comment #5
nick pasiuk commentedHere is also the updated version with non-required taxonomy terms and a fix for replicated pages.
Comment #7
bkelly commentedHi Nick -
Looks great!
I've created the 3.0.1-alpha1 release.
I'm going to look into the second archive.
Thanks you for your time.
-- Bill Kelly