node validate prevents programmatic node submission [#80271]

Have noticed a few issues with XML-RPC usage since the update to 4.7.3. Some of these things (like MetaWeblog categories) are - I believe - older issues, but the main issue appears to be new.

Attempting to post a blog entry using the MovableType API and any available blogging client (I have attempted to use BlogDesk, Windows Live Writer, and ecto) results in the blog entry being posted, but not published, regardless of settings on the client or the Drupal installation. The error returned is this:

This content has been modified by another user, changes cannot be saved.

I know from personal usage that this was working properly prior to my update to 4.7.3. I cannot personally remember posting since I made that change and having an entry publish successfully. A quick scan of the relevant support forms indicates that this problem is also affecting other users, who are asking the software writers to respond.

On the flip side, categories are unable to be retrieved by several blogging clients while trying to use the metaWeblog API, claiming that the server response was "invalid."

Comment	File	Size	Author
#16	node_changed_47.patch.txt	1.28 KB	Heine
#12	node_changed.patch.txt	1.26 KB	Heine

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mgharris CreditAttribution: mgharris commented 25 August 2006 at 01:17

I can't say that I can concur with your expeirence with any release of Drupal since 4.6 right through to the new 4.7.X branch.

I have used several blogging clients to connect with both the MoveableType and Blogger API's and they have worked without incident. Have successfully used Windows Live Writer, w.bloggar, and a couple of others who's names I cannot recall right now. All have been able to successfully perform all relevant functions and posted content has been published without incident.

I strongly suspect the problem may reside with user permissions for the account you are using to connect for posting, or blogging client configuration problems. This issue would be better addressed in the post installation support forum.

Comment #2

cpzhao CreditAttribution: cpzhao commented 27 August 2006 at 15:24

I concur with the original post. There seems to be a lot of changes in the xmlrpc code from 4.7.2 to 4.7.3 (I diffed the code). I can get a few blog clients to work with 4.7.2, but they all fail (with the exact error as above) with 4.7.3.

More details at:
http://www.cpzhao.com/drupal_blog_clients

Comment #3

funana CreditAttribution: funana commented 28 August 2006 at 11:03

Same problem here. Fresh 4.7.3 install. Same error.

Also the same error with Aggregator2 Module, which I reported here:
http://drupal.org/node/81085

Comment #4

jshiell CreditAttribution: jshiell commented 31 August 2006 at 21:09

Also seen here - worked fine on 4.7.2, behaviour occurs with 4.7.3 upgrade.

Comment #5

Ryan Markel CreditAttribution: Ryan Markel commented 6 September 2006 at 05:32

Priority:

Normal

» Critical

On the concurrences from other users, I am bumping this to "critical," as the blogapi is completely useless if external clients cannot connect to it properly or use its full functionailty.

To respond to the first follow-up from this issue, no blogging client configurations were changed from 4.7.2 to 4.7.3, and the account I am attempting to post with is the *superuser* account.

MovableType API is workaround-able, but not completely useful, as posts can be created, but they are not set to "published" due to the error above. In my experience so far, the MetaWeblog implementation doesn't produce categories when a post is sent to the system, and the Blogger API is pretty much useless because it doesn't support most of the *good* functionality possible with Drupal.