Single post causing DB errors - How to fix?

[Lynne]

Impex won't do a thing to help out with this problem.

Did you modify that column in the database like I suggested?

[Gadget_Guy]

Originally Posted by Lynne

Impex won't do a thing to help out with this problem.

Did you modify that column in the database like I suggested?

Can you tell me how to do that?

I will need exact commands if you don't mind.

D.

--------------- Added [DATE]1403744223[/DATE] at [TIME]1403744223[/TIME] ---------------

Okay... figured out how to use myphpadmin...

I did like you said and took care of the post causing that error.

Now, I get another.


I looked at the post... there was nothing strange in it either.


There has to be a better way than doing this one by one.... it's going to take forever.

or should I just say screw it?


Makes me sort of panicy thinking there are a lot of issues in the DB potentially and that I can't run the rebuild post cache.

Should I turn caching off?

D.

[Simon Lloyd]

Are you using a caching mod like vboptimes or such like?

[Gadget_Guy]

Okay... here's an update.

I had my host increase the MySQL max_packet_size to 32M and now I am able to get through a complete run of the Rebuilt Post Cache.

WHEW!

However, there is still that one post in that thread that is causing Chrome to crash.

I can't seem to figure out which post it is or how to deal with it.

I now have ZERO database errors being thrown at me or being able to be captured... but any ideas how I can isolate that one post that is causing that thread to crash?

D.

[Zachery]

In the future, you don't really need to run the rebuild post cache function.

truncating the post_parsed table, will let it naturally rebuild.

[ForceHSS]

Originally Posted by Gadget_Guy

Okay... here's an update.

I had my host increase the MySQL max_packet_size to 32M and now I am able to get through a complete run of the Rebuilt Post Cache.

WHEW!


However, there is still that one post in that thread that is causing Chrome to crash.

I can't seem to figure out which post it is or how to deal with it.


I now have ZERO database errors being thrown at me or being able to be captured... but any ideas how I can isolate that one post that is causing that thread to crash?

D.

Do you have any idea what section or topic this bad post is

[Gadget_Guy]

Update: Something very odd has happened..... and not sure why.

Now... when people click "new posts" nothing comes up even though there are new posts. If you click the "click here for posts in 24 hours" all the new posts are there.

I tried clearing and rebuilding search index after I rebuild the post cache.... still no go.


D.

--------------- Added [DATE]1403803743[/DATE] at [TIME]1403803743[/TIME] ---------------

I have isolated the offending post.

I adjusted my UserCP to only show one post per page and went post by post.

This looks to be the bad post:

https://www.toronto-subaru-club.com/...ycles-745.html


I am going to try and search for it using phpmyadmin

D.

[Zachery]

What cookie mark read system are you using? Read posts don't showup in new posts (hint: they're not new)

[Gadget_Guy]

I made no changes to the cookie settings.

It was all working prior to all this playing around

D.

--------------- Added [DATE]1403804601[/DATE] at [TIME]1403804601[/TIME] ---------------

The good news is I was able to nuke that bad post and that thread is working perfectly now.

D.

--------------- Added [DATE]1403817366[/DATE] at [TIME]1403817366[/TIME] ---------------

I am happy to report that because of all this great advice my site is now working very well.

I managed to find the offending post in that thread and deal with it, that setting change did wonders for the operation of the site, and now that I cleared my own browser cookies the "new posts" are working as they should.


I want to sincerely extend a huge thank you to everyone that chimed in and had such great ideas and suggestions.

Not only did we solve the issues, but I learned a lot as well.

I had never used some of the techniques you illustrated and it is very good information to help me continue on.


THANKS!

D.