Not pingning blo.gs etc., when publishing a draft

[hrkaspar]

When I write an article and save it as draft, there is no ping to the different "bloggregators" out there when I publish it. Seem´s like an important bug to me!

[garvinhicking]

Thanks for bringing this to attention again -- it was formerly a known "TODO" item, but seems to have been forgotten since then!

I have just fixed that in CVS, it was indeed undesired behaviour.

[blogjam]

I think a variation of this behaviour still exists - when you publish a post with a publishing date set in the future, the ping is sent immediately, not when the post actually appears online.

[garvinhicking]

Yes. There's sadly nothing we can do about it easily.

This would require a crontab facility, which has several drawbacks. There was a discussion on this forum about it, maybe you can look it up.

Regards,
Garvin

[blogjam]

Thanks Garvin - I will do.

[Ralf Skirr]

Is scheduled publishing and pinging possilbe now?

Since this thread is quite old now I wonder whether the behaviour of the ping has changed with newer versions of Serendipity.

Is it possible to schedule a post for publishing at a future date and then have the ping happening at that future date?

Ragards,
Ralf

[stm999999999]

I read this thread because of the new posting and I have a big question to the first posting:

Why should there be a ping when the article is still a draft!?

[Ralf Skirr]

sorry, double post, don't know how to delete this

[Ralf Skirr]

Why should there be a ping when the article is still a draft!?

The ping is not meant to be for the draft. The ping is meant to be sent when the post is finally published. Then it should be beyon draft state.

That should also be true for the first post in this thread.

I am referring to a scheduled publishing. So I don't have a draft state at all. I simply want to write and save the post today but have it published on a specific date and THEN have the ping occur at that specific date.

Ralf

[garvinhicking]

Hi!

No, Serendipity currently cannot send pings for posts published in the future at the time where an entry appears.

There now exists a cronjob event plugin though, for which a sub-plugin could be created that would send a ping for not-yet-pinged entries periodically.

However, to me it seems that XMLRPC pinging has become quite useless because of spambots and has for most services little use. Most services crawl pages periodically themselves and discard XMLRPC pings completely.

Best regards,
Garvin

[Ralf Skirr]

Thanks Garvin,

that's good to know.

Kind Regards,
Ralf

[stm999999999]

There now exists a cronjob event plugin though, for which a sub-plugin could be created that would send a ping for not-yet-pinged entries periodically.

that would be realy nice. And even if such pings are possibily useless today, this mechanism could be interesting for trackback-pings, or?

[garvinhicking]

that would be realy nice. And even if such pings are possibily useless today, this mechanism could be interesting for trackback-pings, or?

I already see bug reports coming in from users that report "My trackbacks get sent over and over again every 5 minutes, help!"

[stm999999999]

in the moment, I don't understand this problem. Why over and over again?

[garvinhicking]

Hi!

Because it might be that when a trackback should be sent, it timeouts and fails. But because the timestamp is reached, the next PHP calltime will call the trackback again. And it fails again. And gets send again. And again. And so on.

Also, if people call your blog within the same second, it might be that trackbacks get sent twice, if no safe lockfile could be created.

Plus, people that call the blog during the sending of a trackback, it might stale and create many apache children.

The opossibilities of the screwup of this are nearly endless

Best regards,
Garvin