Yo yo. Call for speakers for WCSF. Note that this year devs are the main attraction (Saturday at conference center is all dev, plus hack days before/after). http://2011.sf.wordcamp.org/call-for-speakers/
Who should we put on stage (and subsequently on wordpress.tv) to inspire developers?
There have been two major releases of the jQuery library during this release cycle. WordPress 3.1 includes jQuery 1.4.4. WordPress 3.2 will include jQuery 1.6.1. The new jQuery is faster and better but also has some major changes. The two most important changes that all plugin and theme authors must test for are:
$('input[name=submit]') will not work. It needs to be $('input[name="submit"]').attr('checked', '') fails (that used to remove the checked=”checked” from checkboxes). More details and a list of all affected properties are on the jQuery’s blog.
Are we using 1.6.1?
From the post:
WordPress 3.1 includes jQuery 1.4.4. WordPress 3.2 will include jQuery 1.6.1.
Yep! It’s going to be jQuery 1.6.1 in 3.2
http://core.trac.wordpress.org/ticket/17311
great jQuery 1.6.1 will power the WP now….
Two queries…
Will you be using the min JS?
Your use of $ there doesn’t happen to mean you’ll be supporting that in 3.2….?
WordPress has always used the minified version, have a look 
What do you mean by “supporting”? Making $ belong to jQuery in the global scope and breaking Prototype.js? Don’t think we want to break all plugins that use Prototype.
Sorry. You’re right, I didn’t actually look at the code.
And yeah, I woulda been surprised, but was just hoping.
So let’s say your plugin uses .attr(‘checked’, ”). What do you do to make sure that it works for version 3.2 and lower?
GSoC Student Chat Today! In half an hour (17:00 UTC) in #wordpress-gsoc, hear about, ask questions regarding, and get to know the developers of these student projects:
Note: Stas Suscov (learn.wordpress.org) is being rescheduled for next week along with the students who missed their chats this week.
Howdy 3.2 contributors: The new credits page in 3.2 (#17384) now pulls your name from your WP.org profile. So if you want your full name to show up, go update it.
Mine is here. When you’re logged in, the Edit link on your own profile and the subsequent name field are both rather obvious.
Potential contributors: This enough incentive to contribute to 3.2? Go grab the beta.
(Fine print: Server cache updates every 12 hours. Core cache updates once a week, so you’ll need to flush the transient to see it on your own install.)
If you have opened this page before the change, you will need to clear the transient to see the new page.
A few weeks ago a change was deployed to the plugins directory. If you click “Other Versions” on the sidebar when viewing a plugin, there’s a new section called “Browse the Code” with three links to:
Hopefully this makes it easier to find the right URL for plugin checkouts, and to browse the code.
Check it out here.
This is fantastic @nacin! I’ve bumped my… elbow on this many times previously.
ooo buddy! I understand you perfectly 
thanks to those tips Nacin!
I always go from the Trac /log/ to the /browser/ URL, I want to read the code as it currently is, but with the nice browse interface that Trac offers. Have you considered not linking to the SVN page but to the Trac browser page? The “Repository URL” link at the top of the page should then maybe link to the real SVN URL, with an extra “Directory URL” that links to the plugin directory page.
This was designed to provide a direct link to the SVN, for such operations, rather than for actually browsing the code. I tried to not keep the list of links from becoming too bloated, and considering that you can get from /log/ to /browser/ pretty easily, I think it’s currently pretty good. Maybe that’s just me though.
I would actually prefer the Trac browse page (and thus two Trac links) more than the two different SVN links. But as you said, maybe that’s just me.
Well done! That will definitely make getting the SVN URL much easier.
A couple of hours ago, the first 3.2 beta release hit the ground. You know the drill: you break it, you buy it. Oh, wait. I meant, you break it, report it, and we all work together to fix it. Would be great to get more people helping with bug fixes between now and RC. Tell your friends.
Hello there. Reporting some minor details:
WYSIWYGRN is no more. In editor-style (I have tested twenty ten and twenty eleven) what you see when editing and when published is not the same.
In twenty eleven, when you change the link color in Theme Options, it doesn’t change in the editor.
In the twenty eleven editor, strong + a looks like a, without the bold.
Could you please use the normal bug reporting channels as listed in the announcement post on .org? This P2 is not set up to be a bug tracker. Thanks!
Sure. Sorry.
Whe is scheduled RC1 ?
Check the Project Schedule link in the sidebar widget labeled 3.2 Dev Cycle.
nice !
Hello folks. The GSoC students have ironed out scope and schedule for their projects, and are ready to tell you about them and answer questions and/or hear suggestions. The links below have the project descriptions and schedules. Each student will hold a Q&A in IRC according to the schedule below. Please come and show our GSoC students some support!
irc.freenode.net #wordpress-gsoc
Tuesday 17:00 UTC:
Anirudh S. (Refresh Android UI) – Dan Roundhill, Isaac
Mert Yazicioglu (WordPress Move) – Pete Mall, Brian Layman
Wojtek Szutnik (Enhanced Emails) – Aaron Campbell, Justin
Wednesday 14:00 UTC:
David Julia (Template Versioning) – Ocean90, Nacin, Koop
Jakub Tyrcha (Full-throttle Trac Annihilation) – Dion, duck_, scribu, Nacin
Marko Novakovic (Language Packs) – Nacin, Nikolay
Thursday 17:00 UTC:
Jacob Gillespie (File Uploader Upgrade) – Koop, azaozz
Lukasz Koprowski (Threaded Comments) – Westi, Koop
Mihai Chereji (Local Storage Drafts Backup) – Filosofo, mitcho, azaozz and Koop
Friday 17:00 UTC:
Ben Balter (Document Revisions) – Mitcho, duck_, Jorbin
Prasath Nadarajah (Extending WP Webservices) – Thorsten, Eric Mann
Stas Suscov (learn.wordpress.org) – Jtrip, Jeremy Boggs
Oh, and re suggestions: Please be respectful of students and mentors and try not to assume that they don’t know what they’re doing. Sometimes it’s easy to get carried away — out of the best intentions — when giving advice, so once a suggestion has been heard, leave it to the students and mentors to decide if they’ll take the advice or not. Thanks!
@otto42: in theme repo on .org, search results for “Twenty Ten” put Twenty Ten as result #6. Higher results are Freedream2010, 2010 Weaver, Third Style, Clear Style, and Atmosphere 2010. Can you do some magic so exact matches come up first?
I will take a look at it.
Gracias!
Made a change to push exact slug/title matches to the top.
Just a heads up. WP trunk uses jQuery 1.5.2. 1.5.2 no longer allows selectors of the form [property=value]. These selectors now require quotes: [property="value"]. Unquoted values will result in “uncaught exception: Syntax error, unrecognized expression: [property=value]“. Check your plugins against 1.5.2.
Now that jQuery 1.6 is released, is that likely to make it in to 3.2 or has it missed the cut?
1.6 does make some changes that might break compatibility – see the release notes about attr() and prop().
jQuery 1.6 was released a few days ago, too:
patch #17311
It won’t be going into 3.2 in all likelihood though because it will require more robust testing.
Or maybe it will…
jQuery 1.6 has some features that would require rewriting most of the code that uses it (thinking mostly about all the plugins that use jQuery). 1.6.1 fixes that and is currently in RC. Hopefully it will be released in time for inclusion in WordPress 3.2.
Oh, and 1.6 still has the same requirement like 1.5.2, all [property=value] selectors have to be fixed.
I put out a call from the @wordpress Twitter account yesterday asking for accessibility volunteers. Already getting some helpful feedback. Anyone not working on a 3.2 feature already could help out by working on one of the accessibility issues.
ChrisH, 
arena, 
Otto, and 
Otto 6:37 pm on May 31, 2011 Permalink |
I’ve never spoken at a WordCamp, but I’m willing to speak on whatever topic is needed. I’m not particularly good at coming up with topic ideas though, so suggestions would be nice.
Aaron Brazell 6:51 pm on May 31, 2011 Permalink |
Submitted.
scribu 7:11 pm on May 31, 2011 Permalink |
It would be nice to bring someone from the Ubuntu community. Jono Bacon, for example.
Stephane Daury 12:53 am on June 1, 2011 Permalink |
Jane Wells 2:06 pm on June 1, 2011 Permalink |
That’s heresy. And ultra-sad.