CINXE.COM

<?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>WordPress News</title> <atom:link href="http://wordpress.org/news/feed/" rel="self" type="application/rss+xml" /> <link>http://wordpress.org/news</link> <description>WordPress News</description> <lastBuildDate>Sat, 16 Jul 2011 21:32:34 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3-aortic-dissection</generator> <item> <title>Best WordCamp Speakers?</title> <link>http://wordpress.org/news/2011/07/best-wordcamp-speakers/</link> <comments>http://wordpress.org/news/2011/07/best-wordcamp-speakers/#comments</comments> <pubDate>Sat, 16 Jul 2011 21:32:34 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <category><![CDATA[WordCamp]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2000</guid> <description><![CDATA[As we complete speaker selection for the annual WordPress conference (a.k.a. WordCamp San Francisco), it’s clear that even though there were more than 200 speaker applications, many great WordCamp speakers did not apply. No fear! We will seek them out to make sure that WordCamp SF has a fantastic lineup, including people who didn’t apply [...]]]></description> <content:encoded><![CDATA[As we complete speaker selection for <a href="http://2011.sf.wordcamp.org/">the annual WordPress conference (a.k.a. WordCamp San Francisco)</a>, it’s clear that even though there were more than 200 speaker applications, many great WordCamp speakers did not apply. No fear! We will seek them out to make sure that WordCamp SF has a fantastic lineup, including people who didn’t apply (too shy? who knows?) but have wowed local crowds at previous WordCamps. This is about as basic a survey as there is. Tell us the three best WordCamp presentations you saw in the past year or so. For each, give the presenters name, the topic (exact title not necessary) and which WordCamp it was at (important). Example: 1. Joe Shmoe, Using the Loop, WordCamp Sheboygan 2011 2. Jane Doe, Top 5 WordPress Plugins, WordCamp La Mancha 2010 3. Lee Smith, Your First Core Patch, WordCamp Atlantis 2011 That’s it. We don’t need your name or any info at all, just your three top speaker votes. We’ll take a look at the people with the most votes, and consider them for WCSF if they’re not already in the application pool. Thanks for your help in making this year’s conference better and more WordPressy than ever. <img src='http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> <a href="http://wordcampcentral.polldaddy.com/s/best-2010-2011-wordcamp-speakers-so-far">Vote Now!</a> P.S. <a href="http://2011.sf.wordcamp.org/get-tickets/">Have you bought your tickets yet</a>? ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/07/best-wordcamp-speakers/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.2.1</title> <link>http://wordpress.org/news/2011/07/wordpress-3-2-1/</link> <comments>http://wordpress.org/news/2011/07/wordpress-3-2-1/#comments</comments> <pubDate>Tue, 12 Jul 2011 19:49:06 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Releases]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1982</guid> <description><![CDATA[After more than a million downloads of WordPress 3.2, we’re now releasing WordPress 3.2.1 into the wild. This maintenance release fixes a server incompatibility related to JSON that’s unfortunately affected some of you, as well as a few other fixes in the new dashboard design and the Twenty Eleven theme. If you’ve already updated to [...]]]></description> <content:encoded><![CDATA[After more than a million downloads of WordPress 3.2, we’re now releasing <a href="http://wordpress.org/download/">WordPress 3.2.1</a> into the wild. This maintenance release fixes a server incompatibility related to JSON that’s unfortunately affected some of you, as well as a few other fixes in the new dashboard design and the Twenty Eleven theme. If you’ve already updated to 3.2, then this update will be even faster than usual, thanks to the new feature in 3.2 that only updates files that have been changed, rather than replacing all the files in your installation. For a full list of fixes, view the <a href="http://core.trac.wordpress.org/log/branches/3.2/?rev=18436&stop_rev=18398">changelog</a> the list of <a href="http://core.trac.wordpress.org/query?status=closed&group=resolution&milestone=3.2.1">tickets</a>. Our release haiku: JSON, the admin A little bit tidier Edge cases covered <a href="http://wordpress.org/download/">Download 3.2.1</a> or update now from the Dashboard → Updates menu in your site’s admin area. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/07/wordpress-3-2-1/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.2 now available</title> <link>http://wordpress.org/news/2011/07/gershwin/</link> <comments>http://wordpress.org/news/2011/07/gershwin/#comments</comments> <pubDate>Mon, 04 Jul 2011 21:07:06 +0000</pubDate> <dc:creator>Matt Mullenweg</dc:creator> <category><![CDATA[Releases]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1924</guid> <description><![CDATA[Here in the U.S. we are observing Independence Day, and I can’t think of a more fitting way to mark a day that celebrates freedom than by releasing more free software to help democratize publishing around the globe. I’m excited to announce that WordPress 3.2 is now available to the world, both as an update in [...]]]></description> <content:encoded><![CDATA[Here in the U.S. we are observing Independence Day, and I can’t think of a more fitting way to mark a day that celebrates freedom than by releasing more free software to help democratize publishing around the globe. I’m excited to announce that WordPress 3.2 is now available to the world, both as an update in your dashboard and a <a href="http://wordpress.org/">download on WordPress.org</a>. Version 3.2 is our fifteenth major release of WordPress and comes just four months after 3.1 (which coincidentally just passed the 15 million download mark this morning), reflecting the growing speed of development in the WordPress community and our dedication to getting improvements in your hands as soon as possible. We’re dedicating this release to noted composer and pianist <a href="http://en.wikipedia.org/wiki/George_Gershwin">George Gershwin</a>. Before we get to the release, in anticipation of the State of the Word speech at the upcoming <a href="http://2011.sf.wordcamp.org/">WordCamp San Francisco</a> (the annual WordPress conference) we’re doing a survey or census of the WordPress world. If you have a moment, <a href="http://wpsurvey.polldaddy.com/s/wp-2011">please fill out this survey</a> and we’ll share what we learn by publishing the aggregate results in August. The focus for this release was making WordPress faster and lighter. The first thing you’ll notice when you log in to 3.2 is a refreshed dashboard design that tightens the typography, design, and code behind the admin. (Rhapsody in Grey?) If you’re starting a new blog, you’ll also appreciate the fully HTML5 new Twenty Eleven theme, fulfilling our plan to replace the default theme every year. Start writing your first post in our redesigned post editor and venture to the full-screen button in the editing toolbar to enter the new distraction-free writing or zen mode, my personal favorite feature of the release. All of the widgets, menus, buttons, and interface elements fade away to allow you to compose and edit your thoughts in a completely clean environment conducive to writing, but when your mouse strays to the top of the screen your most-used shortcuts are right there where you need them. (I like to press F11 to take my browser full-screen, getting rid of even the OS chrome.) <embed src="http://v.wordpress.com/ac07H291" type="application/x-shockwave-flash" width="600" height="337" allowscriptaccess="always" allowfullscreen="true" wmode="transparent"></embed> Under the hood there have been a number of improvements, not the least of which is the streamlining enabled by our <a href="http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/">previously announced plan</a> of retiring support for PHP4, older versions of MySQL, and legacy browsers like IE6, which allows us to take advantage of more features enabled by new technologies. The admin bar has a few more shortcuts to your most commonly-used actions. On the comment moderation screen, the new approve & reply feature speeds up your conversation management. You’ll notice in your first update after 3.2 that we’ll only be updating the files that have changed with each new release instead of every file in your WordPress installation, which makes updates significantly faster on all hosting platforms. There are also some fun new theme features shown off by Twenty Eleven, like the ability to have multiple rotating header images to highlight all of your favorite photos. There is way more, like our new freedoms and credits screens (linked from your dashboard footer), so for the full story check out the <a href="http://codex.wordpress.org/Version_3.2">Codex page on 3.2</a> or the <a href="http://core.trac.wordpress.org/milestone/3.2">Trac milestone which includes the 400+ tickets closed in this release</a>. <h3>A Community Effort</h3> We now finally have a credits page inside of WordPress itself (though a cool revision is coming in 3.3), but for posterity let’s give a round of applause to these fine folks who contributed to 3.2: <a href="http://profiles.wordpress.org/users/technosailor">Aaron Brazell</a>, <a href="http://profiles.wordpress.org/users/aaroncampbell">Aaron Campbell</a>, <a href="http://profiles.wordpress.org/users/jorbin">Aaron Jorbin</a>, <a href="http://profiles.wordpress.org/users/kawauso">Adam Harley</a>, <a href="http://profiles.wordpress.org/users/xknown">Alex Concha</a>, <a href="http://profiles.wordpress.org/users/ampt">ampt</a>, <a href="http://profiles.wordpress.org/users/nacin">Andrew Nacin</a>, <a href="http://profiles.wordpress.org/users/azaozz">Andrew Ozz</a>, <a href="http://profiles.wordpress.org/users/andrewryno">andrewryno</a>, <a href="http://profiles.wordpress.org/users/andy">andy</a>, <a href="http://profiles.wordpress.org/users/filosofo">Austin Matzko</a>, <a href="http://profiles.wordpress.org/users/benchapman">BenChapman</a>, <a href="http://profiles.wordpress.org/users/empireoflight">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/users/bluntelk">bluntelk</a>, <a href="http://profiles.wordpress.org/users/boonebgorges">Boone Gorges</a>, <a href="http://profiles.wordpress.org/users/cnorris23">Brandon Allen</a>, <a href="http://profiles.wordpress.org/users/brandonburke">Brandon Burke</a>, <a href="http://profiles.wordpress.org/users/caspie">Caspie</a>, <a href="http://profiles.wordpress.org/users/cfinke">cfinke</a>, <a href="http://profiles.wordpress.org/users/charlesclarkson">charlesclarkson</a>, <a href="http://profiles.wordpress.org/users/chexee">chexee</a>, <a href="http://profiles.wordpress.org/users/coffee2code">coffee2code</a>, <a href="http://profiles.wordpress.org/users/scribu">Cristi Burcă</a>, <a href="http://profiles.wordpress.org/users/daniloercoli">daniloercoli</a>, <a href="http://profiles.wordpress.org/users/koopersmith">Daryl Koopersmith</a>, <a href="http://profiles.wordpress.org/users/dcowgill">David Cowgill</a>, <a href="http://profiles.wordpress.org/users/jdtrower">David Trower</a>, <a href="http://profiles.wordpress.org/users/demetris">demetris</a>, <a href="http://profiles.wordpress.org/users/devinreams">Devin Reams</a>, <a href="http://profiles.wordpress.org/users/dd32">Dion Hulse</a>, <a href="http://profiles.wordpress.org/users/dllh">dllh</a>, <a href="http://profiles.wordpress.org/users/ocean90">Dominik Schilling</a>, <a href="http://profiles.wordpress.org/users/dougwrites">Doug Provencio</a>, <a href="http://profiles.wordpress.org/users/dvwallin">dvwallin</a>, <a href="http://profiles.wordpress.org/users/cyberhobo">Dylan Kuhn</a>, <a href="http://profiles.wordpress.org/users/ericmann">Eric Mann</a>, <a href="http://profiles.wordpress.org/users/fabifott">fabifott</a>, <a href="http://profiles.wordpress.org/users/peaceablewhale">Franklin Tse</a>, <a href="http://profiles.wordpress.org/users/frumph">Frumph</a>, <a href="http://profiles.wordpress.org/users/garyc40">garyc40</a>, <a href="http://profiles.wordpress.org/users/blepoxp">Glenn Ansley</a>, <a href="http://profiles.wordpress.org/users/guyn">guyn</a>, <a href="http://profiles.wordpress.org/users/hakre">hakre</a>, <a href="http://profiles.wordpress.org/users/hebbet">hebbet</a>, <a href="http://profiles.wordpress.org/users/helenyhou">Helen Hou-Sandi</a>, <a href="http://profiles.wordpress.org/users/hew">hew</a>, <a href="http://profiles.wordpress.org/users/holizz">holizz</a>, <a href="http://profiles.wordpress.org/users/iandstewart">Ian Stewart</a>, <a href="http://profiles.wordpress.org/users/jacobwg">Jacob Gillespie</a>, <a href="http://profiles.wordpress.org/users/jane">Jane Wells</a>, <a href="http://profiles.wordpress.org/users/jayjdk">Jayjdk</a>, <a href="http://profiles.wordpress.org/users/jfarthing84">Jeff Farthing</a>, <a href="http://profiles.wordpress.org/users/jkudish">Joachim Kudish</a>, <a href="http://profiles.wordpress.org/users/joelhardi">joelhardi</a>, <a href="http://profiles.wordpress.org/users/johnbillion">John Blackbourn</a>, <a href="http://profiles.wordpress.org/users/aldenta">John Ford</a>, <a href="http://profiles.wordpress.org/users/johnjamesjacoby">John James Jacoby</a>, <a href="http://profiles.wordpress.org/users/johnonolan">JohnONolan</a>, <a href="http://profiles.wordpress.org/users/duck_">Jon Cave</a>, <a href="http://profiles.wordpress.org/users/joostdevalk">joostdevalk</a>, <a href="http://profiles.wordpress.org/users/koke">Jorge Bernal</a>, <a href="http://profiles.wordpress.org/users/josephscott">Joseph Scott</a>, <a href="http://profiles.wordpress.org/users/jtsternberg">Justin Sternberg</a>, <a href="http://profiles.wordpress.org/users/greenshady">Justin Tadlock</a>, <a href="http://profiles.wordpress.org/users/kevinb">kevinB</a>, <a href="http://profiles.wordpress.org/users/knutsp">Knut Sparhell</a>, <a href="http://profiles.wordpress.org/users/kovshenin">kovshenin</a>, <a href="http://profiles.wordpress.org/users/tenpura">Kuraishi</a>, <a href="http://profiles.wordpress.org/users/lancewillett">Lance Willett</a>, <a href="http://profiles.wordpress.org/users/linuxologos">linuxologos</a>, <a href="http://profiles.wordpress.org/users/lloydbudd">lloydbudd</a>, <a href="http://profiles.wordpress.org/users/ldebrouwer">Luc De Brouwer</a>, <a href="http://profiles.wordpress.org/users/marcis20">marcis20</a>, <a href="http://profiles.wordpress.org/users/markjaquith">Mark Jaquith</a>, <a href="http://profiles.wordpress.org/users/markmcwilliams">Mark McWilliams</a>, <a href="http://profiles.wordpress.org/users/tfnab">Martin Lormes</a>, <a href="http://profiles.wordpress.org/users/matveb">Matías Ventura</a>, <a href="http://profiles.wordpress.org/users/sivel">Matt Martz</a>, <a href="http://profiles.wordpress.org/users/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/users/mattyrob">MattyRob</a>, <a href="http://profiles.wordpress.org/users/mcepl">mcepl</a>, <a href="http://profiles.wordpress.org/users/mdawaffe">mdawaffe</a>, <a href="http://profiles.wordpress.org/users/mfields">Michael Fields</a>, <a href="http://profiles.wordpress.org/users/michaelh">MichaelH</a>, <a href="http://profiles.wordpress.org/users/michaeltyson">michaeltyson</a>, <a href="http://profiles.wordpress.org/users/dh-shredder">Mike Schroder</a>, <a href="http://profiles.wordpress.org/users/dimadin/">Milan Dinić</a>, <a href="http://profiles.wordpress.org/users/mintindeed">mintindeed</a>, <a href="http://profiles.wordpress.org/users/mitchoyoshitaka">mitchoyoshitaka</a>, <a href="http://profiles.wordpress.org/users/batmoo">Mohammad Jangda</a>, <a href="http://profiles.wordpress.org/users/mrroundhill">mrroundhill</a>, <a href="http://profiles.wordpress.org/users/natecook">natecook</a>, <a href="http://profiles.wordpress.org/users/nathanrice">nathanrice</a>, <a href="http://profiles.wordpress.org/users/niallkennedy">Niall Kennedy</a>, <a href="http://profiles.wordpress.org/users/nickbohle">Nick Bohle</a>, <a href="http://profiles.wordpress.org/users/nbachiyski">Nikolay Bachiyski</a>, <a href="http://profiles.wordpress.org/users/nuxwin">nuxwin</a>, <a href="http://profiles.wordpress.org/users/otto42">Otto</a>, <a href="http://profiles.wordpress.org/users/pavelevap">pavelevap</a>, <a href="http://profiles.wordpress.org/users/petemall">pete.mall</a>, <a href="http://profiles.wordpress.org/users/westi">Peter Westwood</a>, <a href="http://profiles.wordpress.org/users/nprasath002">Prasath Nadarajah</a>, <a href="http://profiles.wordpress.org/users/ptahdunbar">Ptah Dunbar</a>, <a href="http://profiles.wordpress.org/users/bi0xid">Rafael Poveda</a>, <a href="http://profiles.wordpress.org/users/rahe">Rahe</a>, <a href="http://profiles.wordpress.org/users/ramiy">Ramiy</a>, <a href="http://profiles.wordpress.org/users/rasheed">Rasheed Bydousi</a>, <a href="http://profiles.wordpress.org/users/greuben">Reuben Gunday</a>, <a href="http://profiles.wordpress.org/users/miqrogroove">Robert Chapin</a>, <a href="http://profiles.wordpress.org/users/wpmuguru">Ron Rennick</a>, <a href="http://profiles.wordpress.org/users/rosshanney">Ross Hanney</a>, <a href="http://profiles.wordpress.org/users/ryan">Ryan Boren</a>, <a href="http://profiles.wordpress.org/users/ryanimel">Ryan Imel</a>, <a href="http://profiles.wordpress.org/users/zeo">Safirul Alredha</a>, <a href="http://profiles.wordpress.org/users/solarissmoke">Samir Shah</a>, <a href="http://profiles.wordpress.org/users/saracannon">saracannon</a>, <a href="http://profiles.wordpress.org/users/sbressler">sbressler</a>, <a href="http://profiles.wordpress.org/users/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/users/shakenstirred">shakenstirred</a>, <a href="http://profiles.wordpress.org/users/sidharrell">Sidney Harrell</a>, <a href="http://profiles.wordpress.org/users/pross">Simon Prosser</a>, <a href="http://profiles.wordpress.org/users/sorich87">sorich87</a>, <a href="http://profiles.wordpress.org/users/szadok">szadok</a>, <a href="http://profiles.wordpress.org/users/tetele">tetele</a>, <a href="http://profiles.wordpress.org/users/tigertech">tigertech</a>, <a href="http://profiles.wordpress.org/users/trepmal">trepmal</a>, <a href="http://profiles.wordpress.org/users/utkarsh">Utkarsh Kukreti</a>, <a href="http://profiles.wordpress.org/users/valentinas">valentinas</a>, <a href="http://profiles.wordpress.org/users/webduo">webduo</a>, <a href="http://profiles.wordpress.org/users/xibe">Xavier Borderie</a>, <a href="http://profiles.wordpress.org/users/yoavf">Yoav Farhi</a>, <a href="http://profiles.wordpress.org/users/vanillalounge">Ze Fontainhas</a>, and <a href="http://profiles.wordpress.org/users/ziofix">ziofix</a>. Bonus: On their WordPress.org profiles over 20,000 people have said they make their living from WordPress. Are you one of them? <a href="http://wpsurvey.polldaddy.com/s/wp-2011">Don’t forget to take a minute for our survey</a>. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/07/gershwin/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Are You Ready for WordPress 3.2?</title> <link>http://wordpress.org/news/2011/07/are-you-ready-for-wordpress-3-2/</link> <comments>http://wordpress.org/news/2011/07/are-you-ready-for-wordpress-3-2/#comments</comments> <pubDate>Sun, 03 Jul 2011 23:32:26 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Hosting]]></category> <category><![CDATA[health check]]></category> <category><![CDATA[minimum requirements]]></category> <category><![CDATA[MySQL]]></category> <category><![CDATA[PHP]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1952</guid> <description><![CDATA[WordPress 3.2 is going to be released very soon, and we want you to be ready! Take note: the minimum requirements are changing. PHP and MySQL As of 3.2, you’ll need to be running PHP 5.2.4 and MySQL 5.0. As we mentioned almost a year ago when we announced that this change was coming, the percentage [...]]]></description> <content:encoded><![CDATA[WordPress 3.2 is going to be released very soon, and we want you to be ready! Take note: the minimum requirements are changing. <h3>PHP and MySQL</h3> As of 3.2, you’ll need to be running PHP 5.2.4 and MySQL 5.0. <a title="EOL Announcement for PHP4 and MySQL4" href="http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/">As we mentioned almost a year ago when we announced that this change was coming</a>, the percentage of people running older versions of PHP and MySQL is relatively low. With more than 45 million people using WordPress, though, even a small percentage can mean a lot of people! Don’t caught with your <del>pants</del> dashboard down — make sure you’re running compatible versions of PHP and MySQL before you update <del>tomorrow</del> when WordPress 3.2 is released. Log in to your hosting account, and check to make sure you have at least PHP 5.2.4 and MySQL 5.0. Most of the major hosts already default to these or newer versions, but there are some exceptions. Check to see which versions you are running, and if you’re still on an older version, it should be as simple as changing a dropdown menu and clicking Save to get up to date. If you don’t know how to find this information in your hosting account or you don’t even know how to access your hosting control panel because someone else manages that for you, don’t fret. You can <a href="http://wordpress.org/extend/plugins/health-check/">find out if you’re ready for 3.2 with the Health Check plugin</a>. In your dashboard, go to Plugins → Add New and search for “health check” (it should be the first result). Install it, activate it, and it will tell you if you need to update anything. If you need more help, contact your host’s customer service and use this email template to ask them to help you. <blockquote>Hi there. I host my domain [example.com] with you, and I run WordPress on my site. The minimum requirements are changing to PHP 5.2.4 and MySQL 5.0, and I would appreciate your help in confirming that my site’s setup meets these requirements. If I’m currently running an older version of PHP or MySQL, could you update it for me, or tell me how to do it? Thanks so much!</blockquote> If your host replies that they can’t update to these versions, it might be time to <a href="http://wordpress.org/hosting/">look for a new host</a>. <h3>IE6 and Outdated Browsers</h3> With 3.2, we’re also dropping support for Internet Explorer 6, a 10-years-old outdated browser that even <a href="http://www.ie6countdown.com/">Microsoft is ready to leave behind</a>. From now on, if you access your WordPress dashboard from an outdated browser, we’ll let you know. Why? Because as web technology improves, so does WordPress, as we build features to take advantage of these improvements. If you’re using an out-of-date browser, chances are you’re missing out. If your browser is out of date, you’ll see a friendly orangey-yellow box in your dashboard letting you know you a newer version is available (which you can dismiss, of course). If you’re using IE6, though, the box will be red, and your dashboard will not function properly. If you’re stuck on IE6 because the computer you use is maintained by a business, library, school, or the like, and you are not able to download a newer browser, here’s a sample email you can use to ask your boss/administrator/IT guys to update the browser. <blockquote>Hi there. The computer I use at [where you use the computer] is equipped with an out-of-date web browser. Internet Explorer 6 was created 10 years ago, before modern web standards, and does not support modern web applications. More and more sites and applications are dropping support for IE6, including the new version of WordPress. Even Microsoft, the makers of IE6, are counting down until IE6 goes the way of the dinosaur (see http://www.ie6countdown.com/ for more information). Can you please install an updated version of IE or any modern browser (see http://browsehappy.com for more information) on the available computers? Thank you very much.</blockquote> Welcome to the future!     ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/07/are-you-ready-for-wordpress-3-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.1.4 (and 3.2 Release Candidate 3)</title> <link>http://wordpress.org/news/2011/06/wordpress-3-1-4/</link> <comments>http://wordpress.org/news/2011/06/wordpress-3-1-4/#comments</comments> <pubDate>Wed, 29 Jun 2011 19:00:40 +0000</pubDate> <dc:creator>Ryan Boren</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1927</guid> <description><![CDATA[WordPress 3.1.4 is available now and is a maintenance and security update for all previous versions. This release fixes an issue that could allow a malicious Editor-level user to gain further access to the site. Thanks K. Gudinavicius of SEC Consult for bringing this to our attention. Version 3.1.4 also incorporates several other security fixes and hardening [...]]]></description> <content:encoded><![CDATA[WordPress 3.1.4 is available now and is a maintenance and security update for all previous versions. This release fixes an issue that could allow a malicious Editor-level user to gain further access to the site. Thanks K. Gudinavicius of <a href="http://www.sec-consult.com/">SEC Consult</a> for bringing this to our attention. Version 3.1.4 also incorporates several other security fixes and hardening measures thanks to the work of WordPress developers <a href="http://www.buayacorp.com/">Alexander Concha</a> and <a href="http://joncave.co.uk/">Jon Cave</a> of our security team. Consult the <a href="http://core.trac.wordpress.org/log/branches/3.1/?action=stop_on_copy&mode=stop_on_copy&rev=18377&stop_rev=18043">change log</a> for more details. <a href="http://wordpress.org/download/">Download WordPress 3.1.4</a> or update immediately from the Dashboard → Updates menu in your site’s admin area. <h3>WordPress 3.2 Release Candidate 3</h3> This release was about all that stood in the way of a final release of WordPress 3.2. So we’re also announcing the third release candidate for 3.2, which contains all of the fixes in 3.1.4; few minor RTL, JavaScript, and user interface fixes; and ensures graceful failures if 3.2 is run on PHP4. As a reminder, we’ve bumped our minimum requirements for version 3.2 to PHP 5.2.4 and MySQL 5.0. To test WordPress 3.2, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (you’ll want “bleeding edge nightlies”). Or you can <a href="http://wordpress.org/wordpress-3.2-RC3.zip">download the release candidate here</a> (zip). At this stage, plugin authors should be doing final tests to ensure compatibility. Bonus: For more on what to test and what to do if you find an issue, please read <a href="http://wordpress.org/news/2011/05/wordpress-3-2-beta-1/">our Beta 1 post</a>. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/06/wordpress-3-1-4/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.2 Release Candidate 2</title> <link>http://wordpress.org/news/2011/06/wordpress-3-2-release-candidate-2/</link> <comments>http://wordpress.org/news/2011/06/wordpress-3-2-release-candidate-2/#comments</comments> <pubDate>Fri, 24 Jun 2011 23:15:22 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Testing]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1915</guid> <description><![CDATA[Howdy! The second release candidate for WordPress 3.2 is now available. If you haven’t tested WordPress 3.2 yet, now is the time — please though, not on your live site unless you’re extra adventurous. We’ve handled a number of issues since RC1, including additional Twenty Eleven tweaks, a new theme support option for defaulting to [...]]]></description> <content:encoded><![CDATA[Howdy! The second release candidate for WordPress 3.2 is now available. If you haven’t tested WordPress 3.2 yet, now is the time — please though, not on your live site unless you’re extra adventurous. We’ve handled a number of issues since RC1, including additional Twenty Eleven tweaks, a new theme support option for defaulting to randomized headers, and various RTL fixes. Plugin and theme authors, please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release. Users are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause. If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know: <ul> <li>Post it to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a> or <a href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers</a></li> <li>Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev</li> <li>File a bug ticket on the <a href="http://core.trac.wordpress.org/">WordPress Trac</a></li> </ul> To test WordPress 3.2, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (you’ll want “bleeding edge nightlies”). Or you can <a href="http://wordpress.org/wordpress-3.2-RC2.zip">download the release candidate here</a> (zip). If any known issues crop up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>. If you’d like to know which levers to pull in your testing, <a href="http://wordpress.org/news/2011/05/wordpress-3-2-beta-1/">check out a list of features</a> in our Beta 1 post. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/06/wordpress-3-2-release-candidate-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Passwords Reset</title> <link>http://wordpress.org/news/2011/06/passwords-reset/</link> <comments>http://wordpress.org/news/2011/06/passwords-reset/#comments</comments> <pubDate>Tue, 21 Jun 2011 23:57:42 +0000</pubDate> <dc:creator>Matt Mullenweg</dc:creator> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1908</guid> <description><![CDATA[Earlier today the WordPress team noticed suspicious commits to several popular plugins (AddThis, WPtouch, and W3 Total Cache) containing cleverly disguised backdoors. We determined the commits were not from the authors, rolled them back, pushed updates to the plugins, and shut down access to the plugin repository while we looked for anything else unsavory. We’re [...]]]></description> <content:encoded><![CDATA[Earlier today the WordPress team noticed suspicious commits to several popular plugins (AddThis, WPtouch, and W3 Total Cache) containing cleverly disguised backdoors. We determined the commits were not from the authors, rolled them back, pushed updates to the plugins, and shut down access to the plugin repository while we looked for anything else unsavory. We’re still investigating what happened, but as a prophylactic measure we’ve decided to force-reset all passwords on WordPress.org. To use the forums, trac, or commit to a plugin or theme, you’ll need to <a href="http://wordpress.org/support/bb-login.php">reset your password to a new one</a>. (Same for bbPress.org and BuddyPress.org.) As a user, make sure to never use the same password for two different services, and we encourage you not to reset your password to be the same as your old one. Second, if you use <a href="http://wordpress.org/extend/plugins/addthis/">AddThis</a>, <a href="http://wordpress.org/extend/plugins/wptouch/">WPtouch</a>, or <a href="http://wordpress.org/extend/plugins/w3-total-cache/">W3 Total Cache</a> and there’s a possibility you could have updated in the past day, make sure to visit your updates page and upgrade each to the latest version. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/06/passwords-reset/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.2 Release Candidate</title> <link>http://wordpress.org/news/2011/06/wordpress-3-2-release-candidate/</link> <comments>http://wordpress.org/news/2011/06/wordpress-3-2-release-candidate/#comments</comments> <pubDate>Tue, 14 Jun 2011 04:28:39 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Development]]></category> <category><![CDATA[Releases]]></category> <category><![CDATA[Testing]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1890</guid> <description><![CDATA[The first release candidate (RC1) for WordPress 3.2 is now available. An RC comes after the beta period and before final release. We think we’re done, but with tens of millions of users, a variety of configurations, and thousands of plugins, it’s possible we’ve missed something. So if you haven’t tested WordPress 3.2 yet, now [...]]]></description> <content:encoded><![CDATA[The first release candidate (RC1) for WordPress 3.2 is now available. An RC comes after the beta period and before final release. We think we’re done, but with tens of millions of users, a variety of configurations, and thousands of plugins, it’s possible we’ve missed something. So if you haven’t tested WordPress 3.2 yet, now is the time! Please though, not on your live site unless you’re extra adventurous. Things to keep in mind: <ul> <li>With <a href="http://core.trac.wordpress.org/milestone/3.2">more than 350 tickets closed</a>, there are plenty of changes. Plugin and theme authors, please test your plugins and themes now, so that if there is a compatibility issue, we can figure it out before the final release.</li> <li>Users are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.</li> <li>Twenty Eleven isn’t quite at the release candidate stage. <a href="http://cheezburger.com/Mmmbop/lolz/View/4683101952">Contents may settle</a>.</li> <li>If any known issues crop up, you’ll be able to <a href="http://core.trac.wordpress.org/report/5">find them here</a>.</li> </ul> If you are testing the release candidate and think you’ve found a bug, there are a few ways to let us know: <ul> <li>Post it to the <a href="http://wordpress.org/support/forum/alphabeta/">Alpha/Beta area in the support forums</a> or <a href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers</a></li> <li>Join the development IRC channel and tell us live at irc.freenode.net #wordpress-dev</li> <li>File a bug ticket on the <a href="http://core.trac.wordpress.org/">WordPress Trac</a></li> </ul> To test WordPress 3.2, try the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester plugin</a> (you’ll want “bleeding edge nightlies”). Or you can <a href="http://wordpress.org/wordpress-3.2-RC1.zip">download the release candidate here</a> (zip). Happy testing! If you’d like to know which levers to pull in your testing, <a href="http://wordpress.org/news/2011/05/wordpress-3-2-beta-1/">check out a list of features</a> in our Beta 1 post. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/06/wordpress-3-2-release-candidate/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordCamp San Francisco Call for Speakers</title> <link>http://wordpress.org/news/2011/05/wordcamp-san-francisco-call-for-speakers/</link> <comments>http://wordpress.org/news/2011/05/wordcamp-san-francisco-call-for-speakers/#comments</comments> <pubDate>Tue, 31 May 2011 18:59:48 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <category><![CDATA[WordCamp]]></category> <category><![CDATA[wcsf]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1886</guid> <description><![CDATA[The annual WordPress conference, WordCamp San Francisco (home of the very first WordCamp), is now accepting speaker applications. Past speakers have included core WordPress developers, people building successful businesses on WordPress, popular bloggers, people from related projects and businesses…you name it. In addition to Matt Mullenweg’s annual “State of the Word” address, WCSF has played [...]]]></description> <content:encoded><![CDATA[The annual WordPress conference, <a href="http://2011.sf.wordcamp.org/">WordCamp San Francisco</a> (home of the very first WordCamp), is now accepting speaker applications. Past speakers have included core WordPress developers, people building successful businesses on WordPress, popular bloggers, people from related projects and businesses…you name it. In addition to Matt Mullenweg’s annual “State of the Word” address, WCSF has played host to talks by people like Mark Jaquith, Matt Cutts, Richard Stallman, Scott Berkun, Karl Fogel, Tim Ferriss, Tara Hunt, Chris Pirillo, and John Lilly. With 3 days of content this year instead of just one, the list of speakers should be even more impressive. If you think you’d make a good addition to this year’s roster, check out the <a href="http://2011.sf.wordcamp.org/call-for-speakers/">WCSF Call for Speakers</a>. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/05/wordcamp-san-francisco-call-for-speakers/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.1.3 (and WordPress 3.2 Beta 2)</title> <link>http://wordpress.org/news/2011/05/wordpress-3-1-3/</link> <comments>http://wordpress.org/news/2011/05/wordpress-3-1-3/#comments</comments> <pubDate>Wed, 25 May 2011 18:43:28 +0000</pubDate> <dc:creator>Mark Jaquith</dc:creator> <category><![CDATA[Development]]></category> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=1838</guid> <description><![CDATA[WordPress 3.1.3 is available now and is a security update for all previous versions. It contains the following security fixes and enhancements: Various security hardening by Alexander Concha. Taxonomy query hardening by John Lamansky. Prevent sniffing out user names of non-authors by using canonical redirects. Props Verónica Valeros. Media security fixes by Richard Lundeen of Microsoft, Jesse Ou [...]]]></description> <content:encoded><![CDATA[<a href="http://wordpress.org/download/">WordPress 3.1.3</a> is available now and is a security update for all previous versions. It contains the following security fixes and enhancements: <ul> <li>Various security hardening by <a href="http://www.buayacorp.com">Alexander Concha</a>.</li> <li>Taxonomy query hardening by <a href="http://johnlamansky.com/wordpress">John Lamansky</a>.</li> <li>Prevent sniffing out user names of non-authors by using canonical redirects. Props <a href="http://www.talsoft.com.ar">Verónica Valeros</a>.</li> <li>Media security fixes by Richard Lundeen of <a href="http://www.microsoft.com/">Microsoft</a>, Jesse Ou of <a href="http://www.microsoft.com/">Microsoft</a>, and <a href="http://www.microsoft.com/security/msrc/default.aspx">Microsoft Vulnerability Research</a>.</li> <li>Improves file upload security on hosts with dangerous security settings.</li> <li>Cleans up old WordPress import files if the import does not finish.</li> <li>Introduce “clickjacking” protection in modern browsers on admin and login pages.</li> </ul> Consult the <a href="http://core.trac.wordpress.org/log/branches/3.1/?action=stop_on_copy&mode=stop_on_copy&rev=18023&stop_rev=17805&limit=100">change log</a> for more details. <a href="http://wordpress.org/download/">Download WordPress 3.1.3</a> or update automatically from the Dashboard → Updates menu in your site’s admin area. <hr /> <h3>WordPress 3.2 Beta 2 also available</h3> In other news, our development of WordPress 3.2 development continues right on schedule. We released <a href="http://wordpress.org/news/2011/05/wordpress-3-2-beta-1/">Beta 1</a> thirteen days ago, and today we’re putting out Beta 2 for your testing pleasure. This is still beta software, so we don’t recommend that you use it on production sites. But if you’re a plugin developer, a theme developer, or a site administrator, you should be running this on your test environments and <a href="http://codex.wordpress.org/Reporting_Bugs">reporting any bugs</a> you find. If you’re a WordPress user who wants to open your presents early, take advantage of WordPress’ famous 5-minute install and spin up a secondary test site. Let us know what you think! The plan is to start putting out release candidates in early June, and to release WordPress 3.2 by the end of the month. The more you help us iron out issues during the beta period, the more likely we are to hit those dates. To misappropriate and mangle a quote from Mahatma Gandhi: “Be the punctuality you want to see in the WordPress.” In other words, test now! Here are some of the things that changed since Beta 1: <ul> <li><a href="http://code.google.com/chrome/chromeframe/">Google Chrome Frame</a> is now supported in the admin, if you have it installed. This is especially useful for IE 6 users (remember, IE 6 is otherwise deprecated for the admin).</li> <li>The admin is less ugly in IE 7.</li> <li>The blue admin color scheme has caught up to the grey one, and is ready for testing.</li> <li>We are now bundling jQuery 1.6.1. You should test any JS that uses jQuery. WordPress JavaScript guru Andrew Ozz has <a href="http://wpdevel.wordpress.com/2011/05/25/jquery-updates-in-wordpress-3-2/">a post with more info</a>.</li> </ul> <a href="http://wordpress.org/wordpress-3.2-beta2.zip">Download WordPress 3.2 Beta 2</a> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/05/wordpress-3-1-3/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>