WordPress.org

Ready to get started?Download WordPress

Forums

Conflicting instructions for multiple trackbacks (4 posts)

  1. scoobyfoo
    Member
    Posted 8 years ago #

    When writing a new post, right above the box for inserting trackback URIs it says:

    Separate multiple URIs with spaces.

    But when I look at the help page (http://wordpress.org/docs/reference/post/#trackback), it says:

    Trackback an URL
    This sends trackback pings to the URLs you specify in this field. You can trackback multiple URLs by separating them with commas. Whitespace between things is insignificant. For more information about Trackbacks see Trackback explained. (Which doesn't exist yet.)

    I got to the above link from the bookmarklet help link. Is the information in the above link outdated? Which is the correct way to insert multiple trackback URIs?

  2. Mark (podz)
    Support Maven
    Posted 8 years ago #

    Neither - both seem broken to me.
    Two posts here:
    http://www.tamba2.org.uk/wordpress/TestTrack/
    Both TB to the same two posts on my blog.
    Only one trackback is received - to the second TB url when a space is used between them.

    I'll post this to the hackers list.

  3. philor
    Member
    Posted 8 years ago #

    Spaces is correct, for 1.5.2 and trunk: commas is either out of date or just not true. The "only the second one" thing is on the receiving end: if you send to two space-separated URLs on two different weblogs, they both go, and if you send to two URLs on the same weblog, you can see from the server logs that both are POSTed, but only one is accepted. My first guess would be duplicate checking that isn't checking whether it's to the same post.

  4. philor
    Member
    Posted 8 years ago #

    Though as usual, my first guess would be wrong: it's actually returning the "Slow down cowboy" error from two comments in less than 15 seconds, although my trunk install doesn't do that, and does accept two pings, even though I don't see any change in the code that ought to have fixed it.

Topic Closed

This topic has been closed to new replies.

About this Topic