Things a developer should know about WordPress 3.5

I have already written about the changes you will see in WordPress 3.5. But there are certain important changes which you should know about especially if you are a developer.

  1. XMLRPC will be turned on by default from now on and the setting to turn it off has been removed from the settings page. This is because according to the Dev team, XMLRPC is pretty secure and also has been improved a lot so there is no reason you should have to turn it off. But if for some reason you want to turn it off, you will need to use the following code.
    add_filter( 'xmlrpc_enabled', '__return_false' );

    For more on this, I recommend you to read WPEngineer’s post.

  2. WordPress’s default memory consumption limit has been bumped to 40MB.
  3. Its possible to add a rel=”me” tag in your author descriptions now.
  4. Now its easier to display taxonomy columns on edit post pages. Just add show_admin_column => true for register_taxonomy() parameter to your register_taxonomy() code which will automatically display the taxonomy list on corresponding post types. And if you are looking to add it on your own, you can use manage_taxonomies_for_{$post_type}_columns filter. More Information here.
  5. You can order images explicitly in your galleries by using id parameter to list the images in the order you want them to display.
  6. You can specify a custom order when you include posts by id now. Order will be the same in which you will include the ids using post__in parameter.
  7. Upload Directory settings have been removed from the Media Settings page. From now on, to change the default WordPress wp-content directory, you should use the UPLOADS constant or applying a filter to wp_upload_dir().
  8. From now on, View Post link on Edit post page will open in the same tab/window while only the Preview Post will open it in the new tab/window.
  9. You can now display post archives in Ascending or Descending order by using order = ASC or order = DESC arguments to the function wp_get_archives();
  10. You can now remove an existing oEmbed Provider using wp_oembed_remove_provider() function.
  11. You can add custom arguments for an oEmbed request by using the filter ‘oembed_fetch_url‘.
  12. AutoDiscovery for Custom Post Type feeds has been enabled. This means you won’t have to add the feed links for custom post types in the head tag manually.
  13. Earlier when you had multiple categories per post and your permalink contains category name then the category with the lowest id appears in the permalink for that post’s url. Now you can specify the category to be chosen in such cases using ‘post_link_category’ filter.
  14. Imagemagick Support is coming finally in the core. Images will be processed using the Imagemagick library by default but if its not installed, then the editing functions will fallback to the GD Library. You can read post about editing functions at WordPress development blog.
  15. Similar to get_edit_post_link(), WordPress 3.5 introduces a new function get_edit_user_link(). This function will redirect to the current author’s profile page.
  16. Plugins can now add extra password validity/strength rules to be enforced during password reset process.
  17. sticky_class() function has been deprecated in favor of post_class() function.
  18. Canonical links for paged comments have been fixed finally. They now point to the corresponding comment page instead of the post.
  19. Unused arguments like hierarchical, _edit_link and capability_type have been removed from register_post_status() function.
  20. Incorrect search page links in Adminbar of multisite installs has been fixed.
  21. WordPress 3.5 ships with the latest versions of libraries which includes jQuery 1.8.3, jQuery UI 1.9.2, SimplePie 1.3.1 and TinyMCE 3.5.8. Also now you can use Protocol relative links in your themes to enqueue external scripts. For usage on how to do it, see this patch file which shows how to do it in 3.5 and above while maintaining backward compatibility with older WP versions as well.
  22. Since now the settings to change the default dimensions of oEmbeds has been removed, your content should have a max width set so that your Embeds can use that width. You can use the following code to do so
    if ( ! isset( $content_width ) ) $content_width = 600;

    Source: WPBeginner

Read WordPress’s 3.5 Beta release post for the rest of the changes and keep a check on WordPress Developer Blog for more resources.