luhmann

Excellent. Also I see that the app is no longer stopping at the errors, but continuing to process additional entries after posting an error report. I think I can go ahead and deploy this plugin on the live version of the site.

你是一個很棒的軟體工程師！謝謝你的幫助。

Finally i crossed the great firewall, and copied whole codes to tested, still nothing wrong.

I’m confused..

So am I. But it doesn’t really matter, as long as I can simply finish the process (using post numbers) making a note of the ID numbers (which the debug code already provides) that cause problems for later debugging.

Very strange. Fixing my database didn’t help either…

Here is the cleaned up code for the post, if you want to see:

http://pastebin.com/1pcXhv9p

So 1.5.7.2 finished its run. Two important notes:

1. It didn’t finish – it still stopped with 3115. This is true even though I cleaned up the code in 3115. I suspect there may be a database error. I will try to run some DB maintenance on my MySQL database to see if that helps. Still not clear what the post number (as opposed to the post ID) is of this entry.

2. I really like that my list was not cleared. I can now see that many posts contain missing images. It would be nice to have a concise report with these posts listed, as it can be hard to see them among the hundreds of posts that were scanned.

3. All of this information is really useful. Running a WP site over time leads to some problems and it is great to be able to go back and debug them like this. You might consider adding checking for broken links and release something like this as a general WP debugging/maintenance plugin.

I tried a larger scale test of the new bug reporting. My goal is to scan all entries, skipping the ones that are causing problems and making a note of them. However, the current implementation of the plugin makes it difficult. If I start at the beginning and try to scan all of the posts (in increments of 10) it goes until it gets an error (the same one that appears above) and then stops. Actually, the error is only caused by 1 of the 10 entries listed there, but that isn’t a big problem. What is a problem is trying to complete the task after this is done. I’m simply not clear how to proceed? The thing is that “offset” interface currently wants the post number but the bug report gives me the post ID. This is a problem because there are posts with higher “post numbers” that have lower “post ID.” It would be best if I could start at the last post number after the error happened, but unfortunately the error report clears the list and so I can’t see where the process ended.

Short version: is it possible to get the error report to also list the post number (as well as the IDs)?

In 1.5.7 it still seems to stall indefinitely when it hits something it can’t process.

I’m happy to continue to help testing this. I am using it on a test install, not the actual website till the issue is worked out.

Thanks.

I think the one that didn’t have an image wasn’t the problematic one, but the one afterwards. It can be hard to tell which posts are actually causing problems because the ID numbers of those posts never appears. What would be good would be when, if a post is taking longer than expected to process, QQWorld asked the user if they would like to skip that one – or just automatically skipped it and then reported at the end which ones were skipped.