Merged Last post date "42 years ago" - access denied to topic - database errors

ozneilau wrote: It's also happening to many other websites. Too many to put this down to database corruption...

Not necessarily. There are many more sites where it does NOT happen. Mine for one. So clearly what is required is an understanding about what is common to the sites where it DOES happen.

I don't have enough data to make that judgement, but I do note your comment:

ozneilau wrote: I am using Joomla 2.5.7 and Kunena 2.0.2 and sh404SEF.

I don't use sh404SEF. Could that therefore be the common denominator on sites that do have this problem? There's no doubting that we read of a LOT of issues that plugin seems to cause.

Thanks for your response! I realise this is not easy to fix and Kunena may not be the cause of the problem, but merely where it is showing up.

sozzled wrote: Occasionally we see these issues in a non-transactional database

Nearly 200,000 instances is a bit more than occasionally! (See attached Google Search).

Neil.

kiwi3685 wrote: Not necessarily. There are many more sites where it does NOT happen. Mine for one. So clearly what is required is an understanding about what is common to the sites where it DOES happen.

Agreed! I look after half a dozen websites with Kunena installed but only the one running v2.0.2 is having this problem.

kiwi3685 wrote: I don't use sh404SEF. Could that therefore be the common denominator on sites that do have this problem?

Possibly. It's happening on kunena.org/forum too. Is sh404SEF used here?

Neil.

No, sh404sef isn't used here

ozneilau wrote: Nearly 200,000 instances

I just re-ran the same search and there are nearly 300,000 search results now.

Whatever the problem is it's spreading. Maybe it's a Joomla update or a Kunena update or something else but hopefully worth someone's time to investigate.

Neil.

More info from a hyper aware moderator on our forum, but she's pretty sure her internet connection hiccupped when she went to submit.

However, there's an easy way to prevent this... Before posting to the database, verify that the post has all the key elements. If not, post an error message and ask the user to repost.