<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Make WordPress Core &#187; API</title>
	<atom:link href="http://make.wordpress.org/core/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://make.wordpress.org/core</link>
	<description>WordPress Development Updates</description>
	<lastBuildDate>Mon, 17 Jun 2013 10:00:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.6-beta3-24432</generator>
	<atom:link rel='hub' href='http://make.wordpress.org/core/?pushpress=hub'/>
		<item>
		<title>Javascript changes in 3.3</title>
		<link>http://make.wordpress.org/core/2011/09/23/javascript-changes-in-3-3/</link>
		<comments>http://make.wordpress.org/core/2011/09/23/javascript-changes-in-3-3/#comments</comments>
		<pubDate>Fri, 23 Sep 2011 06:47:49 +0000</pubDate>
		<dc:creator>Andrew Ozz</dc:creator>
				<category><![CDATA[post]]></category>
		<category><![CDATA[3.3]]></category>
		<category><![CDATA[API]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/?p=1631</guid>
		<description><![CDATA[Now that WordPress 3.3 is in feature freeze, it&#8217;s time to have a look at some new Javascript goodies for developers: jQuery 1.6.4 and jQuery UI 1.8.16. And that&#8217;s the full UI including widgets and effects. This will make it a lot easier and simpler for plugins using UI components that are not used in [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Now that WordPress 3.3 is in feature freeze, it&#8217;s time to have a look at some new Javascript goodies for developers:</p>
<ul>
<li>jQuery 1.6.4 and jQuery UI 1.8.16. And that&#8217;s the full UI including widgets and effects. This will make it a lot easier and simpler for plugins using UI components that are not used in core as they will be able to just enqueue whatever they need.<br />
<strong>Note:</strong> there is a known bug/regression in UI Draggable since version 1.8.13. When connecting a draggable item to a sortable container, the HTML ID of the item is removed,<a href="http://core.trac.wordpress.org/ticket/17952"> #17952</a>.</li>
<li>WordPress Editor API. This is an updated API for both TinyMCE and Quicktags that outputs all parts of both editors in the same way as used on the Add / Edit Post screens,<a href="http://core.trac.wordpress.org/ticket/17144"> #17144</a>. Plugins will be able to use the WordPress editor anywhere including the Visual/HTML tabs and the links to upload files and show the media library.</li>
<li>Quicktags refactoring. This was necessary in order to make it fully multi-instance compatible,<a href="http://core.trac.wordpress.org/ticket/16695"> #16695</a>.<br />
<strong>Note:</strong> if your plugin adds a Quicktags button please enhance it to use the new methods in quicktags.js.</li>
<li>New multi-file uploader. <a href="http://www.plupload.com/">Plupload</a> was included as a result ofÂ  Google Summer of Code project,<a href="http://core.trac.wordpress.org/ticket/18206"> #18206</a>. It&#8217;s more stable and has a lot more features as well as chooses the best available interface that the current browser supports: HTML 5, Silverlight or Flash.<br />
<strong>Note:</strong> two actions that were specific to SWFUpload were renamed and there is a new filter &#8216;plupload_init&#8217; that gives access to all initialization options.</li>
<li>Other enhancements: wp_enqueue_script() now works mid-page and prints the late enqueued scripts in the footer<a href="http://core.trac.wordpress.org/ticket/9346"> #9346</a>, wp_localize_script() uses json_encode to properly escape and output all strings,<a href="http://core.trac.wordpress.org/ticket/11520"> #11520</a>.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2011/09/23/javascript-changes-in-3-3/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>New and improved this morning, we have a&#8230;</title>
		<link>http://make.wordpress.org/core/2010/10/22/new-and-improved-this-morning-we-have-a/</link>
		<comments>http://make.wordpress.org/core/2010/10/22/new-and-improved-this-morning-we-have-a/#comments</comments>
		<pubDate>Fri, 22 Oct 2010 12:14:24 +0000</pubDate>
		<dc:creator>Samuel Wood (Otto)</dc:creator>
				<category><![CDATA[status]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[plugin directory]]></category>
		<category><![CDATA[wporg]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2010/10/22/new-and-improved-this-morning-we-have-a/</guid>
		<description><![CDATA[New and improved this morning, we have a two-fer. First, on the extend plugin directory, you may notice some new pie chart fun on the stats tab for each plugin. This shows a percentage breakdown of the versions being actively used by that plugin&#8217;s users. Only slices greater than 1.0% are shown. Secondly, since data [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>New and improved this morning, we have a two-fer.</p>
<p>First, on the extend plugin directory, you may notice some new pie chart fun on the stats tab for each plugin. This shows a percentage breakdown of the versions being actively used by that plugin&#8217;s users. Only slices greater than 1.0% are shown.</p>
<p>Secondly, since data kept in a box is not very useful, there&#8217;s a new API for getting this data. Usage is fairly obvious from just a simple example, which gets the version breakdown of one of my own plugins:</p>
<p><a href="http://api.wordpress.org/stats/plugin/1.0/simple-facebook-connect?callback=demo" rel="nofollow">http://api.wordpress.org/stats/plugin/1.0/simple-facebook-connect?callback=demo</a></p>
<p>The callback parameter is optional, of course, and provided for people who want JSONP usage.</p>
<p>Note that the version data is relatively new, so we don&#8217;t have it for all plugins at present. It will get better as reporting continues. For those interested, it&#8217;s saving the total counts of the version numbers as reported by the plugin update-checks over the last week. Since the data at present is only from one day, it&#8217;s not very accurate. </p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2010/10/22/new-and-improved-this-morning-we-have-a/feed/</wfw:commentRss>
		<slash:comments>64</slash:comments>
		</item>
		<item>
		<title>Previously we&#8217;d talked about putting up&#8230;</title>
		<link>http://make.wordpress.org/core/2010/08/31/previously-wed-talked-about-putting-up/</link>
		<comments>http://make.wordpress.org/core/2010/08/31/previously-wed-talked-about-putting-up/#comments</comments>
		<pubDate>Tue, 31 Aug 2010 22:32:21 +0000</pubDate>
		<dc:creator>Joseph Scott</dc:creator>
				<category><![CDATA[status]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[stats]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2010/08/31/previously-wed-talked-about-putting-up/</guid>
		<description><![CDATA[Previously we&#8217;d talked about putting up a stats page on WordPress.org (WPORG) so that more people could see what was happening. While working on some of the new stats processing code on WPORG I realized that people would likely end up scraping this data for their own uses. That seemed like a waste, so instead [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Previously we&#8217;d talked about putting up a stats page on WordPress.org (WPORG) so that more people could see what was happening.  While working on some of the new stats processing code on WPORG I realized that people would likely end up scraping this data for their own uses.  That seemed like a waste, so instead as a first run the stats numbers are available in JSON format via:</p>
<p><a href="http://api.wordpress.org/stats/wordpress/1.0/" rel="nofollow">http://api.wordpress.org/stats/wordpress/1.0/</a></p>
<p><a href="http://api.wordpress.org/stats/php/1.0/" rel="nofollow">http://api.wordpress.org/stats/php/1.0/</a></p>
<p><a href="http://api.wordpress.org/stats/mysql/1.0/" rel="nofollow">http://api.wordpress.org/stats/mysql/1.0/</a></p>
<p>A few notes about these numbers.  First, they are summary percentages for the previous day (where day is based on GMT).  You&#8217;ll also notice that these numbers don&#8217;t really line up with each other, this is because the system normalizes the version numbers and throws out odd/invalid versions (I was surprised by how many odd version strings there are out there).  As a result each category is best compared to itself, instead of trying to compare PHP with MySQL numbers.</p>
<p>The content type returned for this data is &#8216;application/json&#8217;, your browser may or may not display them correctly.</p>
<p>This is a start, there are more things to be added to this in the future.  One obvious item is support for getting numbers for previous days and date ranges.  Another would be to add some pretty graphs to WPORG to display this data.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2010/08/31/previously-wed-talked-about-putting-up/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Deprecated clean_url() in favor of esc_u&#8230;</title>
		<link>http://make.wordpress.org/core/2009/05/18/deprecated-clean_url-in-favor-of-esc_u/</link>
		<comments>http://make.wordpress.org/core/2009/05/18/deprecated-clean_url-in-favor-of-esc_u/#comments</comments>
		<pubDate>Mon, 18 May 2009 16:54:19 +0000</pubDate>
		<dc:creator>Mark Jaquith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[escaping]]></category>
		<category><![CDATA[esc_url]]></category>
		<category><![CDATA[esc_url_raw]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2009/05/18/deprecated-clean_url-in-favor-of-esc_u/</guid>
		<description><![CDATA[Deprecated clean_url() in favor of esc_url(), and deprecated sanitize_url() in favor of esc_url_raw().]]></description>
				<content:encoded><![CDATA[<p>Deprecated <code>clean_url()</code> in favor of <code>esc_url()</code>, and deprecated <code>sanitize_url()</code> in favor of <code>esc_url_raw()</code>.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2009/05/18/deprecated-clean_url-in-favor-of-esc_u/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Deprecated wp_specialchars() in favor of&#8230;</title>
		<link>http://make.wordpress.org/core/2009/05/18/deprecated-wp_specialchars-in-favor-of/</link>
		<comments>http://make.wordpress.org/core/2009/05/18/deprecated-wp_specialchars-in-favor-of/#comments</comments>
		<pubDate>Mon, 18 May 2009 15:13:40 +0000</pubDate>
		<dc:creator>Mark Jaquith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[escaping]]></category>
		<category><![CDATA[esc_attr]]></category>
		<category><![CDATA[esc_html]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2009/05/18/deprecated-wp_specialchars-in-favor-of/</guid>
		<description><![CDATA[Deprecated wp_specialchars() in favor of esc_html() (also: esc_html__() and esc_html_e()). Using wp_specialchars() with more than one param works for backwards compat. Also, esc_html() (or wp_specialchars() with one param) escapes quotes, just like esc_attr(). This buys security for plugin authors who were mistakenly using a one-param wp_specialchars() call in an HTML attribute. See this wp-hackers message [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Deprecated <code>wp_specialchars()</code> in favor of <code>esc_html()</code> (also: <code>esc_html__()</code> and <code>esc_html_e()</code>). Using <code>wp_specialchars()</code> with more than one param works for backwards compat. Also, <code>esc_html()</code> (or <code>wp_specialchars()</code> with one param) escapes quotes, just like <code>esc_attr()</code>. This buys security for plugin authors who were mistakenly using a  one-param <code>wp_specialchars()</code> call in an HTML attribute. See <a href="http://comox.textdrive.com/pipermail/wp-hackers/2009-May/026242.html">this wp-hackers message</a> for more detail.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2009/05/18/deprecated-wp_specialchars-in-favor-of/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Standardizing and shortening the WP secu&#8230;</title>
		<link>http://make.wordpress.org/core/2009/05/05/standardizing-and-shortening-the-wp-secu/</link>
		<comments>http://make.wordpress.org/core/2009/05/05/standardizing-and-shortening-the-wp-secu/#comments</comments>
		<pubDate>Tue, 05 May 2009 21:16:37 +0000</pubDate>
		<dc:creator>Mark Jaquith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[escaping]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2009/05/05/standardizing-and-shortening-the-wp-secu/</guid>
		<description><![CDATA[Standardizing and shortening the WP security escaping functions. attribute_escape() is now esc_attr() Additionally, you can do attribute escaping and translation in one go. Just add the translation function to the end. Like so: esc_attr__() &#8212; translate and return, attribute-escaped. esc_attr_e() &#8212; translate and echo, attribute-escaped. Will be following up with esc_html (with __() and _e() [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Standardizing and shortening the WP security escaping functions.</p>
<p><code>attribute_escape()</code> is now <code>esc_attr()</code></p>
<p>Additionally, you can do attribute escaping and translation in one go. Just add the translation function to the end. Like so:</p>
<ul>
<li><code>esc_attr__()</code> &#8212; translate and return, attribute-escaped.</li>
<li><code>esc_attr_e()</code> &#8212; translate and echo, attribute-escaped.</li>
</ul>
<p>Will be following up with <code>esc_html</code> (with <code>__()</code> and <code>_e()</code> variants), <code>esc_url()</code>, maybe some more. Will be nice, short, predictable, and allow you do translate/escape in one go without a lot of nested parenthesis.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2009/05/05/standardizing-and-shortening-the-wp-secu/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>New API that allows plugins to add secti &#8230;</title>
		<link>http://make.wordpress.org/core/2008/09/09/new-api-that-allows-plugins-to-add-secti/</link>
		<comments>http://make.wordpress.org/core/2008/09/09/new-api-that-allows-plugins-to-add-secti/#comments</comments>
		<pubDate>Tue, 09 Sep 2008 22:51:04 +0000</pubDate>
		<dc:creator>Ryan Boren</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[plugins]]></category>
		<category><![CDATA[settings]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2008/09/09/new-api-that-allows-plugins-to-add-secti/</guid>
		<description><![CDATA[New API that allows plugins to add sections and fields to settings pages and register new settings along with sanitization callbacks. add_settings_section(), add_settings_field(), register_setting(), unregister_setting()]]></description>
				<content:encoded><![CDATA[<p>New API that allows plugins to add sections and fields to settings pages and register new settings along with sanitization callbacks.  add_settings_section(), add_settings_field(), register_setting(), unregister_setting()</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2008/09/09/new-api-that-allows-plugins-to-add-secti/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>New wp_page_menu() API that creates a me &#8230;</title>
		<link>http://make.wordpress.org/core/2008/09/09/new-wp_page_menu-api-that-creates-a-me/</link>
		<comments>http://make.wordpress.org/core/2008/09/09/new-wp_page_menu-api-that-creates-a-me/#comments</comments>
		<pubDate>Tue, 09 Sep 2008 22:50:04 +0000</pubDate>
		<dc:creator>Ryan Boren</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[templates]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2008/09/09/new-wp_page_menu-api-that-creates-a-me/</guid>
		<description><![CDATA[New wp_page_menu() API that creates a menu of pages. Themes will no longer have to do this for themselves.]]></description>
				<content:encoded><![CDATA[<p>New wp_page_menu() API that creates a menu of pages.  Themes will no longer have to do this for themselves.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2008/09/09/new-wp_page_menu-api-that-creates-a-me/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Avatar support is now baked in.  Themes  &#8230;</title>
		<link>http://make.wordpress.org/core/2008/02/09/avatar-support-is-now-baked-in-themes/</link>
		<comments>http://make.wordpress.org/core/2008/02/09/avatar-support-is-now-baked-in-themes/#comments</comments>
		<pubDate>Sat, 09 Feb 2008 06:53:44 +0000</pubDate>
		<dc:creator>Ryan Boren</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[avatar]]></category>
		<category><![CDATA[themes]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2008/02/09/avatar-support-is-now-baked-in-themes/</guid>
		<description><![CDATA[Avatar support is now baked in. Themes can use get_avatar() to fetch the avatar for an author or commenter.]]></description>
				<content:encoded><![CDATA[<p>Avatar support is now baked in.  Themes can use <a href="http://trac.wordpress.org/ticket/5775">get_avatar()</a> to fetch the avatar for an author or commenter.</p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2008/02/09/avatar-support-is-now-baked-in-themes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New API for adding boxes to edit page: a &#8230;</title>
		<link>http://make.wordpress.org/core/2008/02/08/new-api-for-adding-boxes-to-edit-page-a/</link>
		<comments>http://make.wordpress.org/core/2008/02/08/new-api-for-adding-boxes-to-edit-page-a/#comments</comments>
		<pubDate>Fri, 08 Feb 2008 19:17:30 +0000</pubDate>
		<dc:creator>Ryan Boren</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[API]]></category>

		<guid isPermaLink="false">http://wpdevel.wordpress.com/2008/02/08/new-api-for-adding-boxes-to-edit-page-a/</guid>
		<description><![CDATA[New API for adding boxes to edit page: add_meta_box()]]></description>
				<content:encoded><![CDATA[<p>New API for adding boxes to edit page: <a href="http://trac.wordpress.org/ticket/5798">add_meta_box()</a></p>
]]></content:encoded>
			<wfw:commentRss>http://make.wordpress.org/core/2008/02/08/new-api-for-adding-boxes-to-edit-page-a/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
