Codex Audit & Docs Sprint

@jhoffm34 and I have been reviewing the content in the Codex. I exported all of the pages from Google Analytics and then we’ve sorted them into groups of similar content types to see what emerges. You can view the spreadsheet here: https://docs.google.com/spreadsheet/ccc?key=0AnxB9WffF3jOdEFWYWozTGtvNlQ5WGFTQTAxTG55R0E&usp=sharing

The content we analysed broke down broadly into these different areas:

User

  • Installing WordPress
  • Getting Started
  • Glossary
  • Blogging
  • Site Builder
  • Troubleshooting
  • MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network.
  • Administration (inc Security?)
  • Getting Help

There are also about 60 reference pages for the various Panels/Screens. e.g. https://codex.wordpress.org/Administration_Panels

Developer

  • Setting up a Development Environment
  • How WordPress Works
  • Troubleshooting
  • Code Reference
  • PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Developer
  • Theme Developer
  • Server
  • Multisite
  • Administration

I am keen to have a strict division between the user-focused material and the developer-focused material. Of course, there are times when a developer will be a user (when they are managing their website) and there are times when a user will be a developer (when they tweak their theme) but linking between resources is more effective than putting the user and developer material together.

I’m reluctant to make major plans for restructuring and changing everything around before we close the Codex survey and analyse the results (some of which are surprising i.e. not everyone hates the Codex), however, I would like to come up with some concrete tasks for the Docs Sprint in a few weeks.

Therefore, I suggest that the team at the docs sprint tackle the following handbooks that can be built on learn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/:

  • Site Builder Handbook
  • Blogging Handbook
  • Editor Handbook
  • Theme Developer Handbook

Thoughts? Complaints? Suggestions?

#codex, #sprint

FYI The Codex & Doc survey is live…

FYI: The Codex & Doc survey is live: http://wordpressdotorg.polldaddy.com/s/documentation-survey

#codex

3.6 Master Codex changes list (in progress)

Since we’re revving up for the 3.6 release and a Codex Sprint, this post will serve as our “master changes list” for 3.6. This list is by no means complete, so leave a comment if you feel like something is missing. We’ll update it as we go. If you’ve completed a todo item, let us know and we’ll check it off for you.

Pages

  • Revision Management [ current ][ new draft ] Ref: #23497 (mostly technical)
  • Menus Administration Screen [ current ] Ref: #23607 (Tracking ticket)
  • Menus User Guide [ current ] Ref: #23607 (Tracking ticket)
  • Post Locking [ current ] Ref: This is more of a UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. change. Users now have to consciously override the post lock, vs before you could just open something if somebody was editing it.
  • Function Reference update the Function Reference with new functions.

General

Version 3.6

Twenty Thirteen

oEmbeds

Media

Function Changes

  • Strip slashes from passwords sent to new users by email
  • Make sure the url returned by post_preview() is filterable with preview_post_link
  • An arg parameter was added for wp_nonce_url()
  • Allow paths with two consecutive dots to be passed to home_url() and all related *_url() functions
  • Document 7th parameter, $callback_args in add_meta_box()
  • Confirm a user exists before deleting them in wp_delete_user() and wpmu_delete_user()
  • Return WP_Error from wp_crop_image() if saving has failed
  • Bail early with correct WP_Error if invalid post ID passed to wp_insert_post()

MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network.

  • Pass blog_id to the wpmu_drop_tables filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.

Class Changes

  • XML-RPC: Return an error for getRecentPosts (mw and blogger) if the user does not have edit_posts cap
  • XML-RPC: Standardize home/site url labels with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. labels

‘needs-codex’ TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets

