O:9:"MagpieRSS":18:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:10:{i:0;a:13:{s:5:"title";s:23:"Event Organizers Unite!";s:4:"link";s:57:"http://wordpress.org/news/2012/07/event-organizers-unite/";s:8:"comments";s:66:"http://wordpress.org/news/2012/07/event-organizers-unite/#comments";s:7:"pubdate";s:31:"Fri, 13 Jul 2012 08:18:15 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:60:"CommunityEventsclassescontributorshackathonsmeetupsWordCamps";s:4:"guid";s:33:"http://wordpress.org/news/?p=2412";s:11:"description";s:388:"I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a [...]";s:7:"content";a:1:{s:7:"encoded";s:3709:"<p>I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a central hub of activity for these folks. Despite the many informal connections between community organizers, we weren&#8217;t taking advantage of the huge existing knowledge base as new organizers stepped up to the plate.</p>
<p>With the creation of <a href="http://make.wordpress.org/events/">this new contributor group</a>, we finally have a way to organize and recognize these kinds of contributions, a clear avenue for feedback and input when it comes to policies around official events, and the opportunity to create even more connections between community organizers through mentorship programs and group projects. I&#8217;m especially excited about the creation of this group because until now the role of community organizer, while one of the most important, has not gotten the same recognition as higher-profile contribution methods such as forum support or core code contribution. That is something I hope this group will change, and the local organizers can be recognized for the community leaders they are.*</p>
<p>If you are the organizer of a local WordCamp, WordPress meetup, etc., head over to <a href="http://make.wordpress.org/events/">http://make.wordpress.org/events/</a> and introduce yourself so we can include you in the fun!</p>
<p>Speaking of meetups, an update on <a href="http://wordpress.org/news/2012/01/year-of-the-meetup/">my last post about meetups</a> is long overdue. With around 500 meetup organizers (and/or potential organizers) responding to my last survey, it took much longer than anticipated to review all the responses. We&#8217;re working now with meetup.com to issue invitations to join a centralized WordPress Meetup account, so if you filled out the form earlier this year, you should be hearing from them soon. The first wave of existing meetup account transfers (for those who opted in) should happen in the next two weeks, with additional waves every 3 months thereafter (and new groups will be able to be created along the way).</p>
<p>The <a href="http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/">contributor summit</a> that is being planned for the end of October also generated hundreds of responses/nominations, so that review process is still happening, but we should be announcing some basic plans and issuing invitations soon.</p>
<p>And finally, it would be impossible to talk about in-person WordPress events without mentioning the upcoming annual <a href="http://2012.sf.wordcamp.org">WordCamp in San Francisco</a>. As the event that represents the worldwide project as a whole, it&#8217;s the perfect time to evaluate where we stand as a project and as a community, to help determine where we go next. If you&#8217;re a WordPress user, developer, or in any way a part of our vast and interconnected ecosystem, please take a moment to fill in the <a href="http://wpsurvey.polldaddy.com/s/wp-2012">2nd annual WordPress survey</a>. It&#8217;s just a couple of questions, and your input would be greatly appreciated. The results of the survey will be announced at <a href="http://2012.sf.wordcamp.org">WSCF</a>, and a report issued shortly thereafter.</p>
<p>Thanks!</p>
<p>*<em> I am also of the firm belief that academic and arts activities should earn varsity letters just like sports teams do &#8212; go mathletes! </em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:62:"http://wordpress.org/news/2012/07/event-organizers-unite/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:388:"I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a [...]";s:12:"atom_content";s:3709:"<p>I&#8217;m happy to announce the formation of a new official contributor group within the WordPress project for the organizers of in-person events that promote WordPress. Though there are hundreds of people around the globe organizing WordCamps, WordPress meetups, hackathons, free classes and the like, since their &#8220;projects&#8221; were all happening locally there was never a central hub of activity for these folks. Despite the many informal connections between community organizers, we weren&#8217;t taking advantage of the huge existing knowledge base as new organizers stepped up to the plate.</p>
<p>With the creation of <a href="http://make.wordpress.org/events/">this new contributor group</a>, we finally have a way to organize and recognize these kinds of contributions, a clear avenue for feedback and input when it comes to policies around official events, and the opportunity to create even more connections between community organizers through mentorship programs and group projects. I&#8217;m especially excited about the creation of this group because until now the role of community organizer, while one of the most important, has not gotten the same recognition as higher-profile contribution methods such as forum support or core code contribution. That is something I hope this group will change, and the local organizers can be recognized for the community leaders they are.*</p>
<p>If you are the organizer of a local WordCamp, WordPress meetup, etc., head over to <a href="http://make.wordpress.org/events/">http://make.wordpress.org/events/</a> and introduce yourself so we can include you in the fun!</p>
<p>Speaking of meetups, an update on <a href="http://wordpress.org/news/2012/01/year-of-the-meetup/">my last post about meetups</a> is long overdue. With around 500 meetup organizers (and/or potential organizers) responding to my last survey, it took much longer than anticipated to review all the responses. We&#8217;re working now with meetup.com to issue invitations to join a centralized WordPress Meetup account, so if you filled out the form earlier this year, you should be hearing from them soon. The first wave of existing meetup account transfers (for those who opted in) should happen in the next two weeks, with additional waves every 3 months thereafter (and new groups will be able to be created along the way).</p>
<p>The <a href="http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/">contributor summit</a> that is being planned for the end of October also generated hundreds of responses/nominations, so that review process is still happening, but we should be announcing some basic plans and issuing invitations soon.</p>
<p>And finally, it would be impossible to talk about in-person WordPress events without mentioning the upcoming annual <a href="http://2012.sf.wordcamp.org">WordCamp in San Francisco</a>. As the event that represents the worldwide project as a whole, it&#8217;s the perfect time to evaluate where we stand as a project and as a community, to help determine where we go next. If you&#8217;re a WordPress user, developer, or in any way a part of our vast and interconnected ecosystem, please take a moment to fill in the <a href="http://wpsurvey.polldaddy.com/s/wp-2012">2nd annual WordPress survey</a>. It&#8217;s just a couple of questions, and your input would be greatly appreciated. The results of the survey will be announced at <a href="http://2012.sf.wordcamp.org">WSCF</a>, and a report issued shortly thereafter.</p>
<p>Thanks!</p>
<p>*<em> I am also of the firm belief that academic and arts activities should earn varsity letters just like sports teams do &#8212; go mathletes! </em></p>
";}i:1;a:13:{s:5:"title";s:48:"WordPress 3.4.1 Maintenance and Security Release";s:4:"link";s:50:"http://wordpress.org/news/2012/06/wordpress-3-4-1/";s:8:"comments";s:59:"http://wordpress.org/news/2012/06/wordpress-3-4-1/#comments";s:7:"pubdate";s:31:"Wed, 27 Jun 2012 19:57:46 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Andrew Nacin";}s:8:"category";s:16:"ReleasesSecurity";s:4:"guid";s:33:"http://wordpress.org/news/?p=2383";s:11:"description";s:379:"WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses 18 bugs with version 3.4, including: Fixes an issue where a theme&#8217;s page templates were sometimes not detected. Addresses problems with some category permalink [...]";s:7:"content";a:1:{s:7:"encoded";s:1585:"<p>WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses <a href="http://core.trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=3.4.1&amp;group=resolution&amp;order=severity&amp;desc=1">18 bugs</a> with version 3.4, including:</p>
<ul>
<li>Fixes an issue where a theme&#8217;s page templates were sometimes not detected.</li>
<li>Addresses problems with some category permalink structures.</li>
<li>Better handling for plugins or themes loading JavaScript incorrectly.</li>
<li>Adds early support for uploading images on iOS 6 devices.</li>
<li>Allows for a technique commonly used by plugins to detect a network-wide activation.</li>
<li>Better compatibility with servers running certain versions of PHP (5.2.4, 5.4) or with uncommon setups (safe mode, open_basedir), which had caused warnings or in some cases prevented emails from being sent.</li>
</ul>
<p>Version 3.4.1 also fixes a few security issues and contains some security hardening. The vulnerabilities included potential information disclosure as well as an bug that affects multisite installs with untrusted users. These issues were discovered and fixed by the WordPress security team.</p>
<p><strong><a href="http://wordpress.org/download/">Download 3.4.1</a> now or visit Dashboard ? Updates in your site admin to update now.</strong></p>
<p><em>Green was a bit green<br />
We have hardened it up some<br />
Update WordPress now</em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:55:"http://wordpress.org/news/2012/06/wordpress-3-4-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:379:"WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses 18 bugs with version 3.4, including: Fixes an issue where a theme&#8217;s page templates were sometimes not detected. Addresses problems with some category permalink [...]";s:12:"atom_content";s:1585:"<p>WordPress 3.4.1 is now available for download. WordPress 3.4 has been a very smooth release, and copies are flying off the shelf &#8212; 3 million downloads in two weeks! This maintenance release addresses <a href="http://core.trac.wordpress.org/query?status=closed&amp;resolution=fixed&amp;milestone=3.4.1&amp;group=resolution&amp;order=severity&amp;desc=1">18 bugs</a> with version 3.4, including:</p>
<ul>
<li>Fixes an issue where a theme&#8217;s page templates were sometimes not detected.</li>
<li>Addresses problems with some category permalink structures.</li>
<li>Better handling for plugins or themes loading JavaScript incorrectly.</li>
<li>Adds early support for uploading images on iOS 6 devices.</li>
<li>Allows for a technique commonly used by plugins to detect a network-wide activation.</li>
<li>Better compatibility with servers running certain versions of PHP (5.2.4, 5.4) or with uncommon setups (safe mode, open_basedir), which had caused warnings or in some cases prevented emails from being sent.</li>
</ul>
<p>Version 3.4.1 also fixes a few security issues and contains some security hardening. The vulnerabilities included potential information disclosure as well as an bug that affects multisite installs with untrusted users. These issues were discovered and fixed by the WordPress security team.</p>
<p><strong><a href="http://wordpress.org/download/">Download 3.4.1</a> now or visit Dashboard ? Updates in your site admin to update now.</strong></p>
<p><em>Green was a bit green<br />
We have hardened it up some<br />
Update WordPress now</em></p>
";}i:2;a:13:{s:5:"title";s:25:"WordPress 3.4 “Green”";s:4:"link";s:40:"http://wordpress.org/news/2012/06/green/";s:8:"comments";s:49:"http://wordpress.org/news/2012/06/green/#comments";s:7:"pubdate";s:31:"Wed, 13 Jun 2012 18:42:40 +0000";s:2:"dc";a:1:{s:7:"creator";s:14:"Matt Mullenweg";}s:8:"category";s:8:"Releases";s:4:"guid";s:33:"http://wordpress.org/news/?p=2334";s:11:"description";s:386:"WordPress 3.4 is here and out the door. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist Grant Green whose soulful simplicity has kept many of us company during this release. This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights: For [...]";s:7:"content";a:1:{s:7:"encoded";s:15280:"<p>WordPress 3.4 is <a href="http://wordpress.org/download/">here and out the door</a>. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist <a href="http://en.wikipedia.org/wiki/Grant_Green">Grant Green</a> whose soulful simplicity has kept many of us company during this release.</p>
<p>This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights:</p>
<div id="v-Gg0EFixV-1" class="video-player"><embed id="v-Gg0EFixV-1-video" src="http://s0.videopress.com/player.swf?v=1.03&amp;guid=Gg0EFixV&amp;isDynamicSeeking=true" type="application/x-shockwave-flash" width="692" height="388" title="Introducing WordPress 3.4 &quot;Green&quot;" wmode="direct" seamlesstabbing="true" allowfullscreen="true" allowscriptaccess="always" overstretch="true"></embed></div>
<h3>For Users</h3>
<p>The biggest change in 3.4 is the <strong>theme customizer</strong> which allows you to play around with various looks and settings for your current theme or one you&#8217;re thinking about switching to without publishing those changes to the whole world. For themes that support it, you can change colors, backgrounds, and of course custom image headers. We have more planned for the customizer down the road.</p>
<p>Throughout the rest of the admin you&#8217;ll notice tweaks to make your everyday life easier. For example, if you have lots of themes we&#8217;ve made it quicker to browse them all at once without paging. We&#8217;ve made it possible to use images from your media library to populate custom headers, and for you to choose the height and width of your header images.</p>
<p>We&#8217;ve expanded our embed support to include tweets: just put a Twitter permalink on its own line in the post editor and we&#8217;ll turn it into a beautiful embedded Tweet. And finally, image captions have been improved to allow HTML, like links, in them.</p>
<h3>For Developers</h3>
<p>There are hundreds of under-the-hood improvements in this release, notably in the XML-RPC, themes, and custom header APIs, and significant performance improvements in WP_Query and the translation system. <a href="http://codex.wordpress.org/Version_3.4">The Codex has a pretty good summary of the developer features</a>, and you can always <a href="http://core.trac.wordpress.org/milestone/3.4">dive into Trac directly</a>.</p>
<p>We&#8217;ve also <a href="http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/">put together a busy developer&#8217;s field guide to the new APIs in 3.4</a>.</p>
<h3>It takes a village</h3>
<p>Here are some of the fine folks who were involved in bringing 3.4 to the world:</p>
<p><a href="http://profiles.wordpress.org/082net">082net</a>, <a href="http://profiles.wordpress.org/aaroncampbell">Aaron D. Campbell</a>, <a href="http://profiles.wordpress.org/kawauso">Adam Harley</a>, <a href="http://profiles.wordpress.org/ajacommerce">AJ Acevedo</a>, <a href="http://profiles.wordpress.org/akshayagarwal">akshayagarwal</a>, <a href="http://profiles.wordpress.org/xknown">Alex Concha</a>, <a href="http://profiles.wordpress.org/alexkingorg">Alex King</a>, <a href="http://profiles.wordpress.org/viper007bond">Alex Mills (Viper007Bond)</a>, <a href="http://profiles.wordpress.org/ampt">ampt</a>, <a href="http://profiles.wordpress.org/sabreuse">Amy Hendrix</a>, <a href="http://profiles.wordpress.org/andrea_r">Andrea Rennick</a>, <a href="http://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/andrewryno">Andrew Ryno</a>, <a href="http://profiles.wordpress.org/andy">Andy Skelton</a>, <a href="http://profiles.wordpress.org/arieputranto">Arie Putranto</a>, <a href="http://profiles.wordpress.org/filosofo">Austin Matzko</a>, <a href="http://profiles.wordpress.org/barry">Barry</a>, <a href="http://profiles.wordpress.org/benchapman">BenChapman</a>, <a href="http://profiles.wordpress.org/husobj">Ben Huson</a>, <a href="http://profiles.wordpress.org/benbalter">Benjamin J. Balter</a>, <a href="http://profiles.wordpress.org/billerickson">Bill Erickson</a>, <a href="http://profiles.wordpress.org/bananastalktome">Billy (bananastalktome)</a>, <a href="http://profiles.wordpress.org/boonebgorges">Boone Gorges</a>, <a href="http://profiles.wordpress.org/camiloclc">camiloclc</a>, <a href="http://profiles.wordpress.org/casben79">casben79</a>, <a href="http://profiles.wordpress.org/caspie">Caspie</a>, <a href="http://profiles.wordpress.org/ceefour">ceefour</a>, <a href="http://profiles.wordpress.org/cheald">cheald</a>, <a href="http://profiles.wordpress.org/chellycat">chellycat</a>, <a href="http://profiles.wordpress.org/chexee">Chelsea Otakan</a>, <a href="http://profiles.wordpress.org/chipbennett">Chip Bennett</a>, <a href="http://profiles.wordpress.org/c3mdigital">Chris Olbekson</a>, <a href="http://profiles.wordpress.org/coenjacobs">Coen Jacobs</a>, <a href="http://profiles.wordpress.org/scribu">Cristi Burc&#259;</a>, <a href="http://profiles.wordpress.org/cyapow">Cyapow</a>, <a href="http://profiles.wordpress.org/djcp">Dan Collis-Puro</a>, <a href="http://profiles.wordpress.org/danielbachhuber">Daniel Bachhuber</a>, <a href="http://profiles.wordpress.org/convissor">Daniel Convissor</a>, <a href="http://profiles.wordpress.org/redsweater">Daniel Jalkut (Red Sweater)</a>, <a href="http://profiles.wordpress.org/daniloercoli">daniloercoli</a>, <a href="http://profiles.wordpress.org/koopersmith">Daryl Koopersmith</a>, <a href="http://profiles.wordpress.org/dgwyer">David Gwyer</a>, <a href="http://profiles.wordpress.org/deltafactory">deltafactory</a>, <a href="http://profiles.wordpress.org/demetris">demetris</a>, <a href="http://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/dllh">dllh</a>, <a href="http://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="http://profiles.wordpress.org/dougwrites">Doug Provencio</a>, <a href="http://profiles.wordpress.org/drewapicture">Drew Jaynes (DrewAPicture)</a>, <a href="http://profiles.wordpress.org/ebababi">ebababi</a>, <a href="http://profiles.wordpress.org/edward-mindreantre">edward-mindreantre</a>, <a href="http://profiles.wordpress.org/emhr">emhr</a>, <a href="http://profiles.wordpress.org/empireoflight">Empireoflight</a>, <a href="http://profiles.wordpress.org/ericlewis">Eric Andrew Lewis</a>, <a href="http://profiles.wordpress.org/ericmann">Eric Mann</a>, <a href="http://profiles.wordpress.org/ejdanderson">Evan Anderson</a>, <a href="http://profiles.wordpress.org/evansolomon">Evan Solomon</a>, <a href="http://profiles.wordpress.org/fredwu">Fred Wu</a>, <a href="http://profiles.wordpress.org/ounziw">Fumito Mizuno</a>, <a href="http://profiles.wordpress.org/garyc40">Gary Cao</a>, <a href="http://profiles.wordpress.org/garyj">Gary Jones</a>, <a href="http://profiles.wordpress.org/gautamgupta">Gautam</a>, <a href="http://profiles.wordpress.org/soulseekah">Gennady Kovshenin</a>, <a href="http://profiles.wordpress.org/mamaduka">George Mamadashvili</a>, <a href="http://profiles.wordpress.org/georgestephanis">George Stephanis</a>, <a href="http://profiles.wordpress.org/webord">Gustavo Bordoni</a>, <a href="http://profiles.wordpress.org/hearvox">hearvox</a>, <a href="http://profiles.wordpress.org/helenyhou">Helen Hou-Sandi</a>, <a href="http://profiles.wordpress.org/hugobaeta">Hugo Baeta</a>, <a href="http://profiles.wordpress.org/iandstewart">Ian Stewart</a>, <a href="http://profiles.wordpress.org/insertvisionhere">insertvisionhere</a>, <a href="http://profiles.wordpress.org/ipstenu">Ipstenu</a>, <a href="http://profiles.wordpress.org/master-jake">Jacob Chappell</a>, <a href="http://profiles.wordpress.org/jane">Jane Wells</a>, <a href="http://profiles.wordpress.org/japh">Japh</a>, <a href="http://profiles.wordpress.org/jaquers">jaquers</a>, <a href="http://profiles.wordpress.org/jarretc">JarretC</a>, <a href="http://profiles.wordpress.org/jeremyclarke">jeremyclarke</a>, <a href="http://profiles.wordpress.org/jeremyfelt">Jeremy Felt</a>, <a href="http://profiles.wordpress.org/jayjdk">Jesper Johansen (Jayjdk)</a>, <a href="http://profiles.wordpress.org/jiehanzheng">Jiehan Zheng</a>, <a href="http://profiles.wordpress.org/intoxstudio">Joachim Jensen (Intox Studio)</a>, <a href="http://profiles.wordpress.org/jkudish">Joachim Kudish (jkudish)</a>, <a href="http://profiles.wordpress.org/johnbillion">John Blackbourn (johnbillion)</a>, <a href="http://profiles.wordpress.org/aldenta">John Ford</a>, <a href="http://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="http://profiles.wordpress.org/duck_">Jon Cave</a>, <a href="http://profiles.wordpress.org/joostdevalk">Joost de Valk</a>, <a href="http://profiles.wordpress.org/koke">Jorge Bernal</a>, <a href="http://profiles.wordpress.org/josephscott">Joseph Scott</a>, <a href="http://profiles.wordpress.org/devesine">Justin</a>, <a href="http://profiles.wordpress.org/justindgivens">Justin Givens</a>, <a href="http://profiles.wordpress.org/trepmal">Kailey Lampert (trepmal)</a>, <a href="http://profiles.wordpress.org/kenan3008">Kenan Dervisevic</a>, <a href="http://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/kobenland">Konstantin Obenland</a>, <a href="http://profiles.wordpress.org/klagraff">Kristopher Lagraff</a>, <a href="http://profiles.wordpress.org/kurtpayne">Kurt Payne</a>, <a href="http://profiles.wordpress.org/lancewillett">Lance Willett</a>, <a href="http://profiles.wordpress.org/lardjo">Lardjo</a>, <a href="http://profiles.wordpress.org/leewillis77">Lee Willis (leewillis77)</a>, <a href="http://profiles.wordpress.org/linuxologos">linuxologos</a>, <a href="http://profiles.wordpress.org/latz">Lutz Schroer</a>, <a href="http://profiles.wordpress.org/settle">Mantas Malcius</a>, <a href="http://profiles.wordpress.org/netweblogic">Marcus</a>, <a href="http://profiles.wordpress.org/markjaquith">Mark Jaquith</a>, <a href="http://profiles.wordpress.org/markoheijnen">Marko Heijnen</a>, <a href="http://profiles.wordpress.org/markauk">Mark Rowatt Anderson</a>, <a href="http://profiles.wordpress.org/matveb">Matias Ventura</a>, <a href="http://profiles.wordpress.org/sivel">Matt Martz</a>, <a href="http://profiles.wordpress.org/mattonomics">mattonomics</a>, <a href="http://profiles.wordpress.org/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/mattwiebe">Matt Wiebe</a>, <a href="http://profiles.wordpress.org/mattyrob">MattyRob</a>, <a href="http://profiles.wordpress.org/maxcutler">Max Cutler</a>, <a href="http://profiles.wordpress.org/merty">Mert Yazicioglu</a>, <a href="http://profiles.wordpress.org/mgolawala">mgolawala</a>, <a href="http://profiles.wordpress.org/mdawaffe">Michael Adams (mdawaffe)</a>, <a href="http://profiles.wordpress.org/tw2113">Michael Beckwith</a>, <a href="http://profiles.wordpress.org/mfields">Michael Fields</a>, <a href="http://profiles.wordpress.org/mikeschinkel">Mike Schinkel</a>, <a href="http://profiles.wordpress.org/dh-shredder">Mike Schroder</a>, <a href="http://profiles.wordpress.org/toppa">Mike Toppa</a>, <a href="http://profiles.wordpress.org/dimadin">Milan Dinic</a>, <a href="http://profiles.wordpress.org/mitchoyoshitaka">mitcho (Michael Yoshitaka Erlewine)</a>, <a href="http://profiles.wordpress.org/batmoo">Mohammad Jangda</a>, <a href="http://profiles.wordpress.org/mrtorrent">mrtorrent</a>, <a href="http://profiles.wordpress.org/namely">Name.ly</a>, <a href="http://profiles.wordpress.org/Nao">Naoko McCracken</a>, <a href="http://profiles.wordpress.org/alex-ye">Nashwan Doaqan</a>, <a href="http://profiles.wordpress.org/niallkennedy">Niall Kennedy</a>, <a href="http://profiles.wordpress.org/nikolayyordanov">Nikolay Yordanov</a>, <a href="http://profiles.wordpress.org/norocketsurgeon">norocketsurgeon</a>, <a href="http://profiles.wordpress.org/npetetin">npetetin</a>, <a href="http://profiles.wordpress.org/nunomorgadinho">Nuno Morgadinho</a>, <a href="http://profiles.wordpress.org/ocollet">Olivier Collet</a>, <a href="http://profiles.wordpress.org/pbiron">Paul Biron</a>, <a href="http://profiles.wordpress.org/pavelevap">pavelevap</a>, <a href="http://profiles.wordpress.org/petemall">Pete Mall</a>, <a href="http://profiles.wordpress.org/westi">Peter Westwood</a>, <a href="http://profiles.wordpress.org/pishmishy">pishmishy</a>, <a href="http://profiles.wordpress.org/nprasath002">Prasath Nadarajah</a>, <a href="http://profiles.wordpress.org/prettyboymp">prettyboymp</a>, <a href="http://profiles.wordpress.org/ptahdunbar">Ptah Dunbar</a>, <a href="http://profiles.wordpress.org/pw201">pw201</a>, <a href="http://profiles.wordpress.org/ramiy">Rami Yushuvaev</a>, <a href="http://profiles.wordpress.org/rarst">Rarst</a>, <a href="http://profiles.wordpress.org/arena">RENAUT</a>, <a href="http://profiles.wordpress.org/greuben">Reuben Gunday</a>, <a href="http://profiles.wordpress.org/roscius">Roscius</a>, <a href="http://profiles.wordpress.org/rosshanney">Ross Hanney</a>, <a href="http://profiles.wordpress.org/russellwwest">russellwwest</a>, <a href="http://profiles.wordpress.org/ryan">Ryan Boren</a>, <a href="http://profiles.wordpress.org/ryanduff">Ryan Duff</a>, <a href="http://profiles.wordpress.org/rmccue">Ryan McCue</a>, <a href="http://profiles.wordpress.org/zeo">Safirul Alredha</a>, <a href="http://profiles.wordpress.org/solarissmoke">Samir Shah</a>, <a href="http://profiles.wordpress.org/otto42">Samuel &#8220;Otto&#8221; Wood</a>, <a href="http://profiles.wordpress.org/tenpura">Seisuke Kuraishi</a>, <a href="http://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/simonwheatley">Simon Wheatley</a>, <a href="http://profiles.wordpress.org/sirzooro">sirzooro</a>, <a href="http://profiles.wordpress.org/sksmatt">sksmatt</a>, <a href="http://profiles.wordpress.org/sushkov">Stas Su&#537;kov</a>, <a href="http://profiles.wordpress.org/stephdau">Stephane Daury (stephdau)</a>, <a href="http://profiles.wordpress.org/tamlyn">tamlyn</a>, <a href="http://profiles.wordpress.org/griffinjt">Thomas Griffin</a>, <a href="http://profiles.wordpress.org/tott">Thorsten Ott</a>, <a href="http://profiles.wordpress.org/tobiasbg">TobiasBg</a>, <a href="http://profiles.wordpress.org/tomauger">Tom Auger</a>, <a href="http://profiles.wordpress.org/skithund">Toni Viemero</a>, <a href="http://profiles.wordpress.org/transom">transom</a>, <a href="http://profiles.wordpress.org/sorich87">Ulrich Sossou</a>, <a href="http://profiles.wordpress.org/utkarsh">Utkarsh Kukreti</a>, <a href="http://profiles.wordpress.org/wojtekszkutnik">Wojtek Szkutnik</a>, <a href="http://profiles.wordpress.org/wonderslug">wonderslug</a>, <a href="http://profiles.wordpress.org/xibe">Xavier Borderie</a>, <a href="http://profiles.wordpress.org/yoavf">Yoav Farhi</a>, <a href="http://profiles.wordpress.org/thezman84">Zach &#8220;The Z Man&#8221; Abernathy</a>, <a href="http://profiles.wordpress.org/tollmanz">Zack Tollman</a>, <a href="http://profiles.wordpress.org/vanillalounge">Ze Fontainhas</a>, and <a href="http://profiles.wordpress.org/zx2c4">zx2c4</a>.</p>
<p>See you next time!</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:45:"http://wordpress.org/news/2012/06/green/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:386:"WordPress 3.4 is here and out the door. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist Grant Green whose soulful simplicity has kept many of us company during this release. This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights: For [...]";s:12:"atom_content";s:15280:"<p>WordPress 3.4 is <a href="http://wordpress.org/download/">here and out the door</a>. We&#8217;ve dubbed this release &#8220;Green&#8221; in honor of guitarist <a href="http://en.wikipedia.org/wiki/Grant_Green">Grant Green</a> whose soulful simplicity has kept many of us company during this release.</p>
<p>This release includes significant improvements to theme customization, custom headers, Twitter embeds, and image captions &#8212; here&#8217;s a short clip with the highlights:</p>
<div id="v-Gg0EFixV-1" class="video-player"><embed id="v-Gg0EFixV-1-video" src="http://s0.videopress.com/player.swf?v=1.03&amp;guid=Gg0EFixV&amp;isDynamicSeeking=true" type="application/x-shockwave-flash" width="692" height="388" title="Introducing WordPress 3.4 &quot;Green&quot;" wmode="direct" seamlesstabbing="true" allowfullscreen="true" allowscriptaccess="always" overstretch="true"></embed></div>
<h3>For Users</h3>
<p>The biggest change in 3.4 is the <strong>theme customizer</strong> which allows you to play around with various looks and settings for your current theme or one you&#8217;re thinking about switching to without publishing those changes to the whole world. For themes that support it, you can change colors, backgrounds, and of course custom image headers. We have more planned for the customizer down the road.</p>
<p>Throughout the rest of the admin you&#8217;ll notice tweaks to make your everyday life easier. For example, if you have lots of themes we&#8217;ve made it quicker to browse them all at once without paging. We&#8217;ve made it possible to use images from your media library to populate custom headers, and for you to choose the height and width of your header images.</p>
<p>We&#8217;ve expanded our embed support to include tweets: just put a Twitter permalink on its own line in the post editor and we&#8217;ll turn it into a beautiful embedded Tweet. And finally, image captions have been improved to allow HTML, like links, in them.</p>
<h3>For Developers</h3>
<p>There are hundreds of under-the-hood improvements in this release, notably in the XML-RPC, themes, and custom header APIs, and significant performance improvements in WP_Query and the translation system. <a href="http://codex.wordpress.org/Version_3.4">The Codex has a pretty good summary of the developer features</a>, and you can always <a href="http://core.trac.wordpress.org/milestone/3.4">dive into Trac directly</a>.</p>
<p>We&#8217;ve also <a href="http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/">put together a busy developer&#8217;s field guide to the new APIs in 3.4</a>.</p>
<h3>It takes a village</h3>
<p>Here are some of the fine folks who were involved in bringing 3.4 to the world:</p>
<p><a href="http://profiles.wordpress.org/082net">082net</a>, <a href="http://profiles.wordpress.org/aaroncampbell">Aaron D. Campbell</a>, <a href="http://profiles.wordpress.org/kawauso">Adam Harley</a>, <a href="http://profiles.wordpress.org/ajacommerce">AJ Acevedo</a>, <a href="http://profiles.wordpress.org/akshayagarwal">akshayagarwal</a>, <a href="http://profiles.wordpress.org/xknown">Alex Concha</a>, <a href="http://profiles.wordpress.org/alexkingorg">Alex King</a>, <a href="http://profiles.wordpress.org/viper007bond">Alex Mills (Viper007Bond)</a>, <a href="http://profiles.wordpress.org/ampt">ampt</a>, <a href="http://profiles.wordpress.org/sabreuse">Amy Hendrix</a>, <a href="http://profiles.wordpress.org/andrea_r">Andrea Rennick</a>, <a href="http://profiles.wordpress.org/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/andrewryno">Andrew Ryno</a>, <a href="http://profiles.wordpress.org/andy">Andy Skelton</a>, <a href="http://profiles.wordpress.org/arieputranto">Arie Putranto</a>, <a href="http://profiles.wordpress.org/filosofo">Austin Matzko</a>, <a href="http://profiles.wordpress.org/barry">Barry</a>, <a href="http://profiles.wordpress.org/benchapman">BenChapman</a>, <a href="http://profiles.wordpress.org/husobj">Ben Huson</a>, <a href="http://profiles.wordpress.org/benbalter">Benjamin J. Balter</a>, <a href="http://profiles.wordpress.org/billerickson">Bill Erickson</a>, <a href="http://profiles.wordpress.org/bananastalktome">Billy (bananastalktome)</a>, <a href="http://profiles.wordpress.org/boonebgorges">Boone Gorges</a>, <a href="http://profiles.wordpress.org/camiloclc">camiloclc</a>, <a href="http://profiles.wordpress.org/casben79">casben79</a>, <a href="http://profiles.wordpress.org/caspie">Caspie</a>, <a href="http://profiles.wordpress.org/ceefour">ceefour</a>, <a href="http://profiles.wordpress.org/cheald">cheald</a>, <a href="http://profiles.wordpress.org/chellycat">chellycat</a>, <a href="http://profiles.wordpress.org/chexee">Chelsea Otakan</a>, <a href="http://profiles.wordpress.org/chipbennett">Chip Bennett</a>, <a href="http://profiles.wordpress.org/c3mdigital">Chris Olbekson</a>, <a href="http://profiles.wordpress.org/coenjacobs">Coen Jacobs</a>, <a href="http://profiles.wordpress.org/scribu">Cristi Burc&#259;</a>, <a href="http://profiles.wordpress.org/cyapow">Cyapow</a>, <a href="http://profiles.wordpress.org/djcp">Dan Collis-Puro</a>, <a href="http://profiles.wordpress.org/danielbachhuber">Daniel Bachhuber</a>, <a href="http://profiles.wordpress.org/convissor">Daniel Convissor</a>, <a href="http://profiles.wordpress.org/redsweater">Daniel Jalkut (Red Sweater)</a>, <a href="http://profiles.wordpress.org/daniloercoli">daniloercoli</a>, <a href="http://profiles.wordpress.org/koopersmith">Daryl Koopersmith</a>, <a href="http://profiles.wordpress.org/dgwyer">David Gwyer</a>, <a href="http://profiles.wordpress.org/deltafactory">deltafactory</a>, <a href="http://profiles.wordpress.org/demetris">demetris</a>, <a href="http://profiles.wordpress.org/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/dllh">dllh</a>, <a href="http://profiles.wordpress.org/ocean90">Dominik Schilling</a>, <a href="http://profiles.wordpress.org/dougwrites">Doug Provencio</a>, <a href="http://profiles.wordpress.org/drewapicture">Drew Jaynes (DrewAPicture)</a>, <a href="http://profiles.wordpress.org/ebababi">ebababi</a>, <a href="http://profiles.wordpress.org/edward-mindreantre">edward-mindreantre</a>, <a href="http://profiles.wordpress.org/emhr">emhr</a>, <a href="http://profiles.wordpress.org/empireoflight">Empireoflight</a>, <a href="http://profiles.wordpress.org/ericlewis">Eric Andrew Lewis</a>, <a href="http://profiles.wordpress.org/ericmann">Eric Mann</a>, <a href="http://profiles.wordpress.org/ejdanderson">Evan Anderson</a>, <a href="http://profiles.wordpress.org/evansolomon">Evan Solomon</a>, <a href="http://profiles.wordpress.org/fredwu">Fred Wu</a>, <a href="http://profiles.wordpress.org/ounziw">Fumito Mizuno</a>, <a href="http://profiles.wordpress.org/garyc40">Gary Cao</a>, <a href="http://profiles.wordpress.org/garyj">Gary Jones</a>, <a href="http://profiles.wordpress.org/gautamgupta">Gautam</a>, <a href="http://profiles.wordpress.org/soulseekah">Gennady Kovshenin</a>, <a href="http://profiles.wordpress.org/mamaduka">George Mamadashvili</a>, <a href="http://profiles.wordpress.org/georgestephanis">George Stephanis</a>, <a href="http://profiles.wordpress.org/webord">Gustavo Bordoni</a>, <a href="http://profiles.wordpress.org/hearvox">hearvox</a>, <a href="http://profiles.wordpress.org/helenyhou">Helen Hou-Sandi</a>, <a href="http://profiles.wordpress.org/hugobaeta">Hugo Baeta</a>, <a href="http://profiles.wordpress.org/iandstewart">Ian Stewart</a>, <a href="http://profiles.wordpress.org/insertvisionhere">insertvisionhere</a>, <a href="http://profiles.wordpress.org/ipstenu">Ipstenu</a>, <a href="http://profiles.wordpress.org/master-jake">Jacob Chappell</a>, <a href="http://profiles.wordpress.org/jane">Jane Wells</a>, <a href="http://profiles.wordpress.org/japh">Japh</a>, <a href="http://profiles.wordpress.org/jaquers">jaquers</a>, <a href="http://profiles.wordpress.org/jarretc">JarretC</a>, <a href="http://profiles.wordpress.org/jeremyclarke">jeremyclarke</a>, <a href="http://profiles.wordpress.org/jeremyfelt">Jeremy Felt</a>, <a href="http://profiles.wordpress.org/jayjdk">Jesper Johansen (Jayjdk)</a>, <a href="http://profiles.wordpress.org/jiehanzheng">Jiehan Zheng</a>, <a href="http://profiles.wordpress.org/intoxstudio">Joachim Jensen (Intox Studio)</a>, <a href="http://profiles.wordpress.org/jkudish">Joachim Kudish (jkudish)</a>, <a href="http://profiles.wordpress.org/johnbillion">John Blackbourn (johnbillion)</a>, <a href="http://profiles.wordpress.org/aldenta">John Ford</a>, <a href="http://profiles.wordpress.org/johnjamesjacoby">John James Jacoby</a>, <a href="http://profiles.wordpress.org/duck_">Jon Cave</a>, <a href="http://profiles.wordpress.org/joostdevalk">Joost de Valk</a>, <a href="http://profiles.wordpress.org/koke">Jorge Bernal</a>, <a href="http://profiles.wordpress.org/josephscott">Joseph Scott</a>, <a href="http://profiles.wordpress.org/devesine">Justin</a>, <a href="http://profiles.wordpress.org/justindgivens">Justin Givens</a>, <a href="http://profiles.wordpress.org/trepmal">Kailey Lampert (trepmal)</a>, <a href="http://profiles.wordpress.org/kenan3008">Kenan Dervisevic</a>, <a href="http://profiles.wordpress.org/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/kobenland">Konstantin Obenland</a>, <a href="http://profiles.wordpress.org/klagraff">Kristopher Lagraff</a>, <a href="http://profiles.wordpress.org/kurtpayne">Kurt Payne</a>, <a href="http://profiles.wordpress.org/lancewillett">Lance Willett</a>, <a href="http://profiles.wordpress.org/lardjo">Lardjo</a>, <a href="http://profiles.wordpress.org/leewillis77">Lee Willis (leewillis77)</a>, <a href="http://profiles.wordpress.org/linuxologos">linuxologos</a>, <a href="http://profiles.wordpress.org/latz">Lutz Schroer</a>, <a href="http://profiles.wordpress.org/settle">Mantas Malcius</a>, <a href="http://profiles.wordpress.org/netweblogic">Marcus</a>, <a href="http://profiles.wordpress.org/markjaquith">Mark Jaquith</a>, <a href="http://profiles.wordpress.org/markoheijnen">Marko Heijnen</a>, <a href="http://profiles.wordpress.org/markauk">Mark Rowatt Anderson</a>, <a href="http://profiles.wordpress.org/matveb">Matias Ventura</a>, <a href="http://profiles.wordpress.org/sivel">Matt Martz</a>, <a href="http://profiles.wordpress.org/mattonomics">mattonomics</a>, <a href="http://profiles.wordpress.org/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/mattwiebe">Matt Wiebe</a>, <a href="http://profiles.wordpress.org/mattyrob">MattyRob</a>, <a href="http://profiles.wordpress.org/maxcutler">Max Cutler</a>, <a href="http://profiles.wordpress.org/merty">Mert Yazicioglu</a>, <a href="http://profiles.wordpress.org/mgolawala">mgolawala</a>, <a href="http://profiles.wordpress.org/mdawaffe">Michael Adams (mdawaffe)</a>, <a href="http://profiles.wordpress.org/tw2113">Michael Beckwith</a>, <a href="http://profiles.wordpress.org/mfields">Michael Fields</a>, <a href="http://profiles.wordpress.org/mikeschinkel">Mike Schinkel</a>, <a href="http://profiles.wordpress.org/dh-shredder">Mike Schroder</a>, <a href="http://profiles.wordpress.org/toppa">Mike Toppa</a>, <a href="http://profiles.wordpress.org/dimadin">Milan Dinic</a>, <a href="http://profiles.wordpress.org/mitchoyoshitaka">mitcho (Michael Yoshitaka Erlewine)</a>, <a href="http://profiles.wordpress.org/batmoo">Mohammad Jangda</a>, <a href="http://profiles.wordpress.org/mrtorrent">mrtorrent</a>, <a href="http://profiles.wordpress.org/namely">Name.ly</a>, <a href="http://profiles.wordpress.org/Nao">Naoko McCracken</a>, <a href="http://profiles.wordpress.org/alex-ye">Nashwan Doaqan</a>, <a href="http://profiles.wordpress.org/niallkennedy">Niall Kennedy</a>, <a href="http://profiles.wordpress.org/nikolayyordanov">Nikolay Yordanov</a>, <a href="http://profiles.wordpress.org/norocketsurgeon">norocketsurgeon</a>, <a href="http://profiles.wordpress.org/npetetin">npetetin</a>, <a href="http://profiles.wordpress.org/nunomorgadinho">Nuno Morgadinho</a>, <a href="http://profiles.wordpress.org/ocollet">Olivier Collet</a>, <a href="http://profiles.wordpress.org/pbiron">Paul Biron</a>, <a href="http://profiles.wordpress.org/pavelevap">pavelevap</a>, <a href="http://profiles.wordpress.org/petemall">Pete Mall</a>, <a href="http://profiles.wordpress.org/westi">Peter Westwood</a>, <a href="http://profiles.wordpress.org/pishmishy">pishmishy</a>, <a href="http://profiles.wordpress.org/nprasath002">Prasath Nadarajah</a>, <a href="http://profiles.wordpress.org/prettyboymp">prettyboymp</a>, <a href="http://profiles.wordpress.org/ptahdunbar">Ptah Dunbar</a>, <a href="http://profiles.wordpress.org/pw201">pw201</a>, <a href="http://profiles.wordpress.org/ramiy">Rami Yushuvaev</a>, <a href="http://profiles.wordpress.org/rarst">Rarst</a>, <a href="http://profiles.wordpress.org/arena">RENAUT</a>, <a href="http://profiles.wordpress.org/greuben">Reuben Gunday</a>, <a href="http://profiles.wordpress.org/roscius">Roscius</a>, <a href="http://profiles.wordpress.org/rosshanney">Ross Hanney</a>, <a href="http://profiles.wordpress.org/russellwwest">russellwwest</a>, <a href="http://profiles.wordpress.org/ryan">Ryan Boren</a>, <a href="http://profiles.wordpress.org/ryanduff">Ryan Duff</a>, <a href="http://profiles.wordpress.org/rmccue">Ryan McCue</a>, <a href="http://profiles.wordpress.org/zeo">Safirul Alredha</a>, <a href="http://profiles.wordpress.org/solarissmoke">Samir Shah</a>, <a href="http://profiles.wordpress.org/otto42">Samuel &#8220;Otto&#8221; Wood</a>, <a href="http://profiles.wordpress.org/tenpura">Seisuke Kuraishi</a>, <a href="http://profiles.wordpress.org/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/simonwheatley">Simon Wheatley</a>, <a href="http://profiles.wordpress.org/sirzooro">sirzooro</a>, <a href="http://profiles.wordpress.org/sksmatt">sksmatt</a>, <a href="http://profiles.wordpress.org/sushkov">Stas Su&#537;kov</a>, <a href="http://profiles.wordpress.org/stephdau">Stephane Daury (stephdau)</a>, <a href="http://profiles.wordpress.org/tamlyn">tamlyn</a>, <a href="http://profiles.wordpress.org/griffinjt">Thomas Griffin</a>, <a href="http://profiles.wordpress.org/tott">Thorsten Ott</a>, <a href="http://profiles.wordpress.org/tobiasbg">TobiasBg</a>, <a href="http://profiles.wordpress.org/tomauger">Tom Auger</a>, <a href="http://profiles.wordpress.org/skithund">Toni Viemero</a>, <a href="http://profiles.wordpress.org/transom">transom</a>, <a href="http://profiles.wordpress.org/sorich87">Ulrich Sossou</a>, <a href="http://profiles.wordpress.org/utkarsh">Utkarsh Kukreti</a>, <a href="http://profiles.wordpress.org/wojtekszkutnik">Wojtek Szkutnik</a>, <a href="http://profiles.wordpress.org/wonderslug">wonderslug</a>, <a href="http://profiles.wordpress.org/xibe">Xavier Borderie</a>, <a href="http://profiles.wordpress.org/yoavf">Yoav Farhi</a>, <a href="http://profiles.wordpress.org/thezman84">Zach &#8220;The Z Man&#8221; Abernathy</a>, <a href="http://profiles.wordpress.org/tollmanz">Zack Tollman</a>, <a href="http://profiles.wordpress.org/vanillalounge">Ze Fontainhas</a>, and <a href="http://profiles.wordpress.org/zx2c4">zx2c4</a>.</p>
<p>See you next time!</p>
";}i:3;a:13:{s:5:"title";s:33:"WordPress 3.4 Release Candidate 3";s:4:"link";s:68:"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-3/";s:8:"comments";s:77:"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-3/#comments";s:7:"pubdate";s:31:"Tue, 12 Jun 2012 00:30:14 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Andrew Nacin";}s:8:"category";s:18:"DevelopmentTesting";s:4:"guid";s:33:"http://wordpress.org/news/?p=2326";s:11:"description";s:325:"The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds. There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, [...]";s:7:"content";a:1:{s:7:"encoded";s:1376:"<p>The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds.</p>
<p>There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, you can post to the <a href="http://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums, or file a bug report on <a href="http://core.trac.wordpress.org/">WordPress Trac</a>.</p>
<p>To test WordPress 3.4, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="http://wordpress.org/wordpress-3.4-RC3.zip">download the release candidate here</a> (zip). Be sure to visit <strong><img style="vertical-align: text-top" src="http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png" alt="" /> ? About</strong> for an updated list of features and under-the-hood changes. As a reminder: We’ve published some resources on the <a href="http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/">development blog</a> to help plugin and theme developers prepare.</p>
<p><em>The new live preview<br />
Nearing perfection, and yet?<br />
Not yet. RC3</em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:73:"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-3/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:325:"The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds. There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, [...]";s:12:"atom_content";s:1376:"<p>The third release candidate for WordPress 3.4 is now available. Since RC2, we&#8217;ve fixed a few lingering issues with the new live preview feature, as well as with custom headers and backgrounds.</p>
<p>There are no remaining issues, and we plan to release 3.4 in the coming days. But if you think you&#8217;ve found a bug, you can post to the <a href="http://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums, or file a bug report on <a href="http://core.trac.wordpress.org/">WordPress Trac</a>.</p>
<p>To test WordPress 3.4, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="http://wordpress.org/wordpress-3.4-RC3.zip">download the release candidate here</a> (zip). Be sure to visit <strong><img style="vertical-align: text-top" src="http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png" alt="" /> ? About</strong> for an updated list of features and under-the-hood changes. As a reminder: We’ve published some resources on the <a href="http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/">development blog</a> to help plugin and theme developers prepare.</p>
<p><em>The new live preview<br />
Nearing perfection, and yet?<br />
Not yet. RC3</em></p>
";}i:4;a:13:{s:5:"title";s:33:"WordPress 3.4 Release Candidate 2";s:4:"link";s:68:"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-2/";s:8:"comments";s:77:"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-2/#comments";s:7:"pubdate";s:31:"Thu, 07 Jun 2012 02:48:58 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Andrew Nacin";}s:8:"category";s:26:"DevelopmentReleasesTesting";s:4:"guid";s:33:"http://wordpress.org/news/?p=2318";s:11:"description";s:331:"The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a few dozen final changes. Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely your last chance to test your plugins and themes to find any compatibility issues before the final release. [...]";s:7:"content";a:1:{s:7:"encoded";s:1713:"<p>The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a <a href="http://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=21018&amp;stop_rev=20949&amp;limit=500">few dozen final changes</a>.</p>
<p>Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely <strong>your last chance to test your plugins and themes to find any compatibility issues before the final release</strong>. We&#8217;ve published some resources on the <a href="http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/">development blog</a> to help you prepare.</p>
<p>If you think you’ve found a bug, you can post to the <a href="http://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a reproducible bug report, <a href="http://core.trac.wordpress.org/">file one on WordPress Trac</a>. Known issues that crop up will be listed <a href="http://core.trac.wordpress.org/report/6">here</a>, but we&#8217;re hoping for a quiet few days so we can get some great features into your hands next week!</p>
<p>To test WordPress 3.4, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="http://wordpress.org/wordpress-3.4-RC2.zip">download the release candidate here</a> (zip). Be sure to visit <strong><img src="http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png" alt="" style="vertical-align:text-top" /> &rarr; About</strong> for an updated list of features and under-the-hood changes.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:73:"http://wordpress.org/news/2012/06/wordpress-3-4-release-candidate-2/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:331:"The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a few dozen final changes. Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely your last chance to test your plugins and themes to find any compatibility issues before the final release. [...]";s:12:"atom_content";s:1713:"<p>The second release candidate for WordPress 3.4 is now available. Since RC1, we&#8217;ve made a <a href="http://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=21018&amp;stop_rev=20949&amp;limit=500">few dozen final changes</a>.</p>
<p>Our goal is to release WordPress 3.4 early next week, so plugin and theme authors, this is likely <strong>your last chance to test your plugins and themes to find any compatibility issues before the final release</strong>. We&#8217;ve published some resources on the <a href="http://wpdevel.wordpress.com/2012/06/07/wordpress-3-4-field-guide-for-developers/">development blog</a> to help you prepare.</p>
<p>If you think you’ve found a bug, you can post to the <a href="http://wordpress.org/support/forum/alphabeta">Alpha/Beta area</a> in the support forums. Or, if you’re comfortable writing a reproducible bug report, <a href="http://core.trac.wordpress.org/">file one on WordPress Trac</a>. Known issues that crop up will be listed <a href="http://core.trac.wordpress.org/report/6">here</a>, but we&#8217;re hoping for a quiet few days so we can get some great features into your hands next week!</p>
<p>To test WordPress 3.4, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you’ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="http://wordpress.org/wordpress-3.4-RC2.zip">download the release candidate here</a> (zip). Be sure to visit <strong><img src="http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png" alt="" style="vertical-align:text-top" /> &rarr; About</strong> for an updated list of features and under-the-hood changes.</p>
";}i:5;a:13:{s:5:"title";s:31:"WordPress 3.4 Release Candidate";s:4:"link";s:66:"http://wordpress.org/news/2012/05/wordpress-3-4-release-candidate/";s:8:"comments";s:75:"http://wordpress.org/news/2012/05/wordpress-3-4-release-candidate/#comments";s:7:"pubdate";s:31:"Sun, 27 May 2012 17:18:30 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Andrew Nacin";}s:8:"category";s:26:"DevelopmentReleasesTesting";s:4:"guid";s:33:"http://wordpress.org/news/?p=2303";s:11:"description";s:130:"The first release candidate (RC1) for WordPress 3.4 is now available. If you haven’t tested WordPress 3.4 yet, now is the time! ";s:7:"content";a:1:{s:7:"encoded";s:1871:"<p>The first release candidate (RC1) for WordPress 3.4 is now available.</p>
<p>An RC comes after the beta period and before final release. We think we&#8217;re done, but with millions of users and thousands of plugins and themes, it&#8217;s possible we&#8217;ve missed something. So if you haven’t tested WordPress 3.4 yet, now is the time! Please though, not on your live site unless you’re adventurous.</p>
<p>With more than <a href="http://core.trac.wordpress.org/milestone/3.4">500 tickets closed</a>, there are quite a few changes. <strong>Plugin and theme authors,</strong> please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.</p>
<p>If you are testing the release candidate and think you&#8217;ve found a bug, please post to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a>. If any known issues crop up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>.</p>
<p>To test WordPress 3.4, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you&#8217;ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="http://wordpress.org/wordpress-3.4-RC1.zip">download the release candidate here (zip)</a>.</p>
<p>If you&#8217;d like to know which levers to pull in your testing, visit the About page (<strong><img src="http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png" alt="" style="vertical-align:text-top" /> &rarr; About</strong> in the toolbar) and check out the list of features! You&#8217;ll definitely want to try the live theme previews.</p>
<p><strong>Bonus:</strong> Happy birthday WordPress &#8212; <a href="http://wordpress.org/news/2003/05/wordpress-now-available/">nine years old</a> today.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:71:"http://wordpress.org/news/2012/05/wordpress-3-4-release-candidate/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:130:"The first release candidate (RC1) for WordPress 3.4 is now available. If you haven’t tested WordPress 3.4 yet, now is the time! ";s:12:"atom_content";s:1871:"<p>The first release candidate (RC1) for WordPress 3.4 is now available.</p>
<p>An RC comes after the beta period and before final release. We think we&#8217;re done, but with millions of users and thousands of plugins and themes, it&#8217;s possible we&#8217;ve missed something. So if you haven’t tested WordPress 3.4 yet, now is the time! Please though, not on your live site unless you’re adventurous.</p>
<p>With more than <a href="http://core.trac.wordpress.org/milestone/3.4">500 tickets closed</a>, there are quite a few changes. <strong>Plugin and theme authors,</strong> please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.</p>
<p>If you are testing the release candidate and think you&#8217;ve found a bug, please post to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a>. If any known issues crop up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>.</p>
<p>To test WordPress 3.4, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin (you&#8217;ll want &#8220;bleeding edge nightlies&#8221;). Or you can <a href="http://wordpress.org/wordpress-3.4-RC1.zip">download the release candidate here (zip)</a>.</p>
<p>If you&#8217;d like to know which levers to pull in your testing, visit the About page (<strong><img src="http://wordpress.org/wp-content/themes/twentyten/images/wordpress.png" alt="" style="vertical-align:text-top" /> &rarr; About</strong> in the toolbar) and check out the list of features! You&#8217;ll definitely want to try the live theme previews.</p>
<p><strong>Bonus:</strong> Happy birthday WordPress &#8212; <a href="http://wordpress.org/news/2003/05/wordpress-now-available/">nine years old</a> today.</p>
";}i:6;a:13:{s:5:"title";s:26:"Plugin Directory Refreshed";s:4:"link";s:52:"http://wordpress.org/news/2012/05/plugins-refreshed/";s:8:"comments";s:61:"http://wordpress.org/news/2012/05/plugins-refreshed/#comments";s:7:"pubdate";s:31:"Sat, 19 May 2012 18:56:27 +0000";s:2:"dc";a:1:{s:7:"creator";s:14:"Matt Mullenweg";}s:8:"category";s:4:"Meta";s:4:"guid";s:33:"http://wordpress.org/news/?p=2291";s:11:"description";s:333:"Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over 19,000 plugins listed and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. [...]";s:7:"content";a:1:{s:7:"encoded";s:3324:"<p>Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over <a href="http://wordpress.org/extend/plugins/">19,000 plugins listed</a> and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. Here&#8217;s a quick before and after snapshot you can zoom in on to see a visual overview of some of the changes:</p>
<p><a href="http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png"><img src="http://s2.wp.com/imgpress?resize=690,350&amp;url=http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png&amp;unsharpmask=80,0.5,3" alt="" /></a></p>
<p>Our first focus was around improving the discussion and support around plugins.</p>
<p>You&#8217;ll now notice that threads about a plugin are pulled directly into a &#8220;support&#8221; tab on the plugin page &#8212; each plugin has its own forum. We&#8217;ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you&#8217;re using. And finally to show how active and well-supported a plugin is, you can see  &#8221;16 of 75 support threads in the last two weeks have been resolved.&#8221; Finally, if you&#8217;re logged in you get access to the new &#8220;favorites&#8221; feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!</p>
<p>If you&#8217;re a plugin author, we&#8217;ve started with a short threshold (2 weeks) for the resolved stats so it&#8217;s easy to catch up and stay on top of it. (It&#8217;ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.</p>
<p>We&#8217;ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:</p>
<ul>
<li>&#8220;Plugin headers&#8221; or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.</li>
<li>You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn&#8217;t yours. There is no better way to follow the development of your favorite plugins. There&#8217;s nothing like the smell of fresh changesets in the morning.</li>
<li>Behind the scenes, we&#8217;ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.</li>
</ul>
<p>All of this will continue to evolve as we get feedback and see usage, but we&#8217;re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ &#8212; it imparts magical coding powers.)</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:57:"http://wordpress.org/news/2012/05/plugins-refreshed/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:333:"Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over 19,000 plugins listed and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. [...]";s:12:"atom_content";s:3324:"<p>Been hanging out with a few WordPress.org hackers &#8212; Scott, Nacin, and Otto &#8212; the last few days in a BBQ-fueled haze of hacking to make plugin directory better. There are over <a href="http://wordpress.org/extend/plugins/">19,000 plugins listed</a> and they&#8217;re really the heart and soul of WordPress for many people, so they deserve a little tender loving care. Here&#8217;s a quick before and after snapshot you can zoom in on to see a visual overview of some of the changes:</p>
<p><a href="http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png"><img src="http://s2.wp.com/imgpress?resize=690,350&amp;url=http://wpdotorg.files.wordpress.com/2012/05/contact-form-7.png&amp;unsharpmask=80,0.5,3" alt="" /></a></p>
<p>Our first focus was around improving the discussion and support around plugins.</p>
<p>You&#8217;ll now notice that threads about a plugin are pulled directly into a &#8220;support&#8221; tab on the plugin page &#8212; each plugin has its own forum. We&#8217;ve made authors much more prominent and with bigger Gravatars and better placement, so you can get a sense of who made the plugin you&#8217;re using. And finally to show how active and well-supported a plugin is, you can see  &#8221;16 of 75 support threads in the last two weeks have been resolved.&#8221; Finally, if you&#8217;re logged in you get access to the new &#8220;favorites&#8221; feature that lets you mark the plugins you use the most so you can share them on your profile page and find them quickly later. We soft-launched favorites a few days ago and there have already been 2,000 saved!</p>
<p>If you&#8217;re a plugin author, we&#8217;ve started with a short threshold (2 weeks) for the resolved stats so it&#8217;s easy to catch up and stay on top of it. (It&#8217;ll eventually go to two months.) You also now have the ability to set stickies on your plugin forum to put FAQs or important information at the top, and of course any person you put as a committer on the plugin will have moderation access. People on the forum tag will see your custom header and links to the other resources attached to your plugin.</p>
<p>We&#8217;ve tightened up the styling a bit on the forums and plugin pages, though still some cleanups to do there. Some older improvements you might have missed, but are still useful for users and developers alike:</p>
<ul>
<li>&#8220;Plugin headers&#8221; or those cool graphics you see at the top of plugin pages have really taken off, there are over 1,600 active now.</li>
<li>You can now subscribe to get an email whenever a commit is made to a plugin repository even if it isn&#8217;t yours. There is no better way to follow the development of your favorite plugins. There&#8217;s nothing like the smell of fresh changesets in the morning.</li>
<li>Behind the scenes, we&#8217;ve dramatically ramped up proactive scanning of the entire repository to help authors fix security and other problems they might not even know about yet. The quality level of the repo has gone way, way up.</li>
</ul>
<p>All of this will continue to evolve as we get feedback and see usage, but we&#8217;re happy to have been able to make some key improvements in just a few days while hanging out in Memphis. (This is why WordCamps usually have BBQ &#8212; it imparts magical coding powers.)</p>
";}i:7;a:13:{s:5:"title";s:47:"Calling All Contributors: Community Summit 2012";s:4:"link";s:81:"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/";s:8:"comments";s:90:"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/#comments";s:7:"pubdate";s:31:"Tue, 15 May 2012 22:36:46 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:15:"CommunityEvents";s:4:"guid";s:33:"http://wordpress.org/news/?p=2278";s:11:"description";s:334:"Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend [...]";s:7:"content";a:1:{s:7:"encoded";s:5345:"<p>Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending <a title="WordCamp Central" href="http://wordcamp.org">WordCamps</a> and local <a title="WordPress on Meetup.com" href="http://wordpress.meetup.com/">WordPress meetups</a> (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I&#8217;m aiming a little higher and shooting for a full-on contributor/community summit.</p>
<p>Core code isn&#8217;t the only way to contribute to the WordPress project. We have an active <a title="Theme Review Team blog" href="http://make.wordpress.org/themes/">theme review team</a>, <a href="http://wordpress.org/support/">support forum</a> volunteers, people writing <a href="http://codex.wordpress.org/Main_Page">documentation</a>, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we&#8217;ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.</p>
<p>In addition to bringing together the active contributor team reps to work together, I think it&#8217;s important to include community members who don&#8217;t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!</p>
<p>Taking a cue from events with limited availability like <a title="AdaCamp" href="http://dc.adacamp.org/">AdaCamp</a> (attendance) and the <a title="jQuery Conference" href="http://events.jquery.org/2012/sf/">jQuery conference</a> (speaker roster), I want you to <a title="Nomination survey" href="http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations">nominate people and/or WordPress-based businesses to participate in the summit</a>. Yes, you can nominate yourself.* You can nominate up to 10 additional people &#8212; be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there&#8217;s a theme or hosting company (for example) that you think should be there, you don&#8217;t need to go looking for employee names. This nomination process will hopefully ensure that we don&#8217;t overlook someone who is making a difference in our community when it comes time to issue invitations.</p>
<p>Nominations will be open for a week, after which <a href="http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations">the survey</a> will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at <a href="http://wordpress.tv">WordPress.tv</a>. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you&#8217;re thinking to yourself that maybe now&#8217;s the perfect time to start <a href="http://codex.wordpress.org/Contributing_to_WordPress">contributing time to the WordPress project</a>, good thinking! In the meantime, if you want to weigh in, <a href="http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations">fill in the community summit nomination form</a>. Thanks, and wish us luck!</p>
<p><em>* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.</em></p>
<p><em>** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.</em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:86:"http://wordpress.org/news/2012/05/calling-all-contributors-community-summit-2012/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:334:"Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending WordCamps and local WordPress meetups (which are awesome and you should try to attend [...]";s:12:"atom_content";s:5345:"<p>Each year, the WordPress core development team meets in person for a week to work together and discuss the vision for WordPress in the coming year. As annual events go, it&#8217;s easily my favorite. Don&#8217;t get me wrong, I love attending <a title="WordCamp Central" href="http://wordcamp.org">WordCamps</a> and local <a title="WordPress on Meetup.com" href="http://wordpress.meetup.com/">WordPress meetups</a> (which are awesome and you should try to attend if you are able), but at the core team meetup, the focus on working together and getting things done is unique, as is the experience of every person in the room being so highly qualified. This year, instead of just planning a core team meetup, I&#8217;m aiming a little higher and shooting for a full-on contributor/community summit.</p>
<p>Core code isn&#8217;t the only way to contribute to the WordPress project. We have an active <a title="Theme Review Team blog" href="http://make.wordpress.org/themes/">theme review team</a>, <a href="http://wordpress.org/support/">support forum</a> volunteers, people writing <a href="http://codex.wordpress.org/Main_Page">documentation</a>, plugin managers, community event organizers, translators, and more. The teams have been siloed for too long, so we&#8217;ve recently begun the process of bringing them together by having teams elect representatives to facilitate more communication between the contributor groups. These reps will form the nucleus of the contributor summit now being planned for a long weekend at the end of October in Tybee Island, GA. This is completely different from a WordCamp. It will be a combination of co-working, unconference, and discussions among the project leaders, and participation will be by invitation.</p>
<p>In addition to bringing together the active contributor team reps to work together, I think it&#8217;s important to include community members who don&#8217;t fall into that category (at least not yet!). Successful WordPress-based business, authors of popular plugins and themes, and people using WordPress in unexpected but intriguing ways should have a place at the table, too. That said, part of the magic of the core team meetup is the small size; it allows every voice not only to be heard, but to engage. Since this is my first attempt at bringing together so many groups and points of view, I want to try and keep it small enough to retain that personal atmosphere while at the same time ensuring that the best possible mix of people and businesses in the WordPress ecosystem is represented. This is where you come in!</p>
<p>Taking a cue from events with limited availability like <a title="AdaCamp" href="http://dc.adacamp.org/">AdaCamp</a> (attendance) and the <a title="jQuery Conference" href="http://events.jquery.org/2012/sf/">jQuery conference</a> (speaker roster), I want you to <a title="Nomination survey" href="http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations">nominate people and/or WordPress-based businesses to participate in the summit</a>. Yes, you can nominate yourself.* You can nominate up to 10 additional people &#8212; be prepared to provide URLs and the reason you think they should participate. You can also nominate up to 10 WordPress-based businesses without naming individual people, so if there&#8217;s a theme or hosting company (for example) that you think should be there, you don&#8217;t need to go looking for employee names. This nomination process will hopefully ensure that we don&#8217;t overlook someone who is making a difference in our community when it comes time to issue invitations.</p>
<p>Nominations will be open for a week, after which <a href="http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations">the survey</a> will be closed and the process of analyzing the results** will begin. The nominations process will lead to invitations in June, confirmations in July, planning in August and September, and the summit itself in October. Hopefully we can stream and/or record some of the activity to share online at <a href="http://wordpress.tv">WordPress.tv</a>. Additional invitations may be extended up until the event if there are people/businesses that become more active in the community. If you&#8217;re thinking to yourself that maybe now&#8217;s the perfect time to start <a href="http://codex.wordpress.org/Contributing_to_WordPress">contributing time to the WordPress project</a>, good thinking! In the meantime, if you want to weigh in, <a href="http://wordpressdotorg.polldaddy.com/s/2012-community-summit-nominations">fill in the community summit nomination form</a>. Thanks, and wish us luck!</p>
<p><em>* Nominating yourself: Do nominate yourself if you fall into one of the categories described in the post above, or if you believe that you have a unique point of view. Please do not nominate yourself if you just think it would be cool to hang out with this group. This is a working event, and everyone is expected to bring something special to the table.</em></p>
<p><em>** I (and/or a helpful community volunteer) will sift through the nominations and compile a shortlist of the most-nominated people/businesses and the most intriguing underdogs. This list will be reviewed by the summit planning committee (made up of team reps) to create the invitation list.</em></p>
";}i:8;a:13:{s:5:"title";s:20:"WordPress 3.4 Beta 4";s:4:"link";s:55:"http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/";s:8:"comments";s:64:"http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/#comments";s:7:"pubdate";s:31:"Thu, 03 May 2012 02:52:28 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:33:"http://wordpress.org/news/?p=2273";s:11:"description";s:123:"Less bugs, more polish, the same beta disclaimers. Download, test, report bugs. Thanks much. /ryan #thewholebrevitything";s:7:"content";a:1:{s:7:"encoded";s:190:"<p>Less bugs, more polish, the same beta disclaimers. <a href="http://wordpress.org/wordpress-3.4-beta4.zip">Download</a>, test, report bugs. Thanks much. /ryan #thewholebrevitything</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:123:"Less bugs, more polish, the same beta disclaimers. Download, test, report bugs. Thanks much. /ryan #thewholebrevitything";s:12:"atom_content";s:190:"<p>Less bugs, more polish, the same beta disclaimers. <a href="http://wordpress.org/wordpress-3.4-beta4.zip">Download</a>, test, report bugs. Thanks much. /ryan #thewholebrevitything</p>
";}i:9;a:13:{s:5:"title";s:42:"WordPress 3.3.2 (and WordPress 3.4 Beta 3)";s:4:"link";s:50:"http://wordpress.org/news/2012/04/wordpress-3-3-2/";s:8:"comments";s:59:"http://wordpress.org/news/2012/04/wordpress-3-3-2/#comments";s:7:"pubdate";s:31:"Fri, 20 Apr 2012 15:10:37 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Andrew Nacin";}s:8:"category";s:27:"DevelopmentReleasesSecurity";s:4:"guid";s:33:"http://wordpress.org/news/?p=2262";s:11:"description";s:384:"WordPress 3.3.2 is available now and is a security update for all previous versions. Three external libraries included in WordPress received security updates: Plupload (version 1.5.4), which WordPress uses for uploading media. SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins. SWFObject, which WordPress previously used to embed [...]";s:7:"content";a:1:{s:7:"encoded";s:3345:"<p><a href="http://wordpress.org/download/">WordPress 3.3.2</a> is available now and is a security update for all previous versions.</p>
<p>Three external libraries included in WordPress received security updates:</p>
<ul>
<li>Plupload (version 1.5.4), which WordPress uses for uploading media.</li>
<li>SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins.</li>
<li>SWFObject, which WordPress previously used to embed Flash content, and may still be in use by plugins and themes.</li>
</ul>
<p>Thanks to <a href="https://nealpoole.com/blog/">Neal Poole</a> and <a href="http://greywhind.wordpress.com/">Nathan Partlan</a> for <a href="http://codex.wordpress.org/FAQ_Security">responsibly disclosing</a> the bugs in Plupload and SWFUpload, and <a href="http://mars.iti.pk.edu.pl/~grucha/">Szymon Gruszecki</a> for a separate bug in SWFUpload.</p>
<p>WordPress 3.3.2 also addresses:</p>
<ul>
<li>Limited privilege escalation where a site administrator could deactivate network-wide plugins when running a WordPress network under particular circumstances, disclosed by <a href="http://joncave.co.uk/">Jon Cave</a> of our WordPress core security team, and <a href="http://sixohthree.com/">Adam Backstrom</a>.</li>
<li>Cross-site scripting vulnerability when making URLs clickable, by Jon Cave.</li>
<li>Cross-site scripting vulnerabilities in redirects after posting comments in older browsers, and when filtering URLs. Thanks to <a href="http://www.sneaked.net/">Mauro Gentile</a> for responsibly disclosing these issues to the security team.</li>
</ul>
<p>These issues were fixed by the WordPress core security team. Five other bugs were also fixed in version 3.3.2. Consult the <a href="http://core.trac.wordpress.org/log/branches/3.3?rev=20552&amp;stop_rev=20087">change log</a> for more details.</p>
<p><a href="http://wordpress.org/download/">Download WordPress 3.3.2</a> or update now from the Dashboard ? Updates menu in your site&#8217;s admin area.</p>
<hr />
<h3>WordPress 3.4 Beta 3 also available</h3>
<p>Our development of WordPress 3.4 development continues. Today we are proud to release Beta 3 for testing. <a href="http://core.trac.wordpress.org/log/trunk?rev=20552&amp;stop_rev=20450">Nearly 90 changes</a> have been made since Beta 2, released 9 days ago. (We are aiming for a beta every week.)</p>
<p>This is still beta software, so <strong>we don&#8217;t recommend that you use it on production sites</strong>. But if you&#8217;re a plugin developer, a theme developer, or a site administrator, <strong>you should be running this on your test environments</strong> and <a href="http://codex.wordpress.org/Reporting_Bugs">reporting any bugs</a> you find. (See the <a href="http://core.trac.wordpress.org/report/5">known issues here</a>.) If you&#8217;re a WordPress user who wants to open your presents early, take advantage of WordPress&#8217;s famous 5-minute install and spin up a secondary test site. <a href="http://wordpress.org/support/forum/alphabeta">Let us know what you think</a>!</p>
<p>Version 3.4 Beta 3 includes all of the fixes included in version 3.3.2. <a href="http://wordpress.org/wordpress-3.4-beta3.zip">Download WordPress 3.4 Beta 3</a> or use the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:55:"http://wordpress.org/news/2012/04/wordpress-3-3-2/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:384:"WordPress 3.3.2 is available now and is a security update for all previous versions. Three external libraries included in WordPress received security updates: Plupload (version 1.5.4), which WordPress uses for uploading media. SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins. SWFObject, which WordPress previously used to embed [...]";s:12:"atom_content";s:3345:"<p><a href="http://wordpress.org/download/">WordPress 3.3.2</a> is available now and is a security update for all previous versions.</p>
<p>Three external libraries included in WordPress received security updates:</p>
<ul>
<li>Plupload (version 1.5.4), which WordPress uses for uploading media.</li>
<li>SWFUpload, which WordPress previously used for uploading media, and may still be in use by plugins.</li>
<li>SWFObject, which WordPress previously used to embed Flash content, and may still be in use by plugins and themes.</li>
</ul>
<p>Thanks to <a href="https://nealpoole.com/blog/">Neal Poole</a> and <a href="http://greywhind.wordpress.com/">Nathan Partlan</a> for <a href="http://codex.wordpress.org/FAQ_Security">responsibly disclosing</a> the bugs in Plupload and SWFUpload, and <a href="http://mars.iti.pk.edu.pl/~grucha/">Szymon Gruszecki</a> for a separate bug in SWFUpload.</p>
<p>WordPress 3.3.2 also addresses:</p>
<ul>
<li>Limited privilege escalation where a site administrator could deactivate network-wide plugins when running a WordPress network under particular circumstances, disclosed by <a href="http://joncave.co.uk/">Jon Cave</a> of our WordPress core security team, and <a href="http://sixohthree.com/">Adam Backstrom</a>.</li>
<li>Cross-site scripting vulnerability when making URLs clickable, by Jon Cave.</li>
<li>Cross-site scripting vulnerabilities in redirects after posting comments in older browsers, and when filtering URLs. Thanks to <a href="http://www.sneaked.net/">Mauro Gentile</a> for responsibly disclosing these issues to the security team.</li>
</ul>
<p>These issues were fixed by the WordPress core security team. Five other bugs were also fixed in version 3.3.2. Consult the <a href="http://core.trac.wordpress.org/log/branches/3.3?rev=20552&amp;stop_rev=20087">change log</a> for more details.</p>
<p><a href="http://wordpress.org/download/">Download WordPress 3.3.2</a> or update now from the Dashboard ? Updates menu in your site&#8217;s admin area.</p>
<hr />
<h3>WordPress 3.4 Beta 3 also available</h3>
<p>Our development of WordPress 3.4 development continues. Today we are proud to release Beta 3 for testing. <a href="http://core.trac.wordpress.org/log/trunk?rev=20552&amp;stop_rev=20450">Nearly 90 changes</a> have been made since Beta 2, released 9 days ago. (We are aiming for a beta every week.)</p>
<p>This is still beta software, so <strong>we don&#8217;t recommend that you use it on production sites</strong>. But if you&#8217;re a plugin developer, a theme developer, or a site administrator, <strong>you should be running this on your test environments</strong> and <a href="http://codex.wordpress.org/Reporting_Bugs">reporting any bugs</a> you find. (See the <a href="http://core.trac.wordpress.org/report/5">known issues here</a>.) If you&#8217;re a WordPress user who wants to open your presents early, take advantage of WordPress&#8217;s famous 5-minute install and spin up a secondary test site. <a href="http://wordpress.org/support/forum/alphabeta">Let us know what you think</a>!</p>
<p>Version 3.4 Beta 3 includes all of the fixes included in version 3.3.2. <a href="http://wordpress.org/wordpress-3.4-beta3.zip">Download WordPress 3.4 Beta 3</a> or use the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin.</p>
";}}s:7:"channel";a:8:{s:5:"title";s:14:"WordPress News";s:4:"link";s:25:"http://wordpress.org/news";s:11:"description";s:14:"WordPress News";s:13:"lastbuilddate";s:31:"Fri, 13 Jul 2012 08:18:15 +0000";s:8:"language";s:5:"en-US";s:2:"sy";a:2:{s:12:"updateperiod";s:6:"hourly";s:15:"updatefrequency";s:1:"1";}s:9:"generator";s:39:"http://wordpress.org/?v=3.5-alpha-21360";s:7:"tagline";s:14:"WordPress News";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}s:13:"last_modified";s:31:"Fri, 13 Jul 2012 08:18:15 GMT
";}