Closed (fixed)
Project:
Freelinking
Version:
6.x-3.4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Aug 2011 at 04:22 UTC
Updated:
22 Oct 2014 at 11:44 UTC
Jump to comment: Most recent
If you restrict your nodetitle search to a specific content type, you end up with no titles ever working, because of a logic error in the nodetitle plugin. In a similar (but unrelated) logic error, the nodetitle plugin ignores the title text you specify and always uses the node title. The attached patch fixes both issues.
| Comment | File | Size | Author |
|---|---|---|---|
| fl_nt.patch | 755 bytes | pje |
Comments
Comment #1
morenstratThe first hunk of the patch made it to version 3.2. The second hunk however didn't. The described problem persists.
Comment #2
pje commentedUnfortunately, another part of the change to 3.2 puts back in the same problem for me:
// construct values for link
- $title = $target['text'] ? $target['text'] : $target['dest'];
+ $title = $target['text'] ? $target['text'] : $node->title;
The above change turns nice inline links that reference [[a page here]] into "A Page Here", which disrupts the capitalization of the sentence the link is contained. So, even though part of my patch was included, the hunk above effectively reverts it, as I must *still* write "[[a page here|a page here]]" in order to get the desired behavior.
So I had to revert the above part of the change in order to get back to the desired state, which is to allow users to mark up terms in existing sentences on wiki pages, without having to double the text to get the desired capitalization. (That is, simply adding the brackets around a piece of text should not alter the text, but rather, just make that text a link.)
Comment #3
rsvelko commentedsee here - http://drupal.org/node/1688000
I've reinvented the 2nd hunk from above fix and its working nicely on a 3.2 install.. maybe the screw up from above happened after 3.2 in dev ?
Comment #4
gisleNone of the code this patch touches is left. This has been fixed in 6.x-3.4.