As it turns out, the last time I did repairs this error was gone. But I appreciate your help anyway – if it happens again I will know what to look for.
Oh and yes, I don’t use threaded replies either.
Thank you so much again for your help Robin – this is very helpful information.
Thank you so much for your help Robin – I appreciate it.
So no one can help me with this? I know that the Jetpack mobile theme restricts the blog posts to 5 per page (even though it is set to 10 in the WordPress settings, which is what I want for my desktop theme), so I assume there must be some kind of hook I can use to do the same with bbPress posts.
TBH this is the first time I’ve recorded the error – the first couple of times I assumed it must just be some kind of random error, given that I’d never seen it before. So I can’t confirm if it has always had the missing apostrophe in that position, but I can confirm that the error always occurred in relation to the favorites.
It has happened the last three times I’ve done repairs. How can I go about fixing this?
Like I said, as if I was hitting the submit button on the topic. There won’t actually be anything new within the topic itself, I just want it to be updated, as if it was saved but without any actual changes in the topic itself. I simply want a reply to the topic to trigger a save within the topic itself. I think you’re thinking I must be wanting something more complicated, but it really is that simple.
I do not want the standard behaviour to be modified in any way, except that the topic itself be updated when a reply is posted to it. Nothing will look any different to standard bbpress behaviour as far as the user is concerned – I just want to simulate hitting the submit button on the topic when a reply is posted, nothing more.
Okay, I mean the submit button. I just want the topic to be updated (as if I was hitting the submit button) when a reply is posted, that’s all.
Thanks for the info. I guess this is an example of why I don’t upgrade WordPress – in order to add some feature that will probably be of little use to the vast majority of users, they break compatibility with what will probably be a boatload of plug-ins (given how fundamental this change is). Well done Automatic.
Oh BTW, would 2.5.11 work okay with 3.7?
