Suggest agenda items for Nov 5th dev chat
Updates from October, 2009 Toggle Comment Threads | Keyboard Shortcuts
-
Peter Westwood
-
Jane Wells
Note to self: schedule bug hunts/patch testing sprints for Sun-Mon a week from now and Thurs-Sat in mid-November, per IRC dev chat today. Announce on dev blog tomorrow.
-
Peter Westwood
Agenda for Oct 29th dev chat:
- Custom post type ui – Lari
- Security only patches – Beau
- Beta readiness – westi
- Memory requirements – Jeffro
- Update announcement improvements – demetris
-
Peter Westwood
Suggest agenda items for Oct 29th dev chat
-
Lari
Custom post type ui. Can it make it to 2.9?
-
Alex M. (Viper007Bond)
2.9 is feature frozen.
-
-
Beau
Doing security-only patches as a way of 1. maintaining some level of support for older versions of WP, and 2. being “safer” to implement fully-automated core upgrades
-
Alex M. (Viper007Bond)
Isn’t that what was done with the 2.0.x branch? Turned out to be a ton of work and not really worth the trouble.
http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/
-
-
Peter Westwood
Review status of features with regard to beta readiness
-
Jeffro
I’m noticing more and more with queries in the WordPress support forums of folks who upgrade WordPress only to be greeted with memory limit exhausted errors. I had this problem myself when I upgraded to the version of WordPress once SimplePie was used as the feed parser. I had to go from 32 megs to 64. Is it possible that this information needs to be added to the minimum requirements page on WordPress.org? http://wordpress.org/about/requirements/
-
Matt Martz
I think one thing that people tend to forget is that they should deactivate all plugins before performing an upgrade. Did you perform this step when you did the upgrade? Maybe what we should do is detect whether or not plugins were deactivated. If not, then make a backup of the option containing the active plugins, clear the option, upgrade, then restore it. Or perhaps add a check to see if we are upgrading and then not load plugins if that constant is set. Just some ideas.
-
demetris
Deactivating plugins before upgrading is good advice in theory, but in practice it is problematic, since very often plugins offer functionality that is integral to a site. You can’t just deactivate them.
For upgrade issues caused by plugins, another idea would be to have a “Known Issues” part in the release notes. If a prominent, popular plugin breaks something essential in WordPress when upgrading (and WordPress has enough prerelease testers to catch such issues for popular plugins), then it could be mentioned as a Known Issue.
-
Eric Marden
@demetris
Is that what .maintenance is for? http://sivel.net/2009/06/wordpress-maintenance-mode-without-a-plugin/
-
-
-
demetris
1. Improve template for new release announcements
2. Link to release announcement from admin upgrade notice, something like: [Read what is new] or [Click to upgrade]
-
-
Matt
I updated the access flags for #wordpress so more people can help out there when there is trouble. To remind folks, our policy is for people not to be “opped” all the time, only when needed to set/change things. Here are the new folks with access:
sivel
Viper007Bond
bazza
MarkJaquith
Ozh-
Mark Jaquith
I wasn’t up on ChanServ… appears that op/deop works like this:
- /msg ChanServ OP #wordpress
- /msg ChanServ DEOP #wordpress
-
Matt
Thanks Matt! I have cleared out all of the old outdated bans, and set a few new modes on the channel. If anyone has any questions about the commands and such feel free to ask me on IRC.
-
-
Peter Westwood
Agenda for Oct 22nd dev chat:
- Additional non-oembed sites – Viper007Bond
- Upgrade notification in core
- Trac voting
- Multiple custom image sizes with retroactive image reprocessing – Scribu
- Mailing lists
- #WordPress ops
- Trac configuration
-
Ryan Boren
Prepping 2.8.5. Get the beta here.
Changes:
- Fix for trackback DOS
- Removal of permalink_structure eval
- Remove some create_function() calls
- Disallow unfiltered uploads for admins by default. Enable it again with define(‘ALLOW_UNFILTERED_UPLOADS’, true); in wp-config.php
- Add extra escaping here and there for defense in depth
- Retire two old importers
- A few small bug fixes
This is mainly a security hardening release done as part of our always ongoing security audits. There’s nothing exciting in here unless you are concerned about the trackback DOS bug.
-
Jonathan Dingman
Keep up the great work Ryan! Good job on the fast and responsive release to the threat (even though in my mind, not a serious one).
-
hakre
Well it was about time for some of those
. But it’s good to see them finally in!
hakre, and 
Peter Westwood
Suggest agenda items for Oct 22nd dev chat
-
Alex (Viper007Bond)
I’d like to hear any suggestions for additional non-oEmbed sites that people would like to see supported.
-
Bryan
It would be nice if oEmbed was backwards compatible with Viper’s Video Quicktags or any number of similar plugins that use shortcodes such as: . Otherwise plugin-dependent users will not be able to utilize the native oEmbed features without re-editing many posts.
-
Alex M. (Viper007Bond)
As mentioned on my blog, WordPress can’t be expected to handle the infinite number of video related shortcodes out there. It’s up to plugins to create a bridge.
-
-
-
scribu
Set up an official poll: Upgrade notifications by mail into core.
It’s being discussed in wp-hackers, but with no conclusion.
-
JeffC
I would like to know if the up and down arrow votes for a ticket in Trac has any effect in terms of priority or attention it receives?
-
scribu
-
Massalha Shady
Hi, WP 2.8.5 Still slow. I spent a lot of time trying to fix it but with no success. And please, dont say plugins/mlugins, i have deleted all plugins – reset it – and Dashboard still SLOW??!?!? This is the pacth we need ASAP. because WP is great and have to continue that …
-
hakre
-
Matt
I’d like to discuss creating a new mailing list where the non hackers on the wp-hackers mailing list can take their discussions to. The name of the list doesn’t matter so much, Andy recommended wp-discuss. See this thread on wp-hackers for more information:
http://lists.automattic.com/pipermail/wp-hackers/2009-October/028097.html
-
Jeffro
This has been a long time coming. There is no place to discuss general information or ideas for WordPress. There is the ideas section but nahh, I’d like to see a mailing list just for feedback and discussion on topics or ideas. So I +1 for wp-discuss
-
-
Matt
Meeting Task: #wordpress OPs for sivel and Viper007Bond If Matt is in attendance
-
Jeffro
Persistence will pay off eventually
-
-
hakre
I would like to have the xmlrpc interface in wordpress core trac use the eclipse mylyn trac connector via xmlrpc. Currently I need to use SSL (mainly for auth) and that is slow (and I think it eats server resources). This is a nice system for an upcomming patch-run if anyone is interested for eclipse/wp infos, checkout my codex page.
Mark Jaquith
Two big patches for 2.9 just went in. […
Two big patches for 2.9 just went in.
[12025] by Andy Peatling allows themes to use register_theme_directory() to specify a wp-content-relative path containing theme directories. WP will additionally scan that. Primary use case is BuddyPress adding its themes without requiring copying.
[12023] by Viper007Bond enables smart embeds along with oEmbed support. For instance, to embed a YouTube or Vimeo video, just paste the URL in your browser on a blank line. It’ll grab the correct embed code for you. Much easier than wrangling with embed code vomit or remembering special shortcodes.
Denis de Bernardy, 
-
Alex (Viper007Bond)
Writing up a post for my blog right now that goes more into depth on the new embeds feature, how to use it, how plugins can interact with it, etc.
-
Alex (Viper007Bond)
Here’s the long post: http://v007.me/1a5
-
Alex Leonard
Nice article! Good to see the functionality of this in action
-
-
-
Otto
Sweet baby Jebus! I am just now finding out about oEmbed. Brilliant. Never would have occurred to me to look for such a thing.
Upgrading to trunk now.
-
Denis de Bernardy
Hat Alex for the built-in oEmbed.
Peter Westwood
Suggest agenda items for Oct 15th dev chat
johnmyr, -
filosofo
I’m not sure what to call it exactly—”templating” is too strong a term—but the admin needs to abstract more of the way the markup is generated.
1) Too much stuff is hard-coded
2) Too much stuff is repeated
3) Plugin authors shouldn’t have to make common admin form elements by hand
4) We’re already heading that way somewhat with options registration and media forms-
Ryan McCue
Agreed, but we should also try and stick away from forcing the user to jump through hoops to use it. I seem to recall Drupal’s form API sucking in this sense.
-
Ryan McCue
Durp, ignore this, missed the date.
-
-
-
Matt
Meeting Task: #wordpress OPs (if Matt is in attendance)
-
Jeff Waugh
In the “hopefully simple patches for 2.9″ category: Internal support for conditional scripts (same as existing conditional style support), #10891
-
demetris
Some more thoughts from me about WP.org pages…
1. http://wordpress.org/about/testimonials/
This should be removed. It’s too old and half of the links are dead. It could be archived somewhere for historical purposes.
2. http://wordpress.org/hosting/
This could be improved.
2a. There is no need to quote all this promotional copy for each company.
2b. The recommendations could be better. Now wp.org recommends mostly hosts of the over-promising variety (“Unlimited this, unlimited that, etc. etc.”), hosts that for the most part you can find about at any of the many “review” sites on the web. But that’s not the only kind of affordable web-hosting, and maybe WP.org could do a favour to itself and to the people who trust it by considering the other kind as well.
Two examples from my limited experience and from a bit of research I’ve done, to explain what I’m thinking about:
WebFaction — http://www.webfaction.com/ — is one of only two companies I know of that offer gzipping and PHP caching on shared-hosting packages. They also use Nginx for static content. (Other than WebFaction and Utopian.net, I know of no other company that sells shared-hosting with either gzipping or PHP caching.) I’ve only seen praise about them (real praise, not from “review” sites) and they are recommended by people I trust. They have a modern setup with all kinds of software and they seem to be a straight-up company. Their cheapest package is $102/year.
A Small Orange — http://asmallorange.com/ — are often recommended by knowledgeable members of the wp.org forums, especially for their good support. Interestingly, they also offer what must be the cheapest reliable package on the market: $25/year (or just $20 with a discount code, contact me if you are interested) with everything in, even SSH access! Of course, as with any serious provider, the package has limits: 75MB storage and 3GΒ/month traffic. Which will not be appealing to the naive eye, but, to my eyes, is a sign that I have to do an honest, straight-up company.
Here are the uptime stats for a test site I host with A Small Orange, on the Tiny package, monitored at intervals of 1 minute:
http://www.pingdom.com/reports/n1gtfjjbrld8/check_overview/?name=op109.net-ASO-Thomas
Not bad for 20 dollars a year!
One final note: Both ASO and WebFaction offer referral fees, which means that WP.org stands to gain monetarily as well.
-
johnmyr
http://core.trac.wordpress.org/ticket/10958
Some plugins have unnatural peaks of 20.000 downloads pr day, making the stats unreliable as a measure of a plugins trust within the community. Should be acted upon.
-
johnmyr
-
Bryan 10:03 pm on October 31, 2009 Permalink |
Need fresh patch for inline documentation corrections. http://core.trac.wordpress.org/ticket/6362
Eric Marden 7:12 am on November 11, 2009 Permalink |
@bryan – just replying to say that patch was refreshed
Nicolas Kuttler 1:18 pm on November 3, 2009 Permalink |
The plugin compatibilty beta shows all tags that exist. This is fine, but I think it should select the latest stable tag by default, not the newest that exists. I like to tag experimental versions and versions for translators, but for 99.9% of all visitors only the compatibility of the latest stable release is relevant.
(If 0.1 is stable and there is a 0.1.1 it will be displayed instead by default)
Jane Wells 1:26 am on November 5, 2009 Permalink |
I think people assume the most recent version number is the stable one they should be using, since that is how WordPress itself works. The default should be the most recent on both menus for a consistent experience. Is something isn’t stable, maybe it doesn’t belong in the repo yet?
Peter Westwood 7:02 am on November 5, 2009 Permalink
This is not quite the case. The readme.txt format allows the plugin author to say which is the stable tag and that is what is presented as the latest version for download.
That should be the default version in the dropdown
Jane Wells 1:27 am on November 5, 2009 Permalink |
Bug hunt /patch testing sprint Nov 5-7. ID who will be on to review things for commit, etc.
Peter Westwood 8:16 pm on November 5, 2009 Permalink |
Discuss “Discourage plugin authors calling wp-config.php directly” –
http://core.trac.wordpress.org/ticket/11059
demetris 8:54 pm on November 5, 2009 Permalink |
1. I have drafted a proposed structure for release announcements (as I promised in the last meeting)
2. If there are time slots left, I would like to see some feedback on the new Hello World post: http://core.trac.wordpress.org/ticket/11008