Scan old posts?

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

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

https://pastebin.com/1pcXhv9p

Thank you.

I don’t think the short codes or elements can stop it. i had copied whole post content codes in https://savageminds.org/2010/01/20/place-hacking/ to my local test site. nothing wrong. so, as your suspected, there may be a database error.

The debug system should could showed you what post id was with problem. maybe i can add edit link of problem posts to error notification.

Sorry i can’t open https://pastebin.com/1pcXhv9p, maybe it’s blocking by GFW(Great Firewall of China).

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

I’m confused..

The debug system shows the “post id” but I’d like the “post number.” That is, if I tell QQ to work on the first 10 posts I’ll get something like this:

20
45
35
47
48
49
.
.
.
56

If the bug is at id# 45 the post number is actually 2, so the next time I run I can tell it to start at number 3 and run for 10, skipping 2. But if I tell it to do ID#46-55 it will skip #35!

I hope that explains better why it would be good to know the number of entries processed before the bug and not just the ID of the bug. Especially if it has run for a few hundred.

Sorry the GFW is causing problems. You can try here:

https://hastebin.com/kimapiduho.xml

I agree that this might not be an error with the post content. But the standard MySQL commands for fixing DB errors don’t seem to have helped either…

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.

Okay, i get it.

In 1.5.7.3, show post number in error notification like this:

7(1), 9(2), 50(3), 90(4), 172(5), 173(6), 174(7), 175(8), 177(9), 4747(10)

This is great. Thanks. With this error reporting I am now able to run it in batches, knowing that I’ve gotten all the posts except for those with errors – and I also have a clear idea of where the errors are.

My only request now would be to suppress the output of all the items with “No remote images found” status reports. Instead showing only those that have missing images (or other important status reports). This would make it easier to see what issues need to be addressed. Otherwise one might have to scroll through a lot of data to find the errors and it is possible to miss them.

Good idia, please update 1.5.7.4.

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.

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

Great, glad to help you.

You are welcome.