Make WordPress Core

Opened 15 years ago

Closed 15 years ago

#4489 closed defect (bug) (fixed)

WordPress 2.2 broke default comment and ping status for XML-RPC

Reported by: redsweater's profile redsweater Owned by: josephscott's profile josephscott
Milestone: 2.2.1 Priority: normal
Severity: normal Version: 2.2
Component: Administration Keywords:
Focuses: Cc:


Some good changes that went into xmlrpc.php for the 2.2 milestone inadvertently broke the behavior of WordPress for comment and ping status. I don't have time to put together a patch right now, but the summary of the problem is observed by searching on

if(isset($content_structmt_allow_comments?)) {


if(isset($content_structmt_allow_pings?)) {

In xlmrpc.php. Note that the new structure of this logic (new to 2.2) causes the default_comment_status and default_ping_status values never to be used unless the client attempted to supply a value.

The fix is to make sure that the default status values are used when the content structs are NOT set.

I think this should be considered a higher priority than 2.3, since it's a regression in 2.2 from previous releases.

Daniel Jalkut
Red Sweater Software

(NOTE: This bug is still present in trunk and with the latest changes proposed by I'm writing a separate bug because that issue is not scheduled until 2.3. I'll also add some comments to that issue, however.)

Change History (7)

#1 @redsweater
15 years ago

I should have been more explicit about the end-user behavior. With the bug in 2.2, users of clients which by default do not set any value for the comments or pings status, find that the posts acquire the value of whatever an uninitialized variable is in PHP. It seems to be 0 - that is, comments and pings are forced to OFF.

This is frustrating to users who have been used to the behavior of comments "just working."

#2 @foolswisdom
15 years ago

  • Milestone set to 2.2.2

#3 @josephscott
15 years ago

  • Owner changed from anonymous to josephscott

#4 @josephscott
15 years ago

I've updated with a new patch that addresses this issue as well.

#5 @markjaquith
15 years ago

Thanks for the report, Daniel!

Does [5730] fix it?

#6 @redsweater
15 years ago

Hi Mark - yes the fix for [5730] looks good to me, and in my quick tests on it seemed to be behaving as desired.

#7 @foolswisdom
15 years ago

  • Milestone changed from 2.2.2 to 2.2.1
  • Resolution set to fixed
  • Status changed from new to closed

Confirmed in 2.2.1 rc.

Note: See TracTickets for help on using tickets.