>> Look for the Trac comment where needs-codex was added for more info

  • #11446 – Show ellipsis after truncated filename in Media dialog
  • #13578 – wp_link_pages isn’t fully functional and doesn’t include require style information
  • #15081 – Search Form should use type=’search’
  • #15155 – Allow filtering of shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. attributes
  • #16738 – Add filter for attributes on menu item links
  • #17515 – Flaw in add_meta_box/do_meta_boxes
  • #19067 – Duplicate functionality in core: size_format() and wp_convert_bytes_to_hr()
  • #19210 – Add missing filters to remaining link(url) functions in feed.php
  • #19321 – get_search_form() function calls an action and a filter with the same hook.
  • #20564 – Framework for storing revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. of Post MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • #22187 – Add docblocks to wp-signup.php
  • #22885 – Correct the PhpDoc for the_post_thumbnail
  • #22905 – PhpDoc refresh for register_sidebar()
  • #22913 – “Files “”corrupted”” when streamed to file via HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
  • #23058 – Corrected inline docs for cache.php
  • #23119 – UX Improvements to nav-menus.php
  • #23121 – Correct inline doc return value for WP_Filesystem_Base::gethchmod
  • #23313 – inline doc additions in wp-includes/formatting.php
  • #23325 – wp_crop_image does not return WP_Error when save fails
  • #23508 – Nav Menu Saving: get_nav_menu_locations() can return false, code expects array
  • #23641 – Tweaks to menu management box
  • #23770 – Restore ‘Locations’ meta box functionality as secondary tab in Menus UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.
  • #23791 – Missing param in wp_get_attachment_image() docs
  • #24203 – Remove the_title_attribute() from anchors with the_title() as text
  • #24265 – Clean up revision.php docblocks
  • #24314 – Documentation Improvement wp_dashboard_quota
  • #24343 – Correct inline docs for hook parameters in wp_delete_term()

New Functions

Audio / Video

Media

Revisions

General

New Filters

Deprecated Functions

External Libraries

  • Update to jQuery Color 2.2.1
  • Update to Backbone 1.0.0
  • Update to jQuery UI 1.10.3
  • Services_JSON 1.0.3
  • Iris 1.0.3
  • hoverIntent r7
  • MediaElement.js 2.11.1 (New)

#codex, #release, #sprint

Adopt a Codex Page

Want a high impact, low friction way to help out with the WordPress documentation project? Adopt a Page in the Codex!

The Documentation project is rumbling along, with handbooks and code reference underway. But in the meantime, we need to keep the Codex updated. Below is a list of the top 20 most visited narrative pages in the Codex. This does not include the reference pages, which I’ve excluded since we’re addressing that problem in a different way.

I’m looking for volunteers to take responsibility for one page of the Codex to be their very own. If you want to be involved with docs, but don’t have time to get really involved with the overall project, this is a great way to help out in a big way. The total uniques for these pages in one month is 1,615,139! If we can make these pages beautiful that’ll have a big impact on Codex users.

The pages are:

PageViews Uniques Responsible
Installing WordPress 307562 229754 Amanda
Editing wp_config.php 156380 127632 Rami Yushuvaev
First Steps with WordPress 132409 101865 Rami/Eric
Theme Development 129424 105878 Michael Chacon
Pages 123979 99941 Ben Hubbard & hearvox
Using Permalinks 120125 98980
Child Themes 108800 81198 Morgan Kay & Ulrich
Moving WordPress 102524 81198
Giving WordPress its Own Directory 91232 75590 vancoder
New to WordPress? Where to Start 84243 62195 Rami/Eric
Changing File Permissions 81044 67013
Create a Network 73205 53033
Changing the Site URL 73108 60315
WordPress Backups 71830 56385 Barry Von Someron & mrmist
Getting Started with WordPress 69926 55027 Rami/Eric
Using Themes 68308 58195
Roles and Capabilities 67441 53928 Drew Jaynes
The Loop 59236 49386 Jason Hoffman
Introduction to Blogging 58153 51628 Ronnie Burt
Conditional Tags 57223 45998 Carrie
Hardening WordPress Dre Armeda
2036152 1615139

If you’d like to adopt and maintain a Codex page, please leave a comment here, stating which one you’d like.

What’s Expected

Here’s what you’ll need to do:

1. Do a complete review of your page and carry out any updates that are necessary. Also, think about what can be removed. On long pages like the Installing WordPress page, we could run some analytics to see what people are clicking on. I’ll give you whatever support that I can.
2. Making sure all the links are cool, not spammy, and link to something that’s a) up-to-date, and b) GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples.-compliant
2. Review your page whenever WordPress is updated to make sure it’s up-to-date
3. Keep an eye on the History and the Discussion pages for your page to stay aware of any changes or issues.

It’s quite possible that these pages will end up in a handbook or elsewhere, but until that time they could do with some ongoing oversight and <3

Getting Started with WordPress

Yes, yes, I realise we have 3 pages that are pretty similar:

  • First Steps with WordPress
  • New to WordPress? Where to Start
  • Getting Started with WordPress

Someone could review all three of these pages, see if they’re all necessary, merge the content and create one Getting Started with WordPress page, we can redirect the other two pages there.

Otherwise, please only adopt one page.

