WordPress Beta 1 for version 3.6 is ready for testing

WordPress Beta 1 of version 3.6

WordPress Beta 1 of version 3.6

WordPress Beta 1 for version 3.6 is available for download and testing – that was declared at WordPress official blog at April 4, 2013. Product is still under development and it’s not recommended to setup it on a production site. Inspite of this, independently who are you, WordPress plugin or theme developer, or a WordPress hosting provider, you are encouraged to put new coming WordPress version into testing environment, test it thoroughly against your products and environment and try to find bugs or themes, plugins incompatibility issues and problems. Do you wait something new, something interesting from the latest WordPress version? Download Beta version here.

What’s new in WordPress Beta 1 of version 3.6?

Brief list:

  • Post Formats: Post Formats now have their own UI, and theme authors have access to templating functions to access the structured data.
  • Audio/Video: You can embed audio and video files into your posts without relying on a plugin or a third party media hosting service.
  • Autosave: Posts are now autosaved locally. If your browser crashes, your computer dies, or the server goes offline as you’re saving, you won’t lose the your post.
  • Post Locking: See when someone is currently editing a post, and kick them out of it if they fall asleep at the keyboard.
  • Nav Menus: Nav menus have been simplified with an accordion-based UI, and a separate tab for bulk-assigning menus to locations.
  • Revisions: The all-new revisions UI features avatars, a slider that “scrubs” through history, and two-slider range comparisons.
  • Twenty Thirteen: We’re shipping this year’s default theme in our first release of the year. Twenty Thirteen is an opinionated, color-rich, blog-centric theme that makes full use of the new Post Formats support.
    Twenty Thirteen WordPress theme

    Twenty Thirteen WordPress theme

For this moment I discovered the only problem at my “Thank You Counter Button” plugin, which button imager mouseover javascript event is overridden by CSS hover from Twenty Thirteen theme. That needs some work to fix problem – I should not use “button” HTML element in plugin output. It’s changing to read square button when you put mouse pointer on it under new 2013 theme. Other 6 my plugins work well with WordPress Beta 1 of version 3.6.

Thus, I went to conclusion that WordPress developers team made a good job producing updated product with so high level off backward compatibility. What do you think?