<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 26, 2007, at 3:35 PM, Joseph Scott wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Helvetica Neue'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">In going over the changes in the 2.2 branch for xmlrpc.php (<a href="http://trac.wordpress.org/log/branches/2.2/xmlrpc.php">http://trac.wordpress.org/log/branches/2.2/xmlrpc.php</a>) revision 5305 (and 5514 by association) is where the problem hit. So reverting 5305 in the 2.2 branch (and trunk, along with the associated 5514 revision) will fix the client breakage. Does everyone agree this is correct?<br></span></blockquote></div><br><div>Assuming I'm reading the diffs correctly, and understand your intention, this will put the source tree back to pre-2.2 behavior, right?</div><div><br class="webkit-block-placeholder"></div><div>That is, it will return to being a server-specific time (GMT adjusted for blog time-zone offset).</div><div><br class="webkit-block-placeholder"></div><div>I agree that doing this will put WP behavior back to something akin to what the vast majority of blogging systems do, right or wrong. It will incidentally also remove any bugs my users had specifically with WP 2.2.</div><div><br class="webkit-block-placeholder"></div><div>Daniel</div><div><br class="webkit-block-placeholder"></div></body></html>