#codex

Codex Gardening: query_posts

It was pointed out by @pixolin at the docs chat yesterday that query_posts is recommended in various places throughout the WordPress CodexWordPress Codex Living online manual to WordPress.org https://codex.wordpress.org/. Where possible, query_posts shouldn’t be recommended. Lots of developers who are learning about WordPress use the Codex as their bible, and we should always be recommending best practices.

What’s Required?

We need someone to review the instances of query_posts in the Codex. If query_posts can be replaced with another example, then it should be. If query_posts can’t be replaced then there should be a good reason for it.

Simple job: anyone want to take it on? You’ll be doing a great service to our next generation of developers!

#codex

WordPress Codex Sprint Round-up

The first WordPress codexWordPress Codex Living online manual to WordPress.org https://codex.wordpress.org/ sprint was a success! A bunch of us got together in the #wordpress-sfd chatroom and ploughed through the majority of the docs. You can see how successful we were by checking out our to-do list.

There are a few things left on the list so if anyone could tackle them and let me know so I can tick them off that’d be great. The final bits and pieces are developer docs.

Some things that we learned:

  • documentation sprints are a great way to get through a lot of documentation at once.
  • it is important to have some developers involved who can deal with the ultra-developer stuff and field questions

Anyone learned anything else? Add it to the comments so I can add it to the list.

Thanks to the following people for working hard to get the docs updated: Jerry Bates (@jerrysarcastic), Jonathan Wold (@sirjonathan), Philip Erb (@philerb), Curtis McHale (@curtismchale), Mika Epstein (@ipstenu), Jason Hoffman (@jhoffm34), and Marko Heijnen (@markoheijnen)

Special thanks to Drew Jaynes (@drewapicture) who hasn’t just been a rockstar, he’s been a superstar. Thanks Drew!

Future Sprints

I’d love to see more documentation sprints in the future. As well as having them virtually, they could be organised at WordCamps to coincide with developer activity. Some ideas for future sprints:

  • updating the function reference and making sure that everything has examples
  • cleaning out old content
  • updating out-of-date pages
  • re-working the FAQs
  • making a dent in the handbooks
  • working through the Help Tabs

If anyone else has any suggestions for future documentation sprints, and how often they think they should be, do leave a comment!

#codex, #sprint

As WP won’t be arriving today the Codex…

As WP won’t be arriving today, the Codex will sprint postponed until next week! It will now take place:

Start: Thursday 13th December – 3pm UTC
End: Friday 14th December – 5pm UTC

#codex

WordPress 3.5 mid-week Codex Sprint

This release cycle we’re lucky enough to know the date of the next release – 5th December! All of the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devs will be relaxing with beer, or sleeping, or recuperating in a rest home, and it will be time for us to pick up the slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. and get the docs updated.

We had a discussion in chat and agreed that it would be a great idea to get together to plough through as many of the codex updates as possible. With inspiration from Mozilla’s Doc sprints, here’s how it’s going to work:

Schedule

Start: Thursday 13th December – 3pm UTC
End: Friday 14th December – 5pm UTC

You can get involved at any point. Obviously I’m not planning to be there for 26 hours :), but I will be around as much as possible.

How?

Myself and @DrewAPicture are compiling a WordPress 3.5 Codex Updates List. I’ve already begun the list, but we will have this ready by the time we get started on Thursday 6th.

Come to the IRC chat on freenode – #wordpress-sfd or leave a message in the Codex Updates thread to say what you’d like to do. Myself or someone else will assign it to you. If you see someone already assigned then you know that is being taken care of (i.e. @JerrySarcastic is working his magic on the Media pages).

When it’s complete, let myself or another editor (like @DrewAPicture) know, and we’ll tick it off and note that you’ve done it.

Where?

The WordPress Support and Docs chatroom on IRC freenode. #wordpress-sfd

If you don’t have an IRC client, or ar unfamiliar with IRC, you can join the chat over the web here: http://webchat.freenode.net/?channels=wordpress-sfd (thanks @mrmist )

You don’t have to come to the chatroom. I’ll be monitoring the Codex Updates master list so just leave a message there if you want something assigned to you.

Why?

It sucks to be a user and to get confused because the docs are outdated. Let’s try to avoid that happening.

Because @nacin missed a Bob Dylan concert: https://twitter.com/nacin/status/271003759642034177

Also, because the Codex is important, and helping to update it is a great way to be involved with WordPress.

