Question though... what if its a 504 Gateway timeout, not from your host but for example if they are trying to link to an image that does not exist on imageshack or similar... does the clear.gif still replace properly then? Or does the gateway timeout hinder that from happening and produce these database errors?

Basically it's not his server ultimately timing out... it is but it isn't if that makes sense, due to the fact its trying to get an image from a server where the image does not exist then timing out.

sir you mean to stay that clear.gif not availeable on my server ?

I have run this mod since, I think maybe a couple of weeks ago?

Everything has been running, I have set it pretty low to spread out the initial uploads over time.

I have noticed it hung somewhere, but it has stopped uploading, as in one image intensive thread,... it did the first image, but it hasnt done the followup posts in that thread. It should have gone through that date fairly quickly?

It has been days since the last upload to my image directory, and I know it isnt done.

Any idea of where to look at what hangs it up?

run this hack manualy from scheduled task manager and see what happend

When I manually run the cron, all I get is a blank page with the title "vB4 Import External Images" at the top. Nothing else.

I have changed domain name of my Web site and now old domain imported image link are not working,How i can get link working and old domain link replace to new domain link?

Yes, if the local server has not died by then. And if it has died, it would repeat querying. With CURL, things are slightly better, since it is possible to tune the timeouts in the options.

If database errors occur, the the db server has died before the web service, and this should never happen. In fact, in production sites the database timeout is one day, because then the connection will drop when the web server drops the page, and at no moment earlier.

We have had this particular issue with another user of this plugin. In the end we worked out that extremely large images would drop PHP without error and warning, and it could be fixed only by adding more RAM to the single processes.

UPDATE post SET pagetext=REPLACE(pagetext, 'old url', 'new url')

and similarily everywhere else you need to (signatures, blogs, cms)

Also, you should empty the postparsed table.

As always, please make a backup before issuing this query.

Question, how do I do that?

And also, how can I find out which image it is that is causing this?