Twenty Thirteen project update, March 19, 2013
We’re in great shape to get to beta. Here is what we’re working on right now.
Blocking older installs
Tracked in #23819 — since Twenty Thirteen is 3.6+ only, older installs could see errors. We’d like to come up with a graceful way to not allow older versions of WordPress to install and run Twenty Thirteen.
Maybe a nag function in the theme that puts up a warning? Forcing a change the previously activated theme upon activation? What are your thoughts?
Relates to #13780 also.
Post formats integration
See #23619, #23620, and #23621 — we are waiting on the core functionality to be committed before we can change the theme code (images, videos, galleries, links).
Recently completed
- HTML5 improvements to comment list, comment form, and search form (yay!) #22005, #23702, and #23701
- Solidify footer positioning when no JavaScript or no Masonry script available: #23771
- More gallery visual fixes: #23773 and #23769
Open issues
Here is a link to open tickets.
Rami Yushuvaev 8:22 pm on March 19, 2013 Permalink
Great work lance.
But regarding to search forms, seems like you didn’t addressed the old discussions on tickets #14581, #19321, and #19579.
Rami Yushuvaev 3:09 pm on March 20, 2013 Permalink
#14581 => #14851
Lance Willett 5:06 pm on March 21, 2013 Permalink
Thanks for pointing those out, I hadn’t seen them before.
chp2009 10:49 pm on March 19, 2013 Permalink
I think putting up a nag function that can only be seen by a user with admin permissions is a great idea. As a matter of fact only a user with admin permissions should be able to see errors related to the administration of the website. It creates a better user experience.
chacha102 5:04 am on March 23, 2013 Permalink
Plugins can deactivated themselves if they know their requirements aren’t met. There needs to be a precedent set for how theme’s who requirements haven’t been met can ‘deactivate’ themselves.
I think that the result of a theme ‘deactivating’ itself should cause the same result as if the theme suddenly was removed. I believe right now it defaults to the default theme in WordPress. I would argue doing anything different then that creates an inconsistent error scheme.
Myatu 11:19 am on March 23, 2013 Permalink
If there was a way to track which theme it switched from (active before trying to activate this theme), then one could simply revert the action. That would be the safest method, as it does not alter the website in any way (ie., theme specific customizations, etc).
Myatu 11:25 am on March 23, 2013 Permalink
Having that said… Why not include this sanity check within the WP core itself, for both plugins and themes. Just give add two extra meta headers to the plugins/themes for the minimum WP and PHP versions, and add a little extra code that checks against these prior to activation. That would be a useful feature that could benefit many. #thinkingoutloud
Lance Willett 7:31 pm on March 23, 2013 Permalink
See #13780 for the WordPress version requirement support.
Twenty Thirteen Not Backwards Compatible? - WP Daily 3:01 pm on March 25, 2013 Permalink
[...] March 19th a Twenty Thirteen update was posted to the make.wordpress blog, [...]