WordPress 3.9 Codex Updates

Welcome to the official home of the WordPress Documentation Team.

This team is responsible for coordinating all documentation initiatives around WordPress, including the handbooks and other general wordsmithing across the WordPress project.

Want to get involved?

Start here to find out more about what we do and how to contribute:

Onboarding to Documentation Team: An overview of what we do and how to collaborate
Documentation Issue Tracker on GitHub: Submit any Documentation Team-related issues on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/

Weekly meetings

Join our discussions of documentation issues here on the blog and on Slack.

The documentation team holds weekly office hours and monthly Contributor Days on each Tuesday of the month in the #docs 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/. channel. It’s also where you can contact the team at any time outside meetings.

Siobhan 5:26 am on April 16, 2014

I don’t think we need to add all of the new functions etc to the Codex since we’ll soon have the code reference. @drewapicture and @kpdesign – what do you think?
- Drew Jaynes (DrewAPicture) 5:31 am on April 16, 2014
  
  I’d say probably not. It wouldn’t be too hard to make basic pages for any/all of them though even if just reiterating the info in the doc blocks.
Graham Armfield 5:26 pm on April 22, 2014

One of my patches got accepted into 3.9 and so the function reference for paginate_links() needs updating. I’m happy to get involved with that but I’m not quite sure the appropriate workflow required.
- Kim Parsell 2:20 am on April 23, 2014
  
  @grahamarmfield: I’ve added that Codex page to the list in the Developer section under Miscellaneous. Feel free to make the appropriate changes to the Codex page, comment here when you’re done, and we’ll mark it as complete. We appreciate the help. 🙂
  - Graham Armfield 8:32 am on April 23, 2014
    
    Righto Kim, I’ll give it a go. I’ve not updated a codex page before, are there any special pointers?
    - Kim Parsell 10:42 pm on April 23, 2014
      
      @grahamarmfield: Use your 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/ account to log in to the Codex. Click Edit in the right column, and make the necessary edits to the page to add the documentation for the new arguments (code samples, parameters list, etc.).
      
      For help with wiki formatting, check the existing docs on that page. You can also check https://codex.wordpress.org/Help:Editing for help with any formatting not already there.
      
      When done, make sure to put the reason for the edit in the Summary box at the bottom of the page, then click Save Page.
      
      If you have any questions, either comment here or find one of us in #wordpress-sfd for help. 🙂
  - Graham Armfield 4:05 pm on April 24, 2014
    
    I’ve updated the codex page now. Thanks for your help Kim.
    - Kim Parsell 5:26 pm on April 24, 2014
      
      You are most welcome. Thanks for taking care of that. 🙂
SusanInHouston 7:31 pm on April 25, 2014

Hi … I am working on “Tiny MCE: Writing Posts https://codex.wordpress.org/Writing-Posts
designsimply 11:11 am on April 26, 2014

Updated https://codex.wordpress.org/Inserting_Media_into_Posts_and_Pages for images. Feedback/edits/removal/rewrite/? of the Changes in 3.9 section welcome.
- Kim Parsell 11:45 am on May 28, 2014
  
  @designsimply: It looks good – thank you. 🙂
designsimply 7:34 pm on April 26, 2014

Updated https://codex.wordpress.org/Edit_Media#Edit_Image

I couldn’t get the keyboard shortcuts described at https://codex.wordpress.org/Edit_Media#Keyboard_Shortcuts to work at all. Pushing the arrow keys with a crop area active moved it to the edges of the image container, and trying anything more advanced than just arrows like “Shift + arrow” crashed Firefox every single time I tried them (tested with Firefox 28.0 + Mac on a local WP 3.9 install). Shortcuts didn’t crash Safari 7.0.3, but they didn’t do what the Codex page described either. Can anyone else get the image crop keyboard shortcuts to work?
- Kim Parsell 11:29 am on May 28, 2014
  
  The issue you had with the keyboard shortcuts not working has been reported in #18184.
hearvox 4:38 pm on May 15, 2014

Hey all, this Codex entry is (I Think) wrong in saying: “Check that the very last characters are ?>”:
https://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

WP now ends most files w/o the closing php tag, and a very common reason for “Headers already sent” is a closing “>?” then one or more blank lines. Before I edit, wanted to check here first, but seems like the above phrase needs updating to something like:
“Check that the very last characters are either not a closing php tag (?>) or are ?> with no blank spaces or blank lines after it.”
- Kim Parsell 11:32 am on May 28, 2014
  
  @hearvox: Thanks for catching that – feel free to make the necessary edits to that page to correct it.
Daisuke Takahashi 3:29 pm on June 8, 2014

Why Japanese Codex(http://wpdocs.sourceforge.jp/) is separated from 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/?
To merge with WordPress.org may increase Japanese participation.

There is no reason to keep segregated.
- Naoko Takano 1:05 pm on June 9, 2014
  
  The reason is historical one, back in 2008 when we migrated some ja: namespaces pages from English Codex, there were some Japanese fond display issues on the English Codex. We can certainly take a look at the possibly of migrating back the current contents into codex.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/. It certainly won’t be simple to execute but of course that alone won’t be a good reason not to. Could you propose that to our translation team mailing list or Codex P2? Thanks.
  - Daisuke Takahashi 12:15 am on June 10, 2014
    
    @nao: I don’t have enough permissions to post to Codex P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.. Could you grant me it?
    - Naoko Takano 12:50 am on June 10, 2014
      
      Please see the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. of the P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. (which is linked to here – contact info section). Alternatively you can use the documentation forum.
- samuelsidler 5:17 pm on June 12, 2014
  
  In the future, when the Codex isn’t as important, docs will mostly be in devhub and a support hub. We’ll want teams to translate those docs there. Allowing translations of docs in various places on dotorg is on our long-term roadmap.
  
  For now, there’s no reason for the Japanese team to move things off of their separate codex. New docs (one’s being created now) should be translated side-by-side with current docs in the future. We don’t have a plan in place for that beyond “we want it.”

Want to get involved?

Weekly meetings

Share this: