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>Thu, 03 May 2012 02:52:28 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.4-beta4-20717</generator> <item> <title>WordPress 3.4 Beta 4</title> <link>http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/</link> <comments>http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/#comments</comments> <pubDate>Thu, 03 May 2012 02:52:28 +0000</pubDate> <dc:creator>Ryan Boren</dc:creator> <category><![CDATA[Releases]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2273</guid> <description><![CDATA[Less bugs, more polish, the same beta disclaimers. Download, test, report bugs. Thanks much. /ryan #thewholebrevitything]]></description> <content:encoded><![CDATA[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 ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/05/wordpress-3-4-beta-4/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.3.2 (and WordPress 3.4 Beta 3)</title> <link>http://wordpress.org/news/2012/04/wordpress-3-3-2/</link> <comments>http://wordpress.org/news/2012/04/wordpress-3-3-2/#comments</comments> <pubDate>Fri, 20 Apr 2012 15:10:37 +0000</pubDate> <dc:creator>Andrew Nacin</dc:creator> <category><![CDATA[Development]]></category> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2262</guid> <description><![CDATA[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 [...]]]></description> <content:encoded><![CDATA[<a href="http://wordpress.org/download/">WordPress 3.3.2</a> is available now and is a security update for all previous versions. Three external libraries included in WordPress received security updates: <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> 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. WordPress 3.3.2 also addresses: <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> 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&stop_rev=20087">change log</a> for more details. <a href="http://wordpress.org/download/">Download WordPress 3.3.2</a> or update now from the Dashboard → Updates menu in your site’s admin area. <hr /> <h3>WordPress 3.4 Beta 3 also available</h3> 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&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.) 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. (See the <a href="http://core.trac.wordpress.org/report/5">known issues here</a>.) If you’re a WordPress user who wants to open your presents early, take advantage of WordPress’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>! 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. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/04/wordpress-3-3-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.4 Beta 2</title> <link>http://wordpress.org/news/2012/04/wordpress-3-4-beta-2/</link> <comments>http://wordpress.org/news/2012/04/wordpress-3-4-beta-2/#comments</comments> <pubDate>Thu, 12 Apr 2012 03:52:24 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[3.4]]></category> <category><![CDATA[beta]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2257</guid> <description><![CDATA[Howdy, folks! Another week, another beta. Since we released Beta 1 last week, we’ve committed more than 60 bug fixes and feature adjustments based on testing and feedback. If you’ve been testing Beta 1, please update to Beta 2 to make sure things are still working for you. If you are a theme or plugin [...]]]></description> <content:encoded><![CDATA[Howdy, folks! Another week, another beta. Since we released Beta 1 last week, we’ve committed more than 60 bug fixes and feature adjustments based on testing and feedback. If you’ve been testing Beta 1, please update to Beta 2 to make sure things are still working for you. If you are a theme or plugin author and have not yet started testing your code against the 3.4 beta, now’s the perfect time to start. And as always, if you find any bugs, let us know! Full details on testing and bug reporting can be found in <a href="http://wordpress.org/news/2012/04/wordpress-3-4-beta-1/" title="WordPress 3.4 Beta 1">last week’s Beta 1 post</a>. <a href="http://wordpress.org/wordpress-3.4-beta2.zip">Download WordPress 3.4 Beta 2</a> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/04/wordpress-3-4-beta-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.4 Beta 1</title> <link>http://wordpress.org/news/2012/04/wordpress-3-4-beta-1/</link> <comments>http://wordpress.org/news/2012/04/wordpress-3-4-beta-1/#comments</comments> <pubDate>Thu, 05 Apr 2012 02:07:03 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Releases]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2250</guid> <description><![CDATA[WordPress 3.4 is ready for beta testers! As always, this is software still in development and we don’t recommend that you run it on a production site — set up a test site just to play with the new version. If you break it (find a bug), please report it, and if you’re a developer, try to [...]]]></description> <content:encoded><![CDATA[WordPress 3.4 is ready for beta testers! As always, this is software still in development and we don’t recommend that you run it on a production site — set up a test site just to play with the new version. If you break it (find a bug), please report it, and if you’re a developer, try to help us fix it. If all goes well, we hope to release WordPress 3.4 in May. The more help we get with testing and fixing bugs, the sooner we will be able to release the final version. If you want to be a beta tester, you should check out the Codex article on <a title="Reporting Bugs for WordPress" href="http://codex.wordpress.org/Reporting_Bugs">how to report bugs</a>. Here’s some of what’s new: <ul> <li>Theme Customizer with Previewer</li> <li>Flexible Custom Header Sizes</li> <li>Selecting Custom Header and Background Images from Media Library</li> <li>Better experience searching for and choosing a theme</li> </ul> And some of the under-the-hood changes: <ul> <li>New XML-RPC API for external and mobile applications</li> <li>New API for registering theme support for custom headers and backgrounds</li> <li>Performance improvements to WP_Query by splitting the query (Please test!)</li> <li>Internationalization improvements (improved performance and locale support)</li> <li>Performance and API improvements when working with lists of installed themes</li> <li>Support for installing child themes from the WordPress Themes Directory</li> </ul> Remember, if you find something you think is a bug, report it! You can bring it up in the <a title="Alpha/Beta Support Forum" href="http://wordpress.org/support/forum/alphabeta">alpha/beta forum</a>, you can email it to the <a title="WP-testers mailing list info page" href="http://lists.automattic.com/mailman/listinfo/wp-testers">wp-testers list</a>, or if you’ve confirmed that other people are experiencing the same bug, you can report it on the <a title="WordPress Core Trac" href="http://core.trac.wordpress.org/">WordPress Core Trac</a>. (We recommend starting in the forum or on the mailing list.) Theme and plugin authors, if you haven’t been following the 3.4 development cycle, please start now so that you can update your themes and plugins to be compatible with the newest version of WordPress. <a title="Download WordPress 3.4 Beta 1" href="http://wordpress.org/wordpress-3.4-beta1.zip">Download WordPress 3.4 Beta 1</a> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/04/wordpress-3-4-beta-1/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress Takes SXSW 2012!</title> <link>http://wordpress.org/news/2012/03/wordpress-takes-sxsw-2012/</link> <comments>http://wordpress.org/news/2012/03/wordpress-takes-sxsw-2012/#comments</comments> <pubDate>Tue, 06 Mar 2012 16:19:55 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <category><![CDATA[Events]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2240</guid> <description><![CDATA[The South by Southwest Interactive Festival (SXSW) holds a special place in the history and heart of WordPress. Though the conference has changed in the years since I first met Matt in the hallway in 2003 — before WordPress even had a name — it’s still arguably one of the most influential events in our [...]]]></description> <content:encoded><![CDATA[The <a href="http://sxsw.com/interactive">South by Southwest Interactive Festival</a> (SXSW) holds a special place in the history and heart of WordPress. Though the conference has changed in the years since I first met Matt in the hallway in 2003 — before WordPress even had a name — it’s still arguably one of the most influential events in our industry, and we’ll be there again this year. Will we see you there? <h3>Booth</h3> There will be a <a href="http://wordpress.org/news/sxsw2012/booth/">WordPress booth at the SXSW trade show</a> March 12-15. Our booth was packed to overflowing last year as we helped people with their blogs and gave away WordPress swag, so this year we’ll have more space to meet as many of you as possible. Stop by if you need a helping hand with your site, or just to say hi. We’ll also have buttons, stickers, and t-shirts again this year. <h3>Party</h3> This year’s <a href="http://wordpress.org/news/sxsw2012/">WordPress party</a> will be hosted by the <a href="http://wordpressfoundation.org">WordPress Foundation</a> on Monday, March 12 from 6-9pm. Space is limited, so make sure you <a href="http://wordpress.org/news/sxsw2012/">RSVP</a> (no SXSW badge is required). The party this year will be at the <a href="http://www.purevolume.com/thehouse/">Buzzmedia Pure Volume House</a>, and the story of how we hooked up with them is pretty cool. <blockquote>Once upon a time, David Wang had a business called Buzzmedia in Malaysia, with the twitter username @buzzmedia. When David changed gears and started <a href="http://clickwp.com/">ClickWP</a>, a WordPress support business, he stopped going by the Buzzmedia name. In the U.S., a company also called Buzzmedia wished it had that Twitter username, and asked if they could have it since David wasn’t going to use it anymore. David, feeling the WordPress community love, said he would give them the name, and suggested they do something in return for the WordPress Foundation. So, everyone talked to everyone else and it worked out that Buzzmedia was willing to donate a fantastic venue for this year’s party as well as covering the bar. In the end, the Foundation got a great SXSW party, Buzzmedia got their twitter username, and David got the warm glow of having used his power for the good of the WordPress community, and they all lived happily ever after.</blockquote> Seriously, though, the PureVolume House is always a great SXSW venue, so thank you David and Buzzmedia for your generosity! We’ll have drinks and snacks and a few hundred WordPress-loving partygoers, so you know it will be a good time. Kind of like a WordCamp afterparty without all the work of a WordCamp. <img src='http://wordpress.org/news/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> The venue can hold 500 people, and based on last year, we’ll hit that pretty quickly. The one requirement is that you use WordPress. On the RSVP form, you will be asked to enter the URL of your WordPress-powered site (if you have more than one, just pick your main site). If you fill in this field with something other than what’s requested (such as “N/A” or putting in a fake url) your RSVP may be deleted, so please make sure to enter your real site. <a href="http://wordpress.org/news/sxsw2012/"> RSVP Now</a>! ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/03/wordpress-takes-sxsw-2012/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Year of the Meetup</title> <link>http://wordpress.org/news/2012/01/year-of-the-meetup/</link> <comments>http://wordpress.org/news/2012/01/year-of-the-meetup/#comments</comments> <pubDate>Fri, 27 Jan 2012 20:17:49 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2210</guid> <description><![CDATA[We hereby declare 2012 as the Year of the WordPress Meetup. You'll want to get in on this action. So what is a WordPress Meetup? Basically, it's people in a community getting together — meeting up — who share an interest in WordPress, whether they be bloggers, business users, developers, consultants, or any other category of person able to say, "I use WordPress in some way and I like it, and I want to meet other people who can say the same.]]></description> <content:encoded><![CDATA[We hereby declare 2012 as the Year of the WordPress Meetup. You’ll want to get in on this action. <blockquote>meet·up \mēt-əp\ noun A meeting, especially a regular meeting of people who share a particular interest and have connected with each other through a social-networking Web site: a meetup for new moms in the neighborhood; a meetup to plan the trip; a meetup for WordPress users.1</blockquote> So what is a WordPress Meetup? Basically, it’s people in a community getting together — meeting up — who share an interest in WordPress, whether they be bloggers, business users, developers, consultants, or any other category of person able to say, “I use WordPress in some way and I like it, and I want to meet other people who can say the same.” Meetups come in different shapes and sizes, but they all carry the benefit of connecting you with potential collaborators and friends, and helping you learn more about what you can do with WordPress. Here are some of the common types of WordPress meetups: <ul> <li>Hang out and work on your WordPress sites together</li> <li>Social/happy hour type gatherings</li> <li>Mini-lectures/presentations</li> <li>Developer hacking meetups</li> <li>Show & tell of how group members are using WordPress</li> <li>Formal instruction on how to use WordPress</li> <li>Lecture series (possibly with visiting speakers)</li> <li>Genius bar/help desk</li> </ul> There’s no prescribed format, as each local group can decide for itself what they want to do. Some groups mix it up from month to month, while others have multiple events each month to satisfy the needs of their community. The tough part? Running a popular group takes time and money. Just as we worked last year to remove the financial burden for <a href="http://wordcamp.org">WordCamp</a> organizers and provide logistical support so they could focus more on their event content and experience, we want to start extending that kind of support to meetup groups as well. We don’t want it to cost anything for someone to run a WordPress meetup, or to attend one — building local communities should be as free as WordPress itself! Since there are so many more meetups than there are WordCamps, we’re going to start with the cost that is the same for every group: meetup.com organizer dues. We’re setting up an official WordPress account on <a href="http://Meetup.com">Meetup.com</a> right now, and over the next couple of weeks will be working with existing meetup group organizers, people who want to start a new meetup group, and the helpful folks at Meetup.com to put this program in place. WordPress meetup groups that choose to have their group become part of the WordPress account will no longer pay organizer dues for that group, as the <a href="http://wordpressfoundation.org">WordPress Foundation</a> will be footing the bill. This is exciting for several reasons. First, it means local organizers who are giving something back to the project by way of their time won’t also have shell out $12-19/month for the privilege. That alone is a big step. Second, it will open the door to more events and leaders within a community, since leadership and event planning won’t need to be tied to “owning” the meetup group. Third, more active meetup groups means more WordCamps, yay! In addition to the financial aspects, we’ll be working on ways to improve social recognition of meetup activity by incorporating feeds from the official meetup groups into the WordPress.org site, and including meetup group participation in the activity stream on your <a href="http://profiles.wordpress.org/">WordPress.org profile</a>.2 I’m also hoping we can do something around providing video equipment to meetup groups (like we already do for WordCamps) to record presentations and tutorials that can be posted to <a href="http://WordPress.tv">WordPress.tv</a>, helping meetup groups offer WordPress classes in their community, and getting involved with mentoring WordPress clubs at local schools and universities. Oh, and we’ll send out some WordPress buttons and stickers to the groups that join in, because everyone loves buttons and stickers. We’re also putting together some cool resources for people who want to start a new meetup group. There will be a field guide to getting started and some supplies to help you get your group going, and a forum for organizers to talk to and learn from each other. Over time, we’ll be talking to organizers and looking at what other expenses we can absorb and what other support we can provide to local groups. For now, we’re starting with the organizer dues. If you currently run a WordPress meetup group (whether you are using Meetup.com or not) or would like to start a WordPress meetup group in your area, please fill out our <a href="http://wordpressdotorg.polldaddy.com/s/wordpress-meetup-groups">WordPress Meetup Groups survey</a>. Filling in the survey doesn’t obligate you to join the official group, it just gives us a starting point to a) find out what groups are around/interested, and b) get some information on existing groups and their expenses and needs. Meetup.com will contact the group organizers who’ve said they’d like to join the new program, and will walk them through the logistics of the change and answer questions before helping them to opt-in officially. So, if you currently run a WordPress meetup group, or you would like to start one, please fill out our <a href="http://wordpressdotorg.polldaddy.com/s/wordpress-meetup-groups">WordPress Meetup Groups survey</a>. I can’t wait to see more meetups! 1 – Adapted from <a href="http://dictionary.reference.com/browse/meetup">“meetup” definition at dictionary.com</a>. 2 – Didn’t know about profiles? Check out http://profiles.wordpress.org/users/yourwordpressdotorgusernamehere (put in the username you use in the WordPress.org forums) to see yours! ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/01/year-of-the-meetup/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Internet Blackout Day on January 18</title> <link>http://wordpress.org/news/2012/01/internet-blackout/</link> <comments>http://wordpress.org/news/2012/01/internet-blackout/#comments</comments> <pubDate>Tue, 17 Jan 2012 23:18:58 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2199</guid> <description><![CDATA[WordPress.org is officially joining the protest against Senate Bill 968: the Protect IP Act that is coming before the U.S. Senate next week. As I wrote in my post a week ago, if this bill is passed it will jeopardize internet freedom and shift the power of the independent web into the hands of corporations. [...]]]></description> <content:encoded><![CDATA[WordPress.org is officially joining the <a href="http://sopastrike.com/">protest against Senate Bill 968: the Protect IP Act</a> that is coming before the U.S. Senate next week. As I wrote in <a title="Help Stop SOPA/PIPA" href="http://wordpress.org/news/2012/01/help-stop-sopa-pipa/">my post a week ago</a>, if this bill is passed it will jeopardize internet freedom and shift the power of the independent web into the hands of corporations. We must stop it. On January 18, 2012 many sites around the web — from small personal blogs to internet institutions like <a href="http://Mozilla.org">Mozilla</a>, <a href="http://en.wikipedia.org/wiki/Wikipedia:SOPA_initiative/Action">Wikipedia</a>, <a href="http://blog.reddit.com/2012/01/stopped-they-must-be-on-this-all.html">reddit</a>, and <a href="https://twitter.com/#!/benhuh/status/157538541155516416">I Can Has Cheezburger?</a> – will be going dark in protest and to drive their visitors to sites like <a href="http://americancensorship.org">americancensorship.org</a> to take action and help fight the passage of the Protect IP Act. So will WordPress.org. If you want to join the protest by blacking out your WordPress site or applying a ribbon, there is now a variety of <a href="http://wordpress.org/extend/plugins/tags/sopa">blackout plugins in the WordPress.org plugins directory</a>. While joining the protest in this manner is laudable, please don’t forget to also make those phone calls to U.S. Senators — they’re the ones with the voting power. <ul> <li><a href="http://wordpress.org/extend/plugins/tags/sopa">Get a protest plugin</a></li> <li><a href="http://americancensorship.org">Take action at americancensorship.org</a></li> </ul> ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/01/internet-blackout/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>Help Stop SOPA/PIPA</title> <link>http://wordpress.org/news/2012/01/help-stop-sopa-pipa/</link> <comments>http://wordpress.org/news/2012/01/help-stop-sopa-pipa/#comments</comments> <pubDate>Tue, 10 Jan 2012 19:18:56 +0000</pubDate> <dc:creator>Jane Wells</dc:creator> <category><![CDATA[Community]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2191</guid> <description><![CDATA[You are an agent of change. Has anyone ever told you that? Well, I just did, and I meant it. Normally we stay away from from politics here at the official WordPress project — having users from all over the globe that span the political spectrum is evidence that we are doing our job and [...]]]></description> <content:encoded><![CDATA[You are an agent of change. Has anyone ever told you that? Well, I just did, and I meant it. Normally we stay away from from politics here at the official WordPress project — having users from all over the globe that span the political spectrum is evidence that we are doing our job and democratizing publishing, and we don’t want to alienate any of our users no matter how much some of us may disagree with some of them personally. Today, I’m breaking our no-politics rule, because <a href="http://americancensorship.org/">there’s something going on</a> in U.S. politics right now that we need to make sure you know about and understand, because it affects us all. Using WordPress to blog, to publish, to communicate things online that once upon a time would have been relegated to an unread private journal (or simply remained unspoken, uncreated, unshared) makes you a part of one of the biggest changes in modern history: the democratization of publishing and the independent web. Every time you click Publish, you are a part of that change, whether you are posting canny political insight or a cat that makes you LOL. How would you feel if the web stopped being so free and independent? I’m <del>concerned</del> freaked right the heck out about the bills that threaten to do this, and as a participant in one of the biggest changes in modern history, you should be, too. You may have heard people talking/blogging/twittering about SOPA — the Stop Online Piracy Act. The recent <a href="http://godaddyboycott.org/">SOPA-related boycott of GoDaddy</a> was all over the news, with many people expressing their outrage over the possibilities of SOPA, but when I ask people about SOPA and its sister bill in the Senate, PIPA (Protect IP Act), many don’t really know what the bills propose, or what we stand to lose. If you are not freaked out by SOPA/PIPA, please: for the next four minutes, instead of checking Facebook statuses, seeing who mentioned you on Twitter, or watching the latest episode of Sherlock*, watch this video (by <a href="http://fightforthefuture.org/">Fight for the Future</a>). <iframe src="http://player.vimeo.com/video/31100268" width="600" height="338" frameborder="0" webkitAllowFullScreen mozallowfullscreen allowFullScreen></iframe> Some thoughts: <ul> <li>In the U.S. our legal system maintains that the burden of proof is on the accuser, and that people are innocent until proven guilty. This tenet seems to be on the chopping block when it comes to the web if these bills pass, as companies could shut down sites based on accusation alone.</li> <li>Laws are not like lines of PHP; they are not easily reverted if someone wakes up and realizes there is a better way to do things. We should not be so quick to codify something this far-reaching.</li> <li>The people writing these laws are not the people writing the independent web, and they are not out to protect it. We have to stand up for it ourselves.</li> </ul> Blogging is a form of activism. You can be an agent of change. Some people will tell you that taking action is useless, that online petitions, phone calls to representatives, and other actions won’t change a single mind, especially one that’s been convinced of something by lobbyist dollars. To those people, I repeat the words of Margaret Mead: <blockquote>Never doubt that a small group of thoughtful, committed citizens can change the world. Indeed, it is the only thing that ever has.</blockquote> We are not a small group. More than 60 million people use WordPress — it’s said to power <a href="http://w3techs.com/technologies/overview/content_management/all">about 15% of the web</a>. We can make an impact, and you can be an agent of change. Go to <a href="http://americancensorship.org/">Stop American Censorship</a> for more information and a bunch of ways you can take action quickly, easily, and painlessly. The Senate votes in two weeks, and we need to help at least 41 more senators see reason before then. Please. <a href="http://americancensorship.org/">Make your voice heard</a>. *Yes, the latest episode of Sherlock is good. Stephen Moffatt + Russell Tovey = always good ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/01/help-stop-sopa-pipa/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.3.1 Security and Maintenance Release</title> <link>http://wordpress.org/news/2012/01/wordpress-3-3-1/</link> <comments>http://wordpress.org/news/2012/01/wordpress-3-3-1/#comments</comments> <pubDate>Tue, 03 Jan 2012 21:24:10 +0000</pubDate> <dc:creator>Ryan Boren</dc:creator> <category><![CDATA[Releases]]></category> <category><![CDATA[Security]]></category> <guid isPermaLink="false">http://wordpress.org/news/2012/01/wordpress-3-3-1/</guid> <description><![CDATA[WordPress 3.3.1 is now available. This maintenance release fixes 15 issues with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3. Thanks to Joshua H., Hoang T., Stefan Zimmerman, Chris K., and the Go Daddy security team for responsibly disclosing the bug to our security team. Download 3.3.1 or visit [...]]]></description> <content:encoded><![CDATA[WordPress 3.3.1 is now available. This maintenance release fixes <a href="http://core.trac.wordpress.org/query?status=closed&resolution=fixed&milestone=3.3.1&group=resolution&order=priority">15 issues</a> with WordPress 3.3, as well as a fix for a cross-site scripting vulnerability that affected version 3.3. Thanks to Joshua H., Hoang T., Stefan Zimmerman, Chris K., and the Go Daddy security team for responsibly disclosing the bug to our security team. <a href="http://wordpress.org/download/">Download 3.3.1</a> or visit Dashboard → Updates in your site admin. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2012/01/wordpress-3-3-1/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item> <title>WordPress 3.3 “Sonny”</title> <link>http://wordpress.org/news/2011/12/sonny/</link> <comments>http://wordpress.org/news/2011/12/sonny/#comments</comments> <pubDate>Mon, 12 Dec 2011 22:58:50 +0000</pubDate> <dc:creator>Matt Mullenweg</dc:creator> <category><![CDATA[Releases]]></category> <guid isPermaLink="false">http://wordpress.org/news/?p=2135</guid> <description><![CDATA[The latest and greatest version of the WordPress software — 3.3, named “Sonny” in honor of the great jazz saxophonist Sonny Stitt — is immediately available for download or update inside your WordPress dashboard. WordPress has had over 65 million downloads since version 3.0 was released, and in this third major iteration we’ve added significant [...]]]></description> <content:encoded><![CDATA[The latest and greatest version of the WordPress software — 3.3, named “Sonny” in honor of the great jazz saxophonist Sonny Stitt — is <a href="http://wordpress.org/download/">immediately available for download</a> or update inside your WordPress dashboard. WordPress has had over 65 million downloads since version 3.0 was released, and in this third major iteration we’ve added significant polish around the new user experience, navigation, uploading, and imports. Check out this short video that summarizes the things we think you’ll find are the cat’s pajamas: <div id="v-I7NAw9Zk-1" class="video-player"><embed id="v-I7NAw9Zk-1-video" src="http://s0.videopress.com/player.swf?v=1.03&guid=I7NAw9Zk&isDynamicSeeking=true" type="application/x-shockwave-flash" width="692" height="388" title="Introducing WordPress 3.3 "Sonny"" wmode="direct" seamlesstabbing="true" allowfullscreen="true" allowscriptaccess="always" overstretch="true"></embed></div> <h3>For Users</h3> Experienced users will appreciate the new drag-and-drop uploader, hover menus for the navigation, the new toolbar, improved co-editing support, and the new Tumblr importer. We’ve also been thinking a ton about what the WordPress experience is like for people completely new to the software. Version 3.3 has significant improvements there with pointer tips for new features included in each update, a friendly welcome message for first-time users, and revamped help tabs throughout the interface. Finally we’ve improved the dashboard experience on the iPad and other tablets with better touch support. <h3>For Developers</h3> There is a ton of candy for developers as well. I’d recommend starting your exploration with the <a href="http://codex.wordpress.org/Function_Reference/wp_editor">new editor API</a>, new jQuery version, better ways to hook into the help screens, more performant post-slug-only permalinks, and of course the entire list of improvements <a href="http://codex.wordpress.org/Version_3.3">on the Codex</a> and <a href="http://core.trac.wordpress.org/milestone/3.3">in Trac</a>. <h3>Roll the Credits</h3> The Credits tab on the new About WordPress screen in the WordPress dashboard provides recognition for contributors to each release, but we like to thank them here as well. <a href="http://profiles.wordpress.org/users/aaroncampbell">Aaron D. Campbell</a>, <a href="http://profiles.wordpress.org/users/jorbin">Aaron Jorbin</a>, <a href="http://profiles.wordpress.org/users/adambackstrom">Adam Backstrom</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/alexkingorg">Alex King</a>, <a href="http://profiles.wordpress.org/users/viper007bond">Alex Mills (Viper007Bond)</a>, <a href="http://profiles.wordpress.org/users/amereservant">amereservant</a>, <a href="http://profiles.wordpress.org/users/ampt">ampt</a>, <a href="http://profiles.wordpress.org/users/lordandrei">Andrei Freeman</a>, <a href="http://profiles.wordpress.org/users/arena">Andre Renaut</a>, <a href="http://profiles.wordpress.org/users/andrewfrazier">andrewfrazier</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">Andrew Ryno</a>, <a href="http://profiles.wordpress.org/users/andy">Andy Skelton</a>, <a href="http://profiles.wordpress.org/users/lumination">Anthony Atkinson</a>, <a href="http://profiles.wordpress.org/users/filosofo">Austin Matzko</a>, <a href="http://profiles.wordpress.org/users/simek">Bartosz Kaszubowski</a>, <a href="http://profiles.wordpress.org/users/benbalter">Benjamin J. Balter</a>, <a href="http://profiles.wordpress.org/users/brandondove">Brandon Dove</a>, <a href="http://profiles.wordpress.org/users/carlospaulino">carlospaulino</a>, <a href="http://profiles.wordpress.org/users/caspie">Caspie</a>, <a href="http://profiles.wordpress.org/users/cebradesign">cebradesign</a>, <a href="http://profiles.wordpress.org/users/chexee">Chelsea Otakan</a>, <a href="http://profiles.wordpress.org/users/chipbennett">Chip Bennett</a>, <a href="http://profiles.wordpress.org/users/chrisbliss18">Chris Jean</a>, <a href="http://profiles.wordpress.org/users/coenjacobs">Coen Jacobs</a>, <a href="http://profiles.wordpress.org/users/cgrymala">Curtiss Grymala</a>, <a href="http://profiles.wordpress.org/users/danielbachhuber">Daniel Bachhuber</a>, <a href="http://profiles.wordpress.org/users/koopersmith">Daryl Koopersmith</a>, <a href="http://profiles.wordpress.org/users/dllh">Daryl L. L. Houston</a>, <a href="http://profiles.wordpress.org/users/davecpage">David</a>, <a href="http://profiles.wordpress.org/users/dcowgill">David Cowgill</a>, <a href="http://profiles.wordpress.org/users/dgwyer">David Gwyer</a>, <a href="http://profiles.wordpress.org/users/damst">Da^MsT</a>, <a href="http://profiles.wordpress.org/users/deltafactory">deltafactory</a>, <a href="http://profiles.wordpress.org/users/demetris">demetris</a>, <a href="http://profiles.wordpress.org/users/valendesigns">Derek Herman</a>, <a href="http://profiles.wordpress.org/users/devinreams">Devin Reams</a>, <a href="http://profiles.wordpress.org/users/adeptris">Digital Raindrops</a>, <a href="http://profiles.wordpress.org/users/dd32">Dion Hulse (@dd32)</a>, <a href="http://profiles.wordpress.org/users/ocean90">Dominik Schilling (ocean90)</a>, <a href="http://profiles.wordpress.org/users/dougwrites">Doug Provencio</a>, <a href="http://profiles.wordpress.org/users/dragoonis">dragoonis</a>, <a href="http://profiles.wordpress.org/users/drewapicture">DrewAPicture</a>, <a href="http://profiles.wordpress.org/users/cyberhobo">Dylan Kuhn</a>, <a href="http://profiles.wordpress.org/users/eduplessis">eduplessis</a>, <a href="http://profiles.wordpress.org/users/eightamrock">Eightamrock</a>, <a href="http://profiles.wordpress.org/users/eko-fr">eko-fr</a>, <a href="http://profiles.wordpress.org/users/elpie">Elpie</a>, <a href="http://profiles.wordpress.org/users/elyobo">elyobo</a>, <a href="http://profiles.wordpress.org/users/empireoflight">Empireoflight</a>, <a href="http://profiles.wordpress.org/users/ethitter">Erick Hitter</a>, <a href="http://profiles.wordpress.org/users/ericmann">Eric Mann</a>, <a href="http://profiles.wordpress.org/users/ejdanderson">Evan Anderson</a>, <a href="http://profiles.wordpress.org/users/evansolomon">Evan Solomon</a>, <a href="http://profiles.wordpress.org/users/fonglh">fonglh</a>, <a href="http://profiles.wordpress.org/users/garyc40">garyc40</a>, <a href="http://profiles.wordpress.org/users/garyj">Gary Jones</a>, <a href="http://profiles.wordpress.org/users/logiclord">Gaurav Aggarwal</a>, <a href="http://profiles.wordpress.org/users/georgestephanis">George Stephanis</a>, <a href="http://profiles.wordpress.org/users/goldenapples">goldenapples</a>, <a href="http://profiles.wordpress.org/users/goto10">goto10</a>, <a href="http://profiles.wordpress.org/users/hakre">hakre</a>, <a href="http://profiles.wordpress.org/users/helenyhou">Helen Hou-Sandi</a>, <a href="http://profiles.wordpress.org/users/iandstewart">Ian Stewart</a>, <a href="http://profiles.wordpress.org/users/ipstenu">Ipstenu</a>, <a href="http://profiles.wordpress.org/users/madjax">Jackson</a>, <a href="http://profiles.wordpress.org/users/jacobwg">Jacob Gillespie</a>, <a href="http://profiles.wordpress.org/users/jakemgold">Jake Goldman</a>, <a href="http://profiles.wordpress.org/users/jamescollins">James Collins</a>, <a href="http://profiles.wordpress.org/users/jane">Jane Wells</a>, <a href="http://profiles.wordpress.org/users/jeremyclarke">jeremyclarke</a>, <a href="http://profiles.wordpress.org/users/jayjdk">Jesper Johansen (Jayjdk)</a>, <a href="http://profiles.wordpress.org/users/jgadbois">jgadbois</a>, <a href="http://profiles.wordpress.org/users/jick">Jick</a>, <a href="http://profiles.wordpress.org/users/joehoyle">Joe Hoyle</a>, <a href="http://profiles.wordpress.org/users/johnbillion">John Blackbourn</a>, <a href="http://profiles.wordpress.org/users/vegasgeek">John Hawkins</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/johnpbloch">John P. Bloch</a>, <a href="http://profiles.wordpress.org/users/duck_">Jon Cave</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/jtclarke">jtclarke</a>, <a href="http://profiles.wordpress.org/users/yuraz">Jurica Zuanovic</a>, <a href="http://profiles.wordpress.org/users/justindgivens">Justin Givens</a>, <a href="http://profiles.wordpress.org/users/justinsainton">Justin Sainton</a>, <a href="http://profiles.wordpress.org/users/trepmal">Kailey Lampert (trepmal)</a>, <a href="http://profiles.wordpress.org/users/kevinb">kevinB</a>, <a href="http://profiles.wordpress.org/users/kitchin">kitchin</a>, <a href="http://profiles.wordpress.org/users/kovshenin">Konstantin Kovshenin</a>, <a href="http://profiles.wordpress.org/users/tenpura">Kuraishi</a>, <a href="http://profiles.wordpress.org/users/kurtpayne">Kurt Payne</a>, <a href="http://profiles.wordpress.org/users/lancewillett">Lance Willett</a>, <a href="http://profiles.wordpress.org/users/latz">Latz</a>, <a href="http://profiles.wordpress.org/users/linuxologos">linuxologos</a>, <a href="http://profiles.wordpress.org/users/lloydbudd">Lloyd Budd</a>, <a href="http://profiles.wordpress.org/users/ldebrouwer">Luc De Brouwer</a>, <a href="http://profiles.wordpress.org/users/lukeschlather">lukeschlather</a>, <a href="http://profiles.wordpress.org/users/mako09">Mako</a>, <a href="http://profiles.wordpress.org/users/settle">Mantas Malcius</a>, <a href="http://profiles.wordpress.org/users/marcuspope">MarcusPope</a>, <a href="http://profiles.wordpress.org/users/mark-k">mark-k</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/markoheijnen">Marko Heijnen</a>, <a href="http://profiles.wordpress.org/users/tfnab">Martin Lormes</a>, <a href="http://profiles.wordpress.org/users/masonjames">masonjames</a>, <a href="http://profiles.wordpress.org/users/matveb">Matias Ventura</a>, <a href="http://profiles.wordpress.org/users/matt">Matt Mullenweg</a>, <a href="http://profiles.wordpress.org/users/iammattthomas">Matt Thomas</a>, <a href="http://profiles.wordpress.org/users/mattwiebe">Matt Wiebe</a>, <a href="http://profiles.wordpress.org/users/mattyrob">MattyRob</a>, <a href="http://profiles.wordpress.org/users/merty">Mert Yazicioglu</a>, <a href="http://profiles.wordpress.org/users/mdawaffe">Michael Adams (mdawaffe)</a>, <a href="http://profiles.wordpress.org/users/mfields">Michael Fields</a>, <a href="http://profiles.wordpress.org/users/mau">Michal “Mau” Pliska</a>, <a href="http://profiles.wordpress.org/users/mbijon">Mike Bijon</a>, <a href="http://profiles.wordpress.org/users/dh-shredder">Mike Schroder</a>, <a href="http://profiles.wordpress.org/users/dimadin">Milan Dinic</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/mhauan">Morten Hauan</a>, <a href="http://profiles.wordpress.org/users/usermrpapa">Mr Papa</a>, <a href="http://profiles.wordpress.org/users/mrtorrent">mrtorrent</a>, <a href="http://profiles.wordpress.org/users/Nao">Naoko McCracken</a>, <a href="http://profiles.wordpress.org/users/natebedortha">natebedortha</a>, <a href="http://profiles.wordpress.org/users/nbachiyski">Nikolay Bachiyski</a>, <a href="http://profiles.wordpress.org/users/olivm">olivM</a>, <a href="http://profiles.wordpress.org/users/olleicua">olleicua</a>, <a href="http://profiles.wordpress.org/users/otto42">Otto</a>, <a href="http://profiles.wordpress.org/users/pagesimplify">pagesimplify</a>, <a href="http://profiles.wordpress.org/users/paulhastings0">paulhastings0</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/peterwilsoncc">peterwilsoncc</a>, <a href="http://profiles.wordpress.org/users/ppaire">ppaire</a>, <a href="http://profiles.wordpress.org/users/ptahdunbar">Ptah Dunbar</a>, <a href="http://profiles.wordpress.org/users/r-a-y">r-a-y</a>, <a href="http://profiles.wordpress.org/users/ramiy">Rami Y</a>, <a href="http://profiles.wordpress.org/users/rasheed">Rasheed Bydousi</a>, <a href="http://profiles.wordpress.org/users/miqrogroove">Robert Chapin (miqrogroove)</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/ruslany">ruslany</a>, <a href="http://profiles.wordpress.org/users/ryan">Ryan Boren</a>, <a href="http://profiles.wordpress.org/users/ryanhellyer">ryanhellyer</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/gluten">Sam Margulies</a>, <a href="http://profiles.wordpress.org/users/saracannon">saracannon</a>, <a href="http://profiles.wordpress.org/users/scottbasgaard">Scott Basgaard</a>, <a href="http://profiles.wordpress.org/users/sbressler">Scott Bressler</a>, <a href="http://profiles.wordpress.org/users/l3rady">Scott Cariss</a>, <a href="http://profiles.wordpress.org/users/scottconnerly">scottconnerly</a>, <a href="http://profiles.wordpress.org/users/coffee2code">Scott Reilly</a>, <a href="http://profiles.wordpress.org/users/wonderboymusic">Scott Taylor</a>, <a href="http://profiles.wordpress.org/users/scribu">scribu</a>, <a href="http://profiles.wordpress.org/users/sergeybiryukov">Sergey Biryukov</a>, <a href="http://profiles.wordpress.org/users/designsimply">Sheri Bigelow</a>, <a href="http://profiles.wordpress.org/users/simonwheatley">Simon Wheatley</a>, <a href="http://profiles.wordpress.org/users/sirzooro">sirzooro</a>, <a href="http://profiles.wordpress.org/users/sillybean">Stephanie Leary</a>, <a href="http://profiles.wordpress.org/users/tech163">tech163</a>, <a href="http://profiles.wordpress.org/users/thedeadmedic">TheDeadMedic</a>, <a href="http://profiles.wordpress.org/users/tmoorewp">Tim Moore</a>, <a href="http://profiles.wordpress.org/users/tomauger">Tom Auger</a>, <a href="http://profiles.wordpress.org/users/ansimation">Travis Ballard</a>, <a href="http://profiles.wordpress.org/users/sorich87">Ulrich Sossou</a>, <a href="http://profiles.wordpress.org/users/vnsavage">vnsavage</a>, <a href="http://profiles.wordpress.org/users/wpweaver">wpweaver</a>, <a href="http://profiles.wordpress.org/users/wraithkenny">WraithKenny</a>, <a href="http://profiles.wordpress.org/users/yoavf">Yoav Farhi</a>, and <a href="http://profiles.wordpress.org/users/vanillalounge">Ze Fontainhas</a>. As well, we’d like to give a shout out to these users who have been particularly active <a href="http://wordpress.org/support/">on the support forums</a> since the release of 3.2: <a href="http://profiles.wordpress.org/users/alchymyth">alchymyth</a>, <a href="http://profiles.wordpress.org/users/andrea_r">Andrea_r</a>, <a href="http://profiles.wordpress.org/users/claytonjames">ClaytonJames</a>, <a href="http://profiles.wordpress.org/users/numeeja">cubecolour</a>, <a href="http://profiles.wordpress.org/users/eranmiller">Eran Miller</a>, <a href="http://profiles.wordpress.org/users/esmi">esmi</a>, <a href="http://profiles.wordpress.org/users/fredericktownes">Frederick Townes</a>, <a href="http://profiles.wordpress.org/users/govpatel">govpatel</a>, <a href="http://profiles.wordpress.org/users/ipstenu">Ipstenu</a>, <a href="http://profiles.wordpress.org/users/keesiemeijer">keesiemeijer</a>, <a href="http://profiles.wordpress.org/users/kmessinger">kmessinger</a>, <a href="http://profiles.wordpress.org/users/netweblogic">Marcus</a>, <a href="http://profiles.wordpress.org/users/otto42">Otto</a>, <a href="http://profiles.wordpress.org/users/peredur">peredur</a>, <a href="http://profiles.wordpress.org/users/rvoodoo">Rev. Voodoo</a>, <a href="http://profiles.wordpress.org/users/samboll">Samuel B</a>, <a href="http://profiles.wordpress.org/users/tobiasbg">Tobias</a>, <a href="http://profiles.wordpress.org/users/vtxyzzy">vtxyzzy</a>, and <a href="http://profiles.wordpress.org/users/zoonini">zoonini</a>. ]]></content:encoded> <wfw:commentRss>http://wordpress.org/news/2011/12/sonny/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>