LeeStewart wrote:
I went into phpmyadmin and looked at the tables, I saw that xoops_stories was "in use", a state I've never seen before.

This is a test server, so I just nuked the tables and reinstalled News. Everything was working great.

Then I broke it again.

I have two users, one that has permission to create news articles and the webmaster, who can approve articles. I logged in as the webmaster, wrote a news article and approved it. Everything was fine.

When I use the other account (who can't approve articles) to create a news post and then logged in as the webmaster to approve it, the xoops_stories table got stuck in the weird "in use" state.

I can provide any info you might need, template details, MySQL&PHP versions, my shoe size, whatever...

I can provide any info you might need, template details, MySQL&PHP versions, my shoe size, whatever...

What's your Mysql's version ?

LeeStewart wrote:
I'm running an older version on my test machine: MySQL 4.0.0-alpha-nt.

I've never had problems with records getting locked, but I read something about it on a webpage.

I ran "repair" on the table and that seemed to fix things. I'll see if the problem pops up again.

If there's any chance this might be a problem in the News module code,

I can take a look at it. If you're 100% sure it's a MySQL problem, then I'll try it on my production machine running MySQL 4.0.20.

My shoe size is 10 (USA).

LeeStewart wrote:
I poked around and found that the problem occurs when the user approves an article and $this->storyid isn't set. When this happens, the SQL performs an INSERT instead of an UPDATE and things go weird from there.

While I was tracking down the problem further (why is the storyid unknown?

is it not being set in the hidden form variable?) I started having some other problems. I'm not sure if they're related, but even a simple UPDATE causes the xoops_stories table to get locked...