Updates from Mark RSS Toggle Comment Threads | Keyboard Shortcuts
-
Mark Jaquith
-
Ramoonus
release notes?
-
Ryan
Lol, this broke my site something wicked! I’ve been testing the trunk install for about a month now and am yet to find a single bug!
-
gillesv
Does the_post_image() work yet? I tried it locally but am seeing nothing?
-
Aaron Brazell
your theme would need to support it with the add_theme_support() function.
-
-
Ajay
I can’t download it using the plugin
-
Kirk M
If you mean the WP-Beta-Tester plugin I believe that only deals with point release nightlies (currently states it’s a development version of 2.8.6 or that’s what it says when I just checked it on my test site anyway) and bleeding edge nightlies (2.9 rare). I don’t think you can use it to download beta builds or at least I can’t.
-
Kirk M
Alex – That’s what I thought although I did want to check it out. Just FYI: I switched the plugin back to “Bleeding edge” and auto upgraded to 2.9 beta 1
Go figure.
-
-
Kirk M
Mark – Just to avoid confusion, the “version.php” file in the .zip file for 2.9 beta 1 shows as “2.9 (rare)” and not “2.9 beta 1″. Some testers are being thrown off by this as this. Was this intentional or just something that was missed?
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.
Mark Jaquith
Agenda for 2009/09/03 dev chat:
- Discuss WP.org plugin directory policies. Should have Mark Riley present. As people are beginning to experiment with GPL-compliant business models around plugins, some issues should be clarified WRT the plugin directory:
– Plugins that promote expanded services by the author (“have me customize this plugin for you!”)
– Plugins that ask for monetary donations in the admin UI
– Plugins that are a “lite” version of a premium GPL plugin/support bundle
Mark Jaquith
The way the edit lock works now, if you close your browser with the post open, the lock will stay in effect until it times out. Might it not be better if we shortened the edit lock time to something like 120 seconds and kept it locked via an XHR every 90 seconds that the edit screen for that post is open?
Mark Jaquith
Deprecated clean_url() in favor of esc_url(), and deprecated sanitize_url() in favor of esc_url_raw().
Mark Jaquith
Deprecated wp_specialchars() in favor of esc_html() (also: esc_html__() and esc_html_e()). Using wp_specialchars() with more than one param works for backwards compat. Also, esc_html() (or wp_specialchars() with one param) escapes quotes, just like esc_attr(). This buys security for plugin authors who were mistakenly using a one-param wp_specialchars() call in an HTML attribute. See this wp-hackers message for more detail.
Mark Jaquith
Standardizing and shortening the WP security escaping functions.
attribute_escape() is now esc_attr()
Additionally, you can do attribute escaping and translation in one go. Just add the translation function to the end. Like so:
esc_attr__()— translate and return, attribute-escaped.esc_attr_e()— translate and echo, attribute-escaped.
Will be following up with esc_html (with __() and _e() variants), esc_url(), maybe some more. Will be nice, short, predictable, and allow you do translate/escape in one go without a lot of nested parenthesis.
Leandro Vieira Pinho
Why not escape_attr than esc_attr?. Write escape is more intuitive than esc.
Mark Jaquith
Changed Publish Module style to offer more flexibility. Having the columns side-by-side was too cramped and would have been a nightmare for translators.
Mark Jaquith
wp_title() now consistently handles reverse order title breadcrumbs. So in “right” mode, you get “July (sep) 2008 (sep) Blogname.” SEO plugin authors may want to take note.
Baris Unver
I agree with @monika.
Mark Jaquith
It is better for SEO to have more specific information earlier in the title. This won’t change anything if your theme doesn’t use reverse title breadcrumbs. If it does, it’ll make them more consistent.
Baris Unver
My English is not very good, so I need to ask: Will wp_title function have another parameter to reverse the order, or will it be reversed by default?
monika
Mark I am a seo and a very good one and so I say: this is not useful for seo to have the blog title in every title between head and /head.
title must be unique –
regards
Monika
Mark Jaquith
Baris, the order is NOT reversed by default. It’s manually reversed in the bundled themes (Default and Classic), with the last parameter.
monika, you’re free to omit it when designing themes. This only really affects the bundled themes.
Mark Jaquith
Added canonical URL redirection for feeds. Now requests for /index.php?feed=atom or /wp-atom.php will redirect to the correct location.
-
Nathan Rice
Nice! Was wondering about that.
Shane 5:07 am on November 16, 2009 Permalink |
oh yeah. Time to really kill some bugs.