WordPress Trac: Ticket #18438: Create a new term in XMLRPChttps://core.trac.wordpress.org/ticket/18438
en-usWordPress Trachttps://core.trac.wordpress.org/chrome/site/your_project_logo.pnghttps://core.trac.wordpress.org/ticket/18438
Trac 1.0.1nprasath002Tue, 16 Aug 2011 05:22:55 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>wp.newTerm.patch</em>
</li>
</ul>
TicketmaxcutlerWed, 28 Dec 2011 17:06:55 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>wp.newTerm.2.patch</em>
</li>
</ul>
TicketmaxcutlerWed, 28 Dec 2011 17:07:06 GMTcc sethttps://core.trac.wordpress.org/ticket/18438#comment:1
https://core.trac.wordpress.org/ticket/18438#comment:1
<ul>
<li><strong>cc</strong>
<em>max@…</em> added
</li>
</ul>
<p>
Updated patch formatting and tightened the validation logic. Also fixed the return value which did not match the docstring.
</p>
TicketwestiMon, 06 Feb 2012 17:45:54 GMTstatus, type, milestone changed; owner sethttps://core.trac.wordpress.org/ticket/18438#comment:2
https://core.trac.wordpress.org/ticket/18438#comment:2
<ul>
<li><strong>owner</strong>
set to <em>westi</em>
</li>
<li><strong>status</strong>
changed from <em>new</em> to <em>accepted</em>
</li>
<li><strong>type</strong>
changed from <em>feature request</em> to <em>task (blessed)</em>
</li>
<li><strong>milestone</strong>
changed from <em>Awaiting Review</em> to <em>3.4</em>
</li>
</ul>
<p>
We are including this in our second cycle on XML RPC new features for 3.4 and will use it as the tracking ticket for this cycle's other tickets: <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18439" title="task (blessed): Edit a term in XMLRPC (closed: fixed)">#18439</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18440" title="task (blessed): Delete a term in XMLRPC (closed: fixed)">#18440</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18441" title="task (blessed): Retrieve a term in XML-RPC (closed: fixed)">#18441</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18442" title="task (blessed): Retrieve a list of terms in XML-RPC (closed: fixed)">#18442</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18443" title="task (blessed): Retrieve a taxonomy in XML-RPC (closed: fixed)">#18443</a>, and <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18444" title="task (blessed): Retrieve a list of taxonomies in XML-RPC (closed: fixed)">#18444</a>
</p>
TicketmaxcutlerTue, 07 Feb 2012 03:21:49 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>taxes.combo.patch</em>
</li>
</ul>
<p>
Combined patch with the 7 new methods for cycle 2.
</p>
TicketmaxcutlerTue, 07 Feb 2012 03:23:34 GMThttps://core.trac.wordpress.org/ticket/18438#comment:3
https://core.trac.wordpress.org/ticket/18438#comment:3
<p>
As discussed on IRC, I've put together a patch that combines the methods from the seven taxonomy-related XML-RPC method tickets.
</p>
TicketmarkoheijnenTue, 07 Feb 2012 21:15:56 GMTcc changedhttps://core.trac.wordpress.org/ticket/18438#comment:4
https://core.trac.wordpress.org/ticket/18438#comment:4
<ul>
<li><strong>cc</strong>
<em>marko@…</em> added
</li>
</ul>
TicketmaxcutlerWed, 08 Feb 2012 04:59:04 GMThttps://core.trac.wordpress.org/ticket/18438#comment:5
https://core.trac.wordpress.org/ticket/18438#comment:5
<p>
Updated the patch after the changes in <a class="changeset" href="https://core.trac.wordpress.org/changeset/19848" title="XMLRPC: Introduce new create,read,update and delete XMLRPC apis for Posts, ...">[19848]</a>. Going to start working on unit tests later in the week.
</p>
TicketmaxcutlerSat, 11 Feb 2012 14:26:06 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>taxes.combo.2.patch</em>
</li>
</ul>
<p>
Refreshed patch after other recent changes.
</p>
TicketmaxcutlerSat, 11 Feb 2012 14:26:46 GMThttps://core.trac.wordpress.org/ticket/18438#comment:6
https://core.trac.wordpress.org/ticket/18438#comment:6
<p>
I've updated the <tt>taxes.combo.2.patch</tt> file to apply cleanly after other recent commits to <tt>class-wp-xmlrpc-server.php</tt>.
</p>
TicketmarkoheijnenSun, 12 Feb 2012 01:54:37 GMThttps://core.trac.wordpress.org/ticket/18438#comment:7
https://core.trac.wordpress.org/ticket/18438#comment:7
<p>
Was busy with creating unit tests for the patch and I wonder the following things:
</p>
<p>
wp_newTerm
</p>
<ul><li>Check if taxonomy is set and is a string
</li><li>Why is there the following line: $taxonomy = (array) taxonomy?
</li><li>return term_id should have strval()
</li></ul><p>
wp_editTerm
</p>
<ul><li>should the current_user_can check $term_id as second parameter?
</li><li>error check op $parent_term but trying to show the error of $term
</li><li>Error message for parent variable is not the same as newTerm, the same for error code
</li></ul>
Ticketnprasath002Sun, 12 Feb 2012 05:03:23 GMThttps://core.trac.wordpress.org/ticket/18438#comment:8
https://core.trac.wordpress.org/ticket/18438#comment:8
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/18438#comment:7" title="Comment 7 for Ticket #18438">markoheijnen</a>:
</p>
<blockquote class="citation">
<p>
Was busy with creating unit tests for the patch and I wonder the following things:
</p>
<p>
wp_newTerm
</p>
<ul><li>Check if taxonomy is set and is a string
</li></ul></blockquote>
<p>
A new term must be associated with a taxonomy. So we check whether the input taxonomy is valid.
</p>
<blockquote class="citation">
<ul><li>Why is there the following line: $taxonomy = (array) taxonomy?
</li></ul></blockquote>
<p>
get_taxonomy() returns a taxonomy object.
We use
</p>
<pre class="wiki">$object-&gt;key
</pre><blockquote>
<p>
to get the value from the object.
</p>
</blockquote>
<p>
To use
</p>
<pre class="wiki">$object['key']
</pre><blockquote>
<p>
you must cast the object to an array.
</p>
</blockquote>
<p>
Of course we can use
</p>
<pre class="wiki">$object-&gt;key
</pre><blockquote>
<p>
through out.
</p>
</blockquote>
<p>
But all of the other functions are coded in
</p>
<pre class="wiki">$object['key']
</pre><blockquote>
<p>
style.
</p>
</blockquote>
<p>
For consistency i casted it to an array.
</p>
<blockquote class="citation">
<ul><li>return term_id should have strval()
</li></ul></blockquote>
<p>
+1
</p>
<blockquote class="citation">
<p>
wp_editTerm
</p>
<ul><li>should the current_user_can check $term_id as second parameter?
</li></ul></blockquote>
<p>
I think for terms we check capability in general. Not for a specific term like in posts.
AFAIK there is no 'edit_term' cap defined in the core.
</p>
<blockquote class="citation">
<ul><li>error check op $parent_term but trying to show the error of $term
</li></ul></blockquote>
<p>
+1. Should fix that
</p>
<blockquote class="citation">
<ul><li>Error message for parent variable is not the same as newTerm, the same for error code
</li></ul></blockquote>
<p>
+1
</p>
TicketmarkoheijnenSun, 12 Feb 2012 12:54:49 GMThttps://core.trac.wordpress.org/ticket/18438#comment:9
https://core.trac.wordpress.org/ticket/18438#comment:9
<p>
Thanks for the answers. About the taxonomy check if you pass an array it will result in an error since an array can't be a key.
Not sure if this is something that should be checked tho.
</p>
<p>
About the error codes is there a page about which codes should apply to an error?
</p>
TicketmarkoheijnenSun, 12 Feb 2012 14:03:38 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>term_unittests_new-edit.patch</em>
</li>
</ul>
<p>
1 test will fail due not returning id as a string
</p>
TicketmarkoheijnenSun, 12 Feb 2012 14:07:01 GMThttps://core.trac.wordpress.org/ticket/18438#comment:10
https://core.trac.wordpress.org/ticket/18438#comment:10
<p>
Added some basic unit tests for creating and editing a term. First time I wrote something like this. Love to get some feedback.
</p>
Ticketnprasath002Sun, 12 Feb 2012 14:13:58 GMThttps://core.trac.wordpress.org/ticket/18438#comment:11
https://core.trac.wordpress.org/ticket/18438#comment:11
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/18438#comment:9" title="Comment 9 for Ticket #18438">markoheijnen</a>:
</p>
<blockquote class="citation">
<p>
Thanks for the answers. About the taxonomy check if you pass an array it will result in an error since an array can't be a key.
Not sure if this is something that should be checked tho.
</p>
<p>
About the error codes is there a page about which codes should apply to an error?
</p>
</blockquote>
<p>
The error codes are based on http error codes,
<a class="ext-link" href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes"><span class="icon">​</span>http://en.wikipedia.org/wiki/List_of_HTTP_status_codes</a>
</p>
<blockquote>
<p>
although some of the error codes in class-xmlrpc-server don't line up perfectly
</p>
</blockquote>
TicketmarkoheijnenSun, 12 Feb 2012 14:36:27 GMThttps://core.trac.wordpress.org/ticket/18438#comment:12
https://core.trac.wordpress.org/ticket/18438#comment:12
<p>
I thought so but wasn't sure. I think a lot of the 500 error code should be changed since in the XML-RPC we don't know the reason but the function that is given the error does. It returns an error message so error code 500 isn't the right one. 403 makes more sense then.
</p>
TicketmarkoheijnenWed, 15 Feb 2012 02:07:01 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>taxes.combo.3.patch</em>
</li>
</ul>
TicketmarkoheijnenWed, 15 Feb 2012 02:08:36 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>term_unittests_new-edit.2.patch</em>
</li>
</ul>
TicketmarkoheijnenWed, 15 Feb 2012 02:14:52 GMThttps://core.trac.wordpress.org/ticket/18438#comment:13
https://core.trac.wordpress.org/ticket/18438#comment:13
<p>
Added a new patch and new unit tests.
</p>
<ul><li>return term_id should have strval()
</li><li>error check op $parent_term but trying to show the error of $term
</li><li>Error message for parent variable is not the same as newTerm, the same for error code
</li><li>Changed some of the error messages so it is the same for all the term/taxonomy methods
</li></ul><p>
Did wonder if someone can explain why there is an assign term check for wp_getTerm and wp_getTerms. Same for the edit taxonomy check for wp_getTaxonomy and wp_getTaxonomies. I think those checks can be removed.
</p>
TicketmaxcutlerWed, 15 Feb 2012 02:21:18 GMThttps://core.trac.wordpress.org/ticket/18438#comment:14
https://core.trac.wordpress.org/ticket/18438#comment:14
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/18438#comment:13" title="Comment 13 for Ticket #18438">markoheijnen</a>:
</p>
<blockquote class="citation">
<p>
Did wonder if someone can explain why there is an assign term check for wp_getTerm and wp_getTerms. Same for the edit taxonomy check for wp_getTaxonomy and wp_getTaxonomies. I think those checks can be removed.
</p>
</blockquote>
<p>
I think that was an attempt to restrict access so that not just <em>any</em> user can fetch the taxonomy information. I'm not sure if or what a better cap check could be, or even what the data leakage concerns would be without a cap check.
</p>
<p>
The new wp.getPost and wp.getPosts methods check the <tt>edit_post</tt> cap for similar reasons, I assume.
</p>
TicketwestiWed, 15 Feb 2012 11:04:28 GMThttps://core.trac.wordpress.org/ticket/18438#comment:15
https://core.trac.wordpress.org/ticket/18438#comment:15
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/18438#comment:13" title="Comment 13 for Ticket #18438">markoheijnen</a>:
</p>
<blockquote class="citation">
<p>
Added a new patch and new unit tests.
</p>
<ul><li>return term_id should have strval()
</li><li>error check op $parent_term but trying to show the error of $term
</li><li>Error message for parent variable is not the same as newTerm, the same for error code
</li><li>Changed some of the error messages so it is the same for all the term/taxonomy methods
</li></ul><p>
Did wonder if someone can explain why there is an assign term check for wp_getTerm and wp_getTerms. Same for the edit taxonomy check for wp_getTaxonomy and wp_getTaxonomies. I think those checks can be removed.
</p>
</blockquote>
<p>
Thanks for the updates - I started reviewing the tests and patch yesterday and came accross some of these too.
</p>
<p>
I'll restart my review from the latest patches :)
</p>
TicketwestiWed, 15 Feb 2012 11:17:06 GMThttps://core.trac.wordpress.org/ticket/18438#comment:16
https://core.trac.wordpress.org/ticket/18438#comment:16
<p>
Unit Tests committed in <a class="ext-link" href="https://unit-tests.trac.wordpress.org//intertrac/changeset%3A529" title="changeset:529 in WordPress Unit Tests Trac (old)"><span class="icon">​</span>[UT529]</a> and <a class="ext-link" href="https://unit-tests.trac.wordpress.org//intertrac/changeset%3A530" title="changeset:530 in WordPress Unit Tests Trac (old)"><span class="icon">​</span>[UT530]</a> - There are a couple of bugs in them which I'm going to fix up post-commit.
</p>
TicketmarkoheijnenWed, 15 Feb 2012 11:58:46 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>term_unittests_all.patch</em>
</li>
</ul>
TicketmarkoheijnenWed, 15 Feb 2012 12:00:25 GMThttps://core.trac.wordpress.org/ticket/18438#comment:17
https://core.trac.wordpress.org/ticket/18438#comment:17
<p>
Damn, I uploaded the wrong unit test file. Uploaded here again which also include all the other tests.
Do wonder how we should check the data we get back.
</p>
TicketwestiWed, 15 Feb 2012 12:07:34 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>18438-westi.diff</em>
</li>
</ul>
<p>
Updated version of combo 3 based on my changes so far to correct things while reviewing tests.
</p>
TicketmaxcutlerSat, 18 Feb 2012 21:45:44 GMThttps://core.trac.wordpress.org/ticket/18438#comment:18
https://core.trac.wordpress.org/ticket/18438#comment:18
<p>
It might be worth adding another function akin to <a class="ext-link" href="http://codex.wordpress.org/XML-RPC_wp#wp.suggestCategories"><span class="icon">​</span>wp.suggestCategories</a> that can work against any of the taxonomies.
</p>
TicketmarkoheijnenMon, 20 Feb 2012 23:22:11 GMThttps://core.trac.wordpress.org/ticket/18438#comment:19
https://core.trac.wordpress.org/ticket/18438#comment:19
<p>
For the terms get method don't we need to set the arg hide_empty to false for the function get_terms() ? Or at least the ability to modify it?
</p>
<p>
Also for get_term() shouldn't we set the output to ARRAY_A and for casting it to an array use get_object_vars()? Like WordPress does if you look into the get_term() function
</p>
TicketmaxcutlerTue, 21 Feb 2012 03:29:08 GMThttps://core.trac.wordpress.org/ticket/18438#comment:20
https://core.trac.wordpress.org/ticket/18438#comment:20
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/18438#comment:19" title="Comment 19 for Ticket #18438">markoheijnen</a>:
</p>
<blockquote class="citation">
<p>
For the terms get method don't we need to set the arg hide_empty to false for the function get_terms() ? Or at least the ability to modify it?
</p>
</blockquote>
<p>
I would be in favor of adding an optional <tt>$filter</tt> parameter that covers most of the arguments to <tt>get_terms</tt>, just like we did for <tt>wp.getPosts</tt>.
</p>
<blockquote class="citation">
<p>
Also for get_term() shouldn't we set the output to ARRAY_A and for casting it to an array use get_object_vars()? Like WordPress does if you look into the get_term() function
</p>
</blockquote>
<p>
+1
</p>
TicketmaxcutlerThu, 23 Feb 2012 15:34:10 GMThttps://core.trac.wordpress.org/ticket/18438#comment:21
https://core.trac.wordpress.org/ticket/18438#comment:21
<p>
Cap check changes <a class="ext-link" href="https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&amp;day=2012-02-22&amp;sort=asc#m368792"><span class="icon">​</span>discussed</a> yesterday on IRC:
</p>
<ul><li>Only <tt>wp.editTerm</tt> needs to check the <tt>edit_terms</tt> cap. The <tt>wp.getTerm</tt>, <tt>wp.getTerms</tt>, <tt>wp.getTaxonomies</tt>, and <tt>wp.getTaxonomy</tt> methods should check <tt>assign_terms</tt> instead since they are read-only.
</li><li>nacin suggested <tt>wp.newTerm</tt> should also check <tt>assign_terms</tt> instead of <tt>edit_terms</tt>/<tt>manage_terms</tt>, since currently that's all that's required to create a new tag. He's going to follow up/confirm after doing some more research.
</li></ul>
TicketmaxcutlerSun, 26 Feb 2012 18:30:39 GMTattachment sethttps://core.trac.wordpress.org/ticket/18438
https://core.trac.wordpress.org/ticket/18438
<ul>
<li><strong>attachment</strong>
set to <em>taxes.combo.5.patch</em>
</li>
</ul>
TicketmaxcutlerSun, 26 Feb 2012 18:32:35 GMThttps://core.trac.wordpress.org/ticket/18438#comment:22
https://core.trac.wordpress.org/ticket/18438#comment:22
<p>
Refreshed patch with following changes:
</p>
<ul><li>Tweaked caps on <tt>wp.getTaxonomy</tt> and <tt>wp.getTaxonomies</tt> per previous comment.
</li><li>Added optional <tt>filter</tt> parameter to <tt>wp.getTerms</tt> to support more scenarios, including <tt>hide_empty=0</tt> and <tt>search</tt> (in lieu of a separate <tt>wp.suggestTerm</tt> method).
</li><li>Use <tt>get_object_vars</tt> to convert term object to array.
</li></ul>
TicketmaxcutlerFri, 02 Mar 2012 19:15:06 GMThttps://core.trac.wordpress.org/ticket/18438#comment:23
https://core.trac.wordpress.org/ticket/18438#comment:23
<p>
<tt>get_term</tt>/<tt>get_term_by</tt> return all field values as <tt>string</tt>s, even though some represent <tt>int</tt>s. For example, <tt>count</tt> and the various IDs (<tt>term_id</tt>, <tt>parent</tt>, <tt>term_group</tt>, <tt>term_taxonomy_id</tt>). Should we cast these fields to <tt>int</tt> in <tt>_prepare_term</tt>?
</p>
TicketwestiWed, 07 Mar 2012 16:32:12 GMThttps://core.trac.wordpress.org/ticket/18438#comment:24
https://core.trac.wordpress.org/ticket/18438#comment:24
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/18438#comment:23" title="Comment 23 for Ticket #18438">maxcutler</a>:
</p>
<blockquote class="citation">
<p>
<tt>get_term</tt>/<tt>get_term_by</tt> return all field values as <tt>string</tt>s, even though some represent <tt>int</tt>s. For example, <tt>count</tt> and the various IDs (<tt>term_id</tt>, <tt>parent</tt>, <tt>term_group</tt>, <tt>term_taxonomy_id</tt>). Should we cast these fields to <tt>int</tt> in <tt>_prepare_term</tt>?
</p>
</blockquote>
<p>
We should explicitly cast everything to whatever we want it returned as IMHO so as to future proof the code against internal api changes (in the past these have accidentally changed the datatypes returned by XMLRPC).
</p>
<p>
For anything where the db schema supports values larger than XML-RPC for Integers we should return them as strings to be safe.
</p>
TicketwestiWed, 07 Mar 2012 17:02:23 GMThttps://core.trac.wordpress.org/ticket/18438#comment:25
https://core.trac.wordpress.org/ticket/18438#comment:25
<p>
In <a class="changeset" href="https://core.trac.wordpress.org/changeset/20137" title="XML-RPC: Initial implementation of Taxonomy and Term APIs.
Implements: ...">[20137]</a>:
</p>
<div class="message"><p>
XML-RPC: Initial implementation of Taxonomy and Term APIs.<br />
</p>
<p>
Implements: wp.newTerm, wp.editTerm, wp.deleteTerm, wp.getTerm, wp.getTerms, wp.getTaxonomy and wp.getTaxonomies<br />
</p>
<p>
See: <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18438" title="task (blessed): Create a new term in XMLRPC (closed: fixed)">#18438</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18439" title="task (blessed): Edit a term in XMLRPC (closed: fixed)">#18439</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18440" title="task (blessed): Delete a term in XMLRPC (closed: fixed)">#18440</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18441" title="task (blessed): Retrieve a term in XML-RPC (closed: fixed)">#18441</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18442" title="task (blessed): Retrieve a list of terms in XML-RPC (closed: fixed)">#18442</a>, <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18443" title="task (blessed): Retrieve a taxonomy in XML-RPC (closed: fixed)">#18443</a>, and <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18444" title="task (blessed): Retrieve a list of taxonomies in XML-RPC (closed: fixed)">#18444</a> props maxcutler, markoheijnen and nprasath002.<br />
</p>
</div>
TicketwestiThu, 08 Mar 2012 13:31:33 GMThttps://core.trac.wordpress.org/ticket/18438#comment:26
https://core.trac.wordpress.org/ticket/18438#comment:26
<p>
In <a class="changeset" href="https://core.trac.wordpress.org/changeset/20159" title="XMLRPC: Start casting datatypes in _prepare_term so as to ensure ...">[20159]</a>:
</p>
<div class="message"><p>
XMLRPC: Start casting datatypes in _prepare_term so as to ensure consistent datatypes in our responses. See <a class="closed ticket" href="https://core.trac.wordpress.org/ticket/18438" title="task (blessed): Create a new term in XMLRPC (closed: fixed)">#18438</a>. <br />
</p>
</div>
TicketmaxcutlerWed, 28 Mar 2012 20:46:50 GMTstatus changed; resolution sethttps://core.trac.wordpress.org/ticket/18438#comment:27
https://core.trac.wordpress.org/ticket/18438#comment:27
<ul>
<li><strong>status</strong>
changed from <em>accepted</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>fixed</em>
</li>
</ul>
<p>
New bugs or enhancements on new tickets.
</p>
Ticket