Never Ever Ping Anything

  • Jeff

    (@jmf)


    21 years, 2 months ago

    I know there’s been some degree of discussion about the benefits/drawbacks of pings and update services in the past; I’m not looking to debate, though. Assume for the sake of argument that I wanted a blog (one that I won’t be using, by the way–someone else’s) that wouldn’t even be ABLE to ping a service, accidentally or otherwise. What would I edit to rip that functionality out? 😉

Viewing 3 replies - 1 through 3 (of 3 total)
  • amory

    (@amory)

    21 years, 2 months ago

    Would you be setting it up for them? If so, couldn’t you just delete the ping urls from the update services text box? If you didn’t want the user to be able to see it, you could then simply comment it out, or write an if statement such that if (user_you) then show box else show nothing…

    Thread Starter Jeff

    (@jmf)

    21 years, 2 months ago

    Yeah, I can do that. Is that the only place that pinging takes place, then?

    skippy

    (@skippy)

    21 years, 2 months ago

    There are three seperate ping actions:
    * generic ping
    * pingbacks
    * trackbacks

    Generic pings are those that ping the services listed in Options -> Writing.

    Pingbacks are those that attempt to ping any URLs in the body of posts.

    Trackbacks are manually entered on the post screen.

    You could edit the core WordPress code to comment out all three calls in post.php. That would guarantee that this blog would not generate pings.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Never Ever Ping Anything’ is closed to new replies.