Any questions? I’ll try to have answers. Also, any suggestions on improvements to workflow or any other suggestions are always appreciated. This is the first time we’ll have done it in this way and if it works it’d be fantastic to do it for each WordPress release.

#3-5, #codex

WordPress 3.5 Codex Updates

If all goes to plan, WordPress 3.5 will be with us in a just over a weeks. This means that the Codex is going to need to be updated in line with the new features. To help keep track of what needs to be updated, I thought it would be a good idea to create a list. I’d love some help creating the list of items that need to be reviewed and/or updated. Just note the item in the comments, with or without a link to the relevant codex page.

Sprint happening on 13th December: see here: https://make.wordpress.org/docs/2012/11/30/this-release-cycle-were-lucky-enough-to-know/

For additional reference, you can check out the 3.5 Beta 1 features workup in Google Docs.

Alright, here goes:

#Version 3.5@DrewAPicture

  • Version 3.5 page https://codex.wordpress.org/Version_3.5 (@DrewAPicture)
  • 3.5 Changelog https://codex.wordpress.org/Changelog/3.5 (@DrewAPicture)

#Media:@JerrySarcastic

  • Media Add New Screen https://codex.wordpress.org/Media_Add_New_Screen (@JerrySarcastic)
  • Edit Media Screen (new page for 3.5 workflow) https://codex.wordpress.org/Edit_Media (@JerrySarcastic)
  • Inserting Images into Posts and Pages https://codex.wordpress.org/Inserting_Images_into_Posts_and_Pages (@JerrySarcastic)
  • Media Add New SubPanel https://codex.wordpress.org/Media_Add_New_SubPanel (Deleted this duplicate page) (@JerrySarcastic)

#Gallery – @JerrySarcastic

  • The WordPress Gallery https://codex.wordpress.org/The_WordPress_Gallery (@JerrySarcastic)
  • Gallery Shortcode https://codex.wordpress.org/Gallery_Shortcode Gallery should reflect the new system based on (@JerrySarcastic)

with menu_order deprecated.

#Links: @jhoffm34

  • Links Manager https://codex.wordpress.org/Links_Manager (@jhoffm34)
  • Links Link Categories Screen https://codex.wordpress.org/Links_Link_Categories_Screen (@jhoffm34)

#Twenty Twelve: @raggedrobins

  • Using Themes https://codex.wordpress.org/Using_Themes (@raggedrobins)
  • Add to glossary https://codex.wordpress.org/Glossary (@raggedrobins)
  • Child Themes page uses Twenty Eleven as Example: https://codex.wordpress.org/Child_Themes (@raggedrobins)
  • Update reference to default theme: https://codex.wordpress.org/Common_WordPress_Errors (@raggedrobins)
  • Updating WordPress: https://codex.wordpress.org/Updating_WordPress (this page needs totally rewritten – suggest having another sprint for updating out of date pages) (@raggedrobins)
  • Multisite Network Admin: https://codex.wordpress.org/Multisite_Network_Administration (@raggedrobins)
  • First Steps with WordPress: https://codex.wordpress.org/First_Steps_With_WordPress (@raggedrobins)
  • Appearance Menu Screen: https://codex.wordpress.org/Appearance_Menus_Screen (@raggedrobins)
  • Appearance Header Screen: https://codex.wordpress.org/Appearance_Header_Screen (@raggedrobins)
  • Login Trouble: https://codex.wordpress.org/Login_Trouble (@raggedrobins)

#HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. Editor renamed as Text:

  • Writing Posts https://codex.wordpress.org/Writing_Posts (@raggedrobins)
  • TinyMCE https://codex.wordpress.org/TinyMCE (@raggedrobins)
  • TinyMCE Custom Styles https://codex.wordpress.org/TinyMCE_Custom_Styles (@raggedrobins)

#oEmbeds:
Slideshare, Instagram & SoundCloud integration (also turned on by default)

  • Embeds: https://codex.wordpress.org/Embeds (@DrewAPicture)
  • This post on wpbeginner: http://www.wpbeginner.com/wp-themes/how-to-set-oembed-max-width-in-wordpress-3-5-with-content_width/ This could be added to one of the troubleshooting FAQs – “How do I resize my oembeds?” (@DrewAPicture)

#PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party Favorites: – Philip Erb

  • Managing Plugins: https://codex.wordpress.org/Managing_Plugins (@philerb)
  • Plugins add new subpanel https://codex.wordpress.org/Plugins_Add_New_SubPanel (@philerb)

