S9y wants me to download serendipity_admin.php after posting

[Hokey]

Hi!

I get this window after hitting the "publish"-button (click to enlarge):



S9Y seems to work a while and then this message appears. The post gets published but no pings or trackbacks seem to be sent. Maybe one has an idea how I can fix this.

I use S9Y 1.1-beta5 with PHP 4.4.4 and several plug-ins. If you need further information, write me!

edit
I tried it again and added some ping-links (blogrolling.com, Yahoo, Google,...) and now S9Y tried to send ping and trackbacks but stops with this message:

Code: Select all

Überprüfe http://wirres.net/article/articleview/4012/1/6/ auf mögliche Trackbacks ...
Malformed response.
Notice: Malformed response. in /home/www/doc/13460/serendipity/bundled-libs/PEAR.php on line 848
Malformed response.

[garvinhicking]

Hi!

If you get a download-window like this it usually means your Webserver has had a fatal PHP error, which lead to an invalid return.

It seems the trackback you want to send to the 'wirres.net' does not work, because his webserver returns invalid headers. So you will need to install the "manual trackback" plugin and disable sending trackbacks to that link/for that article.

HTH,
Garvin

[Hokey]

Hi Garvin

I found out that wirres.net was down for some time today. Maybe I sent the trackback exactly at this moment.

The download problem sometimes happens and sometimes not. If the server would be the reason, wouldn't it have to happen everytime? (Sorry for my bad English... )

[garvinhicking]

HI!

Well, this forum on s9y.org also occasionally has that "download" problem, depending on server load and traffic. So it is possible that it can happen sporadically, depending on the server's load and network latency.

HTH,
Garvin

[Hokey]

Okay, thanks!

[carl_galloway]

I'll second what Garvin has said. Over the last week a couple of the major trunk routes in the US have had some issues which meant I've had exactly the same problem with my own blog. It seems to have been fixed now, and I think the problem might have been related to the vast number of big downloads as people upgraded to IE7, and then XP has to check validation and then download a whole bunch of other updates. Several million people doing this would squeeze some networks and make things difficult.