Title: WordPress 3.9 Codex Updates
Author: Siobhan
Published: April 16, 2014
Last modified: May 28, 2014

---

 [  ](https://profiles.wordpress.org/siobhan/) [Siobhan](https://profiles.wordpress.org/siobhan/)
5:25 am _on_ April 16, 2014     
Tags: [Codex ( 19 )](https://make.wordpress.org/docs/tag/codex/)

# WordPress 3.9 Codex Updates

I’ve made a start on the Codex updates list. Feel free to add to it.

I don’t think we’ll have a huge number of updates this time around.

**User**

Widgets:

 *  WordPress Widgets: https://codex.wordpress.org/WordPress_Widgets

Uploading Images:

 *  Using Images: https://codex.wordpress.org/Using_Images (suggest a complete rewrite)

Media Editing:
 (now available in the modal window and with some other tweaks)

 *  Edit Media: https://codex.wordpress.org/Edit_Media
 *  Inserting Media into Posts and Pages: https://codex.wordpress.org/Inserting_Media_into_Posts_and_Pages(
   [@designsimply](https://profiles.wordpress.org/designsimply/))

Galleries:

 *  The WordPress Gallery: https://codex.wordpress.org/The_WordPress_Gallery

Audio and Video Playlists:

 *  Inserting Media into Posts and Pages: https://codex.wordpress.org/Inserting_Media_into_Posts_and_Pages

TinyMCE:

 *  Writing Posts: https://codex.wordpress.org/Writing_Posts

New page needed:

 *  WordPress Theme CustomizerCustomizer Tool built into WordPress core that hooks
   into most modern themes. You can use it to preview and modify many of your site’s
   appearance settings. (user-facing)

**Developer**

TinyMCE:

 *  TinyMCE https://codex.wordpress.org/TinyMCE

Theme Customizer:

 *  Theme Customization API: https://codex.wordpress.org/Theme_Customization_API
 *  Add basic page for new [WP_Customize_Widgets](https://codex.wordpress.org/Class_Reference/WP_Customize_Widgets#Methods_and_Properties)
   class ([@DrewAPicture](https://profiles.wordpress.org/DrewAPicture/))

Miscellaneous:

 *  New arguments added to `paginate_links()` in [r27600](https://core.trac.wordpress.org/changeset/27600)(
   [#24709](https://core.trac.wordpress.org/ticket/24709)): https://codex.wordpress.
   org/Function_Reference/paginate_links ([@grahamarmfield](https://profiles.wordpress.org/grahamarmfield/))

Deprecated Stuff:

 *  [get_current_site_name()](https://codex.wordpress.org/Function_Reference/get_current_site_name)(
   [@DrewAPicture](https://profiles.wordpress.org/DrewAPicture/))
 *  [format_to_post()](https://codex.wordpress.org/Function_Reference/format_to_post)(
   [@DrewAPicture](https://profiles.wordpress.org/DrewAPicture/))
 *  [wpmu_current_site()](https://codex.wordpress.org/Function_Reference/wpmu_current_site)(
   [@DrewAPicture](https://profiles.wordpress.org/DrewAPicture/))

[#codex](https://make.wordpress.org/docs/tag/codex/)

### Share this:

 * [  Threads ](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?share=bluesky)
 * [  X ](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?share=x)
 * [  Facebook ](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2014%2F04%2F16%2Fwordpress-3-9-codex-updates%2F%23respond&locale=en_US)

 1.  ![](https://secure.gravatar.com/avatar/78e12b0e0fd945bd7d661af2b0ca95c1509d09a7a1f528ded21bbd604192c662?
     s=32&d=mm&r=g)
 2.   [Siobhan](https://profiles.wordpress.org/siobhan/)  5:26 am _on_ April 16, 2014
 3.  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](https://profiles.wordpress.org/drewapicture/)
     and [@kpdesign](https://profiles.wordpress.org/kpdesign/) – what do you think?
 4.   * ![](https://secure.gravatar.com/avatar/19347ef87f4fd5978b2184e7f05af5c780485f69dbfdefccfe3521c732a87f06?
        s=32&d=mm&r=g)
      *  [Drew Jaynes (DrewAPicture)](https://profiles.wordpress.org/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.
 5.  ![](https://secure.gravatar.com/avatar/4f684f4cc972282de186d82860316d741081e106110096762e4b2588b3d5920a?
     s=32&d=mm&r=g)
 6.   [Graham Armfield](https://profiles.wordpress.org/grahamarmfield/)  5:26 pm _on_
     April 22, 2014
 7.  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.
 8.   * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385?
        s=32&d=mm&r=g)
      *  [Kim Parsell](https://profiles.wordpress.org/kpdesign/)  2:20 am _on_ April
        23, 2014
      * [@grahamarmfield](https://profiles.wordpress.org/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. 🙂
         - ![](https://secure.gravatar.com/avatar/4f684f4cc972282de186d82860316d741081e106110096762e4b2588b3d5920a?
           s=32&d=mm&r=g)
         -  [Graham Armfield](https://profiles.wordpress.org/grahamarmfield/)  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?
            * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385?
              s=32&d=mm&r=g)
            *  [Kim Parsell](https://profiles.wordpress.org/kpdesign/)  10:42 pm _on_
              April 23, 2014
            * [@grahamarmfield](https://profiles.wordpress.org/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/](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](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](https://make.wordpress.org/docs/tag/wordpress-sfd/)
              for help. 🙂
         - ![](https://secure.gravatar.com/avatar/4f684f4cc972282de186d82860316d741081e106110096762e4b2588b3d5920a?
           s=32&d=mm&r=g)
         -  [Graham Armfield](https://profiles.wordpress.org/grahamarmfield/)  4:05
           pm _on_ April 24, 2014
         - I’ve updated the codex page now. Thanks for your help Kim.
            * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385?
              s=32&d=mm&r=g)
            *  [Kim Parsell](https://profiles.wordpress.org/kpdesign/)  5:26 pm _on_
              April 24, 2014
            * You are most welcome. Thanks for taking care of that. 🙂
 9.  ![](https://secure.gravatar.com/avatar/d031ab933482a7ea7fcd0747a57e6179251e9644ccb96d7d568d81a3203b0e4e?
     s=32&d=mm&r=g)
 10.  [SusanInHouston](https://profiles.wordpress.org/susaninhouston/)  7:31 pm _on_
     April 25, 2014
 11. Hi … I am working on “Tiny MCE: Writing Posts [https://codex.wordpress.org/Writing-Posts](https://codex.wordpress.org/Writing-Posts)
 12. ![](https://secure.gravatar.com/avatar/5058d52425c1e7f41d9e5303d1d8adfaf3a25aa78c62c6e4ebe0ecce5329090b?
     s=32&d=mm&r=g)
 13.  [designsimply](https://profiles.wordpress.org/designsimply/)  11:11 am _on_ April
     26, 2014
 14. Updated [https://codex.wordpress.org/Inserting_Media_into_Posts_and_Pages](https://codex.wordpress.org/Inserting_Media_into_Posts_and_Pages)
     for images. Feedback/edits/removal/rewrite/? of the Changes in 3.9 section welcome.
 15.  * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385?
        s=32&d=mm&r=g)
      *  [Kim Parsell](https://profiles.wordpress.org/kpdesign/)  11:45 am _on_ May
        28, 2014
      * [@designsimply](https://profiles.wordpress.org/designsimply/): It looks good–
        thank you. 🙂
 16. ![](https://secure.gravatar.com/avatar/5058d52425c1e7f41d9e5303d1d8adfaf3a25aa78c62c6e4ebe0ecce5329090b?
     s=32&d=mm&r=g)
 17.  [designsimply](https://profiles.wordpress.org/designsimply/)  7:34 pm _on_ April
     26, 2014
 18. Updated [https://codex.wordpress.org/Edit_Media#Edit_Image](https://codex.wordpress.org/Edit_Media#Edit_Image)
 19. I couldn’t get the keyboard shortcuts described at [https://codex.wordpress.org/Edit_Media#Keyboard_Shortcuts](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?
 20.  * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385?
        s=32&d=mm&r=g)
      *  [Kim Parsell](https://profiles.wordpress.org/kpdesign/)  11:29 am _on_ May
        28, 2014
      * The [issue](https://core.trac.wordpress.org/ticket/18184#comment:7) you had
        with the keyboard shortcuts not working has been reported in [#18184](https://core.trac.wordpress.org/ticket/18184).
 21. ![](https://secure.gravatar.com/avatar/eb86747d2a89ed92c485b40cf34083660311a8da46098cd2a85da2e55ff100b9?
     s=32&d=mm&r=g)
 22.  [hearvox](https://profiles.wordpress.org/hearvox/)  4:38 pm _on_ May 15, 2014
 23. 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](https://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F)
 24. 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.”
 25.  * ![](https://secure.gravatar.com/avatar/8bf29c777c4a386cb938cb3afc6fa6398259c5d31103b9704f75feba84b6b385?
        s=32&d=mm&r=g)
      *  [Kim Parsell](https://profiles.wordpress.org/kpdesign/)  11:32 am _on_ May
        28, 2014
      * [@hearvox](https://profiles.wordpress.org/hearvox/): Thanks for catching that–
        feel free to make the necessary edits to that page to correct it.
 26. ![](https://secure.gravatar.com/avatar/1676a6b7b3e4135920829aad8279e1c4cc25c6fa1e6a0b99c4fe69a8bc953366?
     s=32&d=mm&r=g)
 27.  [Daisuke Takahashi](https://profiles.wordpress.org/extendwings/)  3:29 pm _on_
     June 8, 2014
 28. Why Japanese Codex([http://wpdocs.sourceforge.jp/](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/](https://wordpress.org/)?
     
     To merge with WordPress.org may increase Japanese participation.
 29. There is no reason to keep segregated.
 30.  * ![](https://secure.gravatar.com/avatar/aa89edf971372c035a02c633667412facd8b00fd6946fe4f208f7aed7f7bb524?
        s=32&d=mm&r=g)
      *  [Naoko Takano](https://profiles.wordpress.org/nao/)  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/](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](https://groups.google.com/forum/#!forum/wp-ja-pkg)
        or [Codex P2](http://wpjadocs.wordpress.com)? Thanks.
         - ![](https://secure.gravatar.com/avatar/1676a6b7b3e4135920829aad8279e1c4cc25c6fa1e6a0b99c4fe69a8bc953366?
           s=32&d=mm&r=g)
         -  [Daisuke Takahashi](https://profiles.wordpress.org/extendwings/)  12:15
           am _on_ June 10, 2014
         - [@nao](https://profiles.wordpress.org/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](https://make.wordpress.org/).
           Could you grant me it?
            * ![](https://secure.gravatar.com/avatar/aa89edf971372c035a02c633667412facd8b00fd6946fe4f208f7aed7f7bb524?
              s=32&d=mm&r=g)
            *  [Naoko Takano](https://profiles.wordpress.org/nao/)  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](https://make.wordpress.org/) (which
              is linked to [here](http://wpdocs.sourceforge.jp/Codex:WordPress_Codex_%E6%97%A5%E6%9C%AC%E8%AA%9E%E7%89%88%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6)–
              contact info section). Alternatively you can use the [documentation forum](https://ja.forums.wordpress.org/forum/9).
      * ![](https://secure.gravatar.com/avatar/479f05d4acc73915a43b24a1ee3f30477d4ee19bbec6a5a79906d396f2b2d2ad?
        s=32&d=mm&r=g)
      *  [samuelsidler](https://profiles.wordpress.org/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.”

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/docs/2014/04/16/wordpress-3-9-codex-updates/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fdocs%2F2014%2F04%2F16%2Fwordpress-3-9-codex-updates%2F&locale=en_US)
to post a comment.

# Post navigation

[← Hi make docs — could some of you…](https://make.wordpress.org/docs/2014/04/15/hi-make-docs-could-some-of-you/)

[Massive docs props to Drew and Kim! →](https://make.wordpress.org/docs/2014/04/17/massive-docs-props-to-drew-and-kim/)