#Search Engine Visibility@DrewAPicture
(moved from Settings > Privacy -> Settings > Reading )

  • Settings Privacy Screen https://codex.wordpress.org/Settings_Privacy_Screen (@DrewAPicture)
  • Settings Reading https://codex.wordpress.org/Settings_Reading_Screen (also charset option hidden) (@DrewAPicture)
  • Administration Screens https://codex.wordpress.org/Administration_Screens Cleanup Privacy entries (@DrewAPicture)

#Media Settings

  • Uploads folder hidden: https://core.trac.wordpress.org/ticket/21720 (@raggedrobins)
  • Settings Media Screen: https://codex.wordpress.org/Settings_Media_Screen (@DrewAPicture)
  • oEmbed now enabled by default https://codex.wordpress.org/Settings_Media_Screen (@raggedrobins)

#XML-RPC:
(now enabled by default)

  • XML-RPC Support: https://codex.wordpress.org/XML-RPC_Support (@raggedrobins)

#AtomPub

  • turned off by default: https://codex.wordpress.org/AtomPub Can re-enable with a plugin: https://wordpress.org/extend/plugins/atom-publishing-protocol/ (@raggedrobins)

#MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network.

  • Multisite installs now work with WordPress in a subdirectory (@Ipstenu)
  • Rockstar: Turn off ms-files.php by default (@Ipstenu)
  • File quotas disabled by default on new installs

#Miscellaneous:

  • Widgets menu hidden if no sidebar is active (maybe add an FAQ to the troubleshooting guide?) https://codex.wordpress.org/WordPress_Widgets (@raggedrobins)
  • Display name defaults to first name and last name for new users https://codex.wordpress.org/Users_Screen also: https://codex.wordpress.org/Users_Your_Profile_Screen#Your_Profile_and_Personal_Options (@raggedrobins)
  • Force the user to explicitly choose between content deletion and reassignment when deleting users https://codex.wordpress.org/Users_Screen#Delete_Users (@raggedrobins)
  • changes to custom headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. screen (@raggedrobins)
  • Easier Expression of Time constants (new!) https://codex.wordpress.org/Transients_API#Using_Time_Constants (@DrewAPicture)

Developer

General Developer

  • Bump default memory limit from 32MB to 40MB (@raggedrobins)
  • Add easier expression of time constants, for example DAY_IN_SECONDS vs 86400 (@DrewAPicture)
  • Add flexible-header to allowed theme tags
  • Add ‘publish_post’ metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. capability (@DrewAPicture)
  • No Class Reference: Add ‘term_taxonomy_id’ field handling to WP_Tax_Query::transform_query(), resulting in fewer database queries
  • Add two hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to Post Editing screen, ‘edit_form_after_title’ and ‘edit_form_after_editor’ [more info] (@DrewAPicture)
  • Rockstar: Allow ordering posts by IDs passed to ‘post__in’
  • Check a post type’s ‘show_in_admin_bar’ property for ‘View’ and ‘Edit’ object Toolbar links

#Multisite

  • Multisite: Allow home page of sub-directory sites to resolve regardless of capitalization (@DrewAPicture)
  • Multisite: Introduce get_space_used() and upload_is_user_over_quota() for more gauging more accurate quotas (@Curtismchale)
  • Multisite: Make it easy to replace or augment the over-quota message

#Classes

  • Rockstar: WP_Image_Editor needs starter info https://codex.wordpress.org/Class_Reference/WP_Image_Editor
  • Fix tax query returning all results when empty (@DrewAPicture)
  • Rockstar: Add get() and set() methods to WP_User_Query for modifying query variables the way you might with WP_Query

#New Functions:

#Functions – Needs Example

