The logs coming in from the Link Harvest debug edition I released last night haven’t shown me anything conclusive yet.
Current hunches for the issue include:
- Script timing out.
- Bad Behavior blocking things.
- Plugin incompatibility.
- Certain media types causing trouble (a link to an MP3 file for example).
- PHP version incompatibility.
I’ve put up a new version of Link Harvest with more debug logging added. If you’re having trouble with Link Harvest not completing the initial harvest, try this version.
Download it here, see the install instructions here, and send me the resulting log file.
Thanks again. Just to make sure both versions are version 1 right? Or did I get the old file still?
The debug version is 1.0debug.
I’m having the same problem described here: http://wordpress.org[...]6?replies=10
Tried both debug #1 and #2, but wasn’t able to understand wich post gaves problem to your plugin.
I just can say it always the same point and the log reports:
—SNIP—
Starting with offset “110″
== Start processing post id: 227
Found 2 links in post id: 227
Processed link: http://daubeurs.free[...]ndezvous.mov
Processed link: http://giavasan.diludovico.it/
Added domain: daubeurs.free.fr
About to add link for post id: 227 – http://daubeurs.free[...]ndezvous.mov
—PINS—
Isn’t possible to have the post title in the log?
I was able to find the “bad” post: http://www.fmf.it/bl[...]us-in-paris/
It contains a link to a .mov file.
The workaround I used to complete the harvest is to make “bad” posts as private posts.
At the end of harvesting I tried to set incriminated posts back to public, but I get this error:
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2001 bytes) in /home/mhd-01/www.fmf.it/htdocs/blog/wp-includes/class-snoopy.php on line 901
The log is intended to help me try to find patterns of failure.