[wp-trac] [WordPress Trac] #5366: XMLRPC interface misinterprets
mt_allow_comments value
WordPress Trac
wp-trac at lists.automattic.com
Mon Nov 19 18:17:12 GMT 2007
#5366: XMLRPC interface misinterprets mt_allow_comments value
------------------------+---------------------------------------------------
Reporter: redsweater | Owner: josephscott
Type: defect | Status: new
Priority: normal | Milestone: 2.5
Component: XML-RPC | Version: 2.3.1
Severity: normal | Keywords:
------------------------+---------------------------------------------------
WordPress's XMLRPC interface makes an understandable mistake when
interpreting the mt_allow_comments field.
The field as described and used by MovableType and others is actually a
ternary value with integer values meaning:
0 - None - No comments allowed
1 - Open - Comments can be read and write
2 - Closed - Comments can be read but not written
WordPress doesn't have a notion of "read-only comments" but it needs to do
something accurate when the "2" (closed) value is passed to the XMLRPC
interface.
Right now what it does is fail to recognize 2 as a valid input, and
defaults to the system default comment status.
I believe it should map "2" -> "closed" so that the expected behavior of
halting further comments is obtained by the user. The typical scenario now
is that the blog defaults to "open" comments, so when a user of a client
application specifies "closed" for the comment status, the server defaults
it back to "open" ... exactly the opposite of the user's desire.
--
Ticket URL: <http://trac.wordpress.org/ticket/5366>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list