#Deprecated Functions & Filters:

  • user_pass_ok() https://codex.wordpress.org/Function_Reference/user_pass_ok (@raggedrobins)
  • wp_get_single_post() https://codex.wordpress.org/Function_Reference/wp_get_single_post (@raggedrobins)
  • Deprecate image_resize() https://codex.wordpress.org/Function_Reference/image_resize (@raggedrobins)
  • Deprecate image_resize filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. (@sirjonathan)
  • wp_cache_reset() (@DrewAPicture)
  • Deprecate sticky_class() in favor of post_class() https://codex.wordpress.org/Function_Reference/sticky_class (@raggedrobins)
  • Deprecate wp_create_thumbnail() (@DrewAPicture)
  • Deprecate wp_create_thumbnail filter (@sirjonathan)
  • Deprecate image_save_pre filter, which filters a GD Resource, for image_editor_save_pre, which filters a WP_Image_Editor object (@sirjonathan)
  • Deprecate wp_save_image_file filter, which filters a GD Resource, for wp_save_image_editor_file, which filters a WP_Image_Editor object (@sirjonathan)
  • Deprecate image_edit_before_change filter, which filters a GD Resource, for image_edit_before_change, which filters a WP_Image_Editor object (@DrewAPicture)
  • Deprecate jpeg_quality filter for wp_editor_set_quality, or WP_Image_Editor::set_quality() on an individual image, which sets compression quality for any supported format (@sirjonathan)
  • Deprecate wp_load_image() in favor of wp_get_image_editor() https://codex.wordpress.org/Function_Reference/wp_load_image (@raggedrobins)
  • Deprecate image_resize in favor of WP_Image_Editor::resize() (@raggedrobins)
  • Deprecate gd_edit_image_support() in favor of wp_image_editor_supports() (@raggedrobins)

#Function Changes:

  • register_taxonomy page needs to be updated with the new ‘show_admin_column’ parameter that allows automatic creation of taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. columns on associated post-types. (@Ramly)
  • Add ‘order’ parameter to wp_get_archives() https://codex.wordpress.org/Function_Reference/wp_get_archives (@DrewAPicture)
  • Allow count_many_users_posts() to count only public posts (@jhoffm34)
  • Add ‘order’ to wp_get_archives() (@DrewAPicture)
  • Allow passing stdClass and WP_User to wp_insert_user() and wp_update_user() (@DrewAPicture)
  • Fix the matching in is_email_address_unsafe(), which was too aggressive (@DrewAPicture)
  • Give System temporary directories preference in get_temp_dir() for better Windows compatibility (@DrewAPicture)
  • Hide UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. for attachment taxonomies if ‘show_ui’ is ‘false’ for that taxonomy (@DrewAPicture)
  • Make get_home_path() work in more cases by being case insensitive and sanitzing Windows paths (@DrewAPicture)
  • No markup is output if wp_nav_menu() has no menu items (@DrewAPicture)
  • Return WP_Error object if the database insert in wp_set_object_terms() fails (@DrewAPicture)
  • Simplify protocol stripping in add_query_arg() by avoiding a regular expression (@DrewAPicture)
  • supports => false can be passed to register_post_type() to disable default title and editor (@DrewAPicture)
  • Welcome Panel and accompanying screen option removable via the welcome_panel hook (@DrewAPicture)
  • When reassigning posts and links during user deletion, clear the post and link caches
  • Rockstar: XML-RPC: Add the ‘home’ option to wp.getOptons https://codex.wordpress.org/XML-RPC_WordPress_API/Options
  • Rockstar: XML-RPC: Don’t use switch_to_blog() in wp.getUsersBlogs, improves performance and memory footprint https://codex.wordpress.org/XML-RPC_wp

#New Filters

  • Add cron_request for filtering the cron_url passed to wp_remote_post() in spawn_cron() (@DrewAPicture)
  • Add login_body_class filter to login_header() (@DrewAPicture)
  • Add media_view_strings and media_view_settings filters. Use media_view_strings to filter ‘Insert into post’ button text
  • Add post_type_labels_{$post_type} to filter get_post_type_labels()
  • Add restrict_manage_comments hook to comments list table for better filtering capability
  • Add validate_password_reset filter, making it possible for plugins to enforce password rules
  • Add domain_exists filter for domain_exists()
  • Add wp_get_update_data filter making it easier for plugins to modify update count
  • Rockstar: Add wp_image_editors filter to allow adding to or modifying order of WP_Image_Editor engines
  • XML-RPC: Add xmlrpc_login_error filter to customize the IXR_Error returned when login() fails

#Scripts, External Libraries

  • Add jQuery Masonry for better custom header listings (@raggedrobins)
  • Farbtastic color picker replaced with Iris color picker [more info] (@raggedrobins)
  • Switch to .min for compressed JS and CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. files, e.g. .js becomes .min.js, .dev.js becomes .js (@DrewAPicture)
  • Allow protocol-relative URLs when registering/enqueueing scripts and styles (@georgestephanis)
  • Prototype and Script.aculo.us local libraries unbundled from core, latest versions enqueued via ajax.googleapis.com (@raggedrobins)

Please, add more!

#codex