New install 1.7.1 Save new article: fails if publish at the same time - logs show SQL 'IN' error

Hi I have a fresh MODx 2.2.9-pl Advanced install (core is in the same directory as public_html), and have installed Articles 1.7.1-pl, right clicked on resource tree, created a blog page, and clicked New Article. I enter some text in title, body, alias and some new tags and click save. The progress bar scrolls indefinitely.

The MODx error log says:

[2013-09-22 13:46:00] (ERROR @ /assets/components/articles/connector.php) Encountered empty IN condition with key contentid
[2013-09-22 13:46:00] (ERROR @ /assets/components/articles/connector.php) Error 42000 executing statement:
Array
(
[0] => 42000
[1] => 1064
[2] => You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') )' at line 1
)

I try again, same result. I try again without publishing or tags, and the article saves perfectly, and Articles correctly lists all three blog posts, ie, the last two did save. I edit all previous posts, adding tags, setting publish dates, and selecting publish, and all works perfectly.

I create a new blog post exactly as before, (called 'blog post 1'), with tags and setting Published, and get the same failure - the browser request seems to complete as the firefox icon stops revolving, but the ExtJS progress bar scrolls indefinitely.

I add a new blog post, (called 'blog post 2'), specifying tags, content, alias, etc, EXCEPT I do not select Published, and the save works perfectly.

I return to the main blog page and both 'blog post 1' and 'blog post 2' are there. 'blog post 1' is published, 'blog post 2' is not published. I click 'Publish', and nothing appears to happen - the browser icon does not revolve, the grid does not refresh. I browser refresh the page and 'blog post 2' is now also published.

The only contentid I can find in the code seems to do with tags, and the only IN statement seems to be line 36 of gettages.class.php, in ArticleExtrasGetTagsProcessor.process(). However I can't see how 'Publish' would affect this, so perhaps this is a red herring.

I couldn't find a 'register' link on the defect tracker or I'd have posted there.

PS. I'm running on a Ubuntu 12 install with apache2, latest mysql from apt-get, etc, on VirtualBox running on a Win7x64 host via vhosts. Everything else is working perfectly.

PPS. Absolutely beautiful, invaluable extra, thanks very much!

Can you expand on what you mean by 'if publish at same time'? Does that mean if one Article is attempted to be published using the same publish date and time as another?
Haven't been able to reproduce this yet on 2.2.10 with Articles 1.7.2.

Quote from: dinocorn at Oct 26, 2013, 06:00 PM

Can you expand on what you mean by 'if publish at same time'? Does that mean if one Article is attempted to be published using the same publish date and time as another?
Haven't been able to reproduce this yet on 2.2.10 with Articles 1.7.2.

Sorry for not clarifying adequately. All I mean is that I tick the Published box before saving the post for the first time.

Ie, I click New Article, fill in the details and TICK Published, then Save, and I get the error. (I think an AJAX request is successfully sent, but no success signal is returned, so the extJS 'waiting' animation never goes away.)

However, if I click New Article, fill in the details, but DO NOT tick Published, and Save, it works perfectly.

----

That explains what I mean in the title. The below are another attempt to clearly explain the blog admin page/article list symptoms.

Separately, if on the Articles list page I click the Publish button next to an unpublished article, I get no visual response to my click. I assume the AJAX request is not completing due to an error. However if I then refresh the whole page, the article HAS been published.

If on the Articles list page I select a number of Articles by ticking and click Publish, I also get no visual response. If I then refresh the browser page, the first article has been published.

So it seems the error is in a database retrieval involving an IN clause done after the publish UPDATE command is successfully executed.