Needs review
Project:
Previous/Next API
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
4 May 2013 at 22:11 UTC
Updated:
7 Aug 2014 at 13:44 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #1
holdmann commentedDirty patch included.
Comment #2
johnish commentedI used this patch. It wouldn't automatically apply so I did it manually and so far the testing is looking good.
Comment #3
johnish commentedComment #4
johnish commentedI found that if the term id wasn't chosen for the piece of content then this fails.
Category ID is empty here and causes no nodes to be indexed and quit with a MySQL error.
Comment #5
johnish commentedHere's the code that I used to fixed the category_id is empty condition.
Attaching the git patch file.
Comment #6
johnish commentedComment #7
johnish commentedrerolled this patch
Comment #8
johnish commentedComment #9
johnish commentedComment #10
bhosmer commentedI'm testing this patch now, there is an extra
}on line 551 in the patch. Here is a new one that fixes it.Comment #11
bhosmer commentedI'm marking this as needs work.
It works as designed for some nodes, but node for others.
I get the same node for previous/next on some nodes.
Here is a sample of the
prev_next_nodetable:Steps to reproduce:
Some will show properly, but others will have previous/next nodes that aren't in sequence and the previous/next link will be the same node.
Comment #12
bhosmer commentedThis updates builds upon the previous patches and integrates taxonomy indexing.
It also separates some of the code into include files, and adds documentation for some of the custom functions.
Please review and test.
Comment #13
bhosmer commentedThis patch doesn't cover node deletion properly. Marking back to needs work.
Comment #14
bhosmer commentedI've incorporated the patch from xumepadismal, #1372754, that updates the index properly when deleting a node that seems to have solved the deletion problem in #12.
Comment #15
bhosmer commentedThis patch fixes improper indexing of existing nodes and fixes the modification of the nodes that pointed to the last node as well.