Hello, all--

Preface: I know that I should use [id://###] and not [node://###] to refer to a node, but I occasionally forget. (I always know that only one is correct, but I keep misremembering which one it is.) I had always found that one works--until today.

Anyway, the oddity is this: I used the wrong one (node) on both Re^5: Split process->check ->and run Parallel and Re^3: UnixDate - getting a different date. For Re^5: Split process->check ->and run Parallel it worked just fine (as usual), but for Re^3: UnixDate - getting a different date it renders as [node:// 732632|your question]. Since node is clearly incorrect, I'm not reporting it as a bug. But I am curious why it worked differently in the two nodes.

...roboticus

Replies are listed 'Best First'.
Re: id vs. node oddity
by jdporter (Paladin) on Dec 24, 2008 at 19:56 UTC

    It shouldn't be that hard to remember: if you're specifying a numeric node ID, use id. As in the URL: /?node_id=43037. Node IDs are numeric. Otherwise, it's like giving the title of a node, as in the URL: /?node=What shortcuts can I use for linking to other information? If you ever pay attention to URLs, it should be fairly clear that node_id= is used when the criterion is a numeric node ID, and that node= is used when searching by title. But perhaps more to the point is that node:// is not documented and not supported, so no one should ever use it. Even so, some people have really got it in their heads. I'm looking at you, kennethk, Bloodnok, TGI, repellent, broomduster, pc88mxer, apl, oko1, pileofrogs, Herkum... ;-)

    I always know that only one is correct, but I keep misremembering which one it is.

    Um... Writeup Formatting Tips is prominently linked below each post form textarea, and that in turn links to What shortcuts can I use for linking to other information?. If that's not convenient enough, you could drop a link to What shortcuts can I use for linking to other information? in your Personal Nodelet or whatever.

    I see you've discussed this topic in the past...

    Between the mind which plans and the hands which build, there must be a mediator... and this mediator must be the heart.
[reply]
[d/l]
[select]
      jdporter:

      I know it shouldn't be hard to remember. The problem isn't that I didn't remember, but that I remembered incorrecty--I thought I knew the right one, but didn't. If I had any doubts, I'd've looked it up. I now have it on a sticky on my monitor to prompt me to use the correct one in the future (unless, of course, I ignore the sticky.)

      ...roboticus
[reply]
Re: id vs. node oddity
by Anonymous Monk on Dec 24, 2008 at 16:44 UTC
    because the pmdev who added code for that didn't do it right? or a previous filter modifies it? Lets see, testing
    <code> [id://732478] ([id://732478])
    id vs. node oddity (id vs. node oddity)
    [id://732478] ([id://732478])
    id vs. node oddity (id vs. node oddity)
    [id://732478|node] ([id://732478|node])

    Update: By the way, I think you wanted to use <code> tags for (your question) your question, rather than <center>. You might go back to your node and fix it...

    <p><b>Update:</b> By the way, I think you wanted to use &lt;code&gt; tags for ([id://732632|your question]) [id://732632|your question], rather than &lt;center&gt;.  You might go back to your node and fix it...</p> Hmm is it the words your question? Lets see your question and Zombie ydrol

    Nope, after careful testing, it seems intermittent, which means it probably has to do with the database and/or node cache, and failing to return that one node, so what you get back is just the text, which is apparently the default thing to do (i cant verify this).

[reply]
[d/l]
[select]
[reply]
[d/l]
[select]

Back to Perl Monks Discussion