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.
I have a bookmark of at least one of the new functions that was buried in a semi-unrelated ticket. Do new functions qualify as the “needs-Codex” keyword on Trac?
I’ve compiled a list of new functions, filters and capabilities and their associated ticket numbers. I have no doubt it’s incomplete but might be useful. http://cl.ly/text/0Z1L3G1s0d01
Yes, it’s true. But I don’t think we can pull the pages from the Codex. The User Manual is really a guide in which we’ve pulled everything out that would be relevant to new users who want an easy to follow guide.
Although, nothing stopping us from grabbing content from the user manual and sticking it in the Codex.
The register_taxonomy page needs to be updated with the new ‘show_admin_column’ parameter that allows automatic creation of taxonomy columns on associated post-types.
I noted 2 situations. Old (test) multi-site setup when upgraded to WordPress 3.5 RC3 – did not change file handling URLs.
For a fresh multisite running WordPress 3.5 RC3, files are served properly without “location ~ ^/files/(.*)$” etc.
I will wait for stable 3.5. If upgrade script does not change file-handling for old WordPress then we will need to maintain 2 configs.
In any case having extra line “location ~ ^/files/(.*)$” won’t do any harm as new WordPress will not generate any request for that. (so that line will be never used)
Of course, a larger question is, what are doing about the Links section? Obviously, new users won’t be able to see the Links Manager, but the core team has moved the link manager to a plugin (if I’m understanding it right?) in order to maintain support for the time being. I think that the Link Manager will also be enabled for updates that are already using the blogroll, again, for the time being. So that section of the Codex is still valuable but can be confusing and entirely irrelevant for new users.
Perhaps we need a template like a kind of depreciated for everything from functions/template tags/admin pages that indicate “These functions are still contained in WordPress. However since version 3.5 has been disabled for users who have not used them in previous versions. If needed “Click Here” to learn how to enable or find alternatives.”
I was taking a look at the functions (I’m interested in helping with those, in particular) and noticed that wp_send_json (and related functions) appears to be pointing to the wrong ticket. I’m guessing it corresponds to http://core.trac.wordpress.org/changeset/21679 – Yes?
Siobhan, in general, I think I can be of most help on tackling a first round of descriptions/examples for the functions. Are there any higher priorities that need attention? I’m planning to dedicate up to 2 hours and I want to be as helpful as possible within my time constraint.
That would be great. I think we’ll be at our most productive if everyone tackles the docs they feel they can do best. How many do you think you could get through? I’ll stick your name beside them.
Making Screenshots for your Codex documentation? Have a copy of Photoshop and want to make nice looking Drop shadows like these? If so, here is the layer style you want to use in Photoshop:
Layer Options > Drop-shadow
Blend Mode: Multiply
Color: #888888
Opacity: 30%
Angle: 90º
Distance: 5
Spread: 8
Size: 13
EDIT: Make sure you expand your canvas before applying this layer style, and then trim away the blank parts before making your PNG.
Drew Jaynes (DrewAPicture) 8:26 pm on November 27, 2012 Permalink |
Is somebody keeping track of new/deprecated functions will need Codex entries after 3.5 drops?
Siobhan 8:27 pm on November 27, 2012 Permalink |
I suspect that there is somewhere. I’ll see if I can find out from the core team. We can add them to the list once we have them.
Michael Beckwith 8:28 pm on November 27, 2012 Permalink |
We could also easily do a diff on the depreciated.php file and see what’s been added. Just a quick thought
Siobhan 8:30 pm on November 27, 2012 Permalink |
Great plan. Have now got a list of deprecated functions!
Drew Jaynes (DrewAPicture) 8:30 pm on November 27, 2012 Permalink |
I have a bookmark of at least one of the new functions that was buried in a semi-unrelated ticket. Do new functions qualify as the “needs-Codex” keyword on Trac?
Siobhan 8:31 pm on November 27, 2012 Permalink |
They should, but tbh I don’t know. I will try to find out.
Drew Jaynes (DrewAPicture) 6:17 pm on November 29, 2012 Permalink
According to the keyword description in the handbook, needs-codex is really the only keyword the does apply.
Drew Jaynes (DrewAPicture) 6:39 pm on November 28, 2012 Permalink |
I’ve compiled a list of new functions, filters and capabilities and their associated ticket numbers. I have no doubt it’s incomplete but might be useful. http://cl.ly/text/0Z1L3G1s0d01
Kailey Lampert (trepmal) 8:33 pm on November 27, 2012 Permalink |
Just peeking at wp-includes/deprecated.php, the following functions (that have pages on the Codex) are being deprecated:
http://codex.wordpress.org/Function_Reference/user_pass_ok
http://codex.wordpress.org/Function_Reference/wp_get_single_post
http://codex.wordpress.org/Function_Reference/image_resize
http://codex.wordpress.org/Function_Reference/wp_load_image
Siobhan 8:36 pm on November 27, 2012 Permalink |
Thanks! Added
Bradley Allen 9:16 pm on November 27, 2012 Permalink |
There seems to be overlap with the Codex and new User Manual (Supporting Everything WordPress), for example:
Inserting Images into Posts and Pages
http://codex.wordpress.org/Inserting_Images_into_Posts_and_Pages
&
Adding Images
http://make.wordpress.org/support/user-manual/content/media/adding-media-to-your-pages-and-posts/adding-images/
Siobhan 9:19 pm on November 27, 2012 Permalink |
Yes, it’s true. But I don’t think we can pull the pages from the Codex. The User Manual is really a guide in which we’ve pulled everything out that would be relevant to new users who want an easy to follow guide.
Although, nothing stopping us from grabbing content from the user manual and sticking it in the Codex.
JerrySarcastic 11:38 pm on November 27, 2012 Permalink |
I’ve written sections for the new media uploader, so those can all be folded in to the codex pretty easily.
rachelbaker 2:20 am on November 28, 2012 Permalink |
Farbtastic is being depreciated in favor of the awesome Iris color picker
Relates to (in the very least) the wp_enqueue_script page: http://codex.wordpress.org/Function_Reference/wp_enqueue_script
Justin Sternberg 1:30 am on November 29, 2012 Permalink |
The register_taxonomy page needs to be updated with the new ‘show_admin_column’ parameter that allows automatic creation of taxonomy columns on associated post-types.
http://core.trac.wordpress.org/ticket/21240#comment:27
Henry Perkins 5:33 am on December 4, 2012 Permalink |
The Nginx Page, specifically for MultiSite location blocks.
http://codex.wordpress.org/Nginx
rahul286 9:39 am on December 4, 2012 Permalink |
I guess we will need changes in “location /files/” section. Yet to check how multisite file handling is implemented in 3.5.
I will update that page soon.
Henry Perkins 4:40 am on December 5, 2012 Permalink |
I used:
location ~ ^/files/(.*)$ {
try_files /wp-content/uploads/sites/$blogid/$uri /wp-includes/ms-files.php?file=$1;
}
rahul286 9:13 am on December 5, 2012 Permalink |
@Henry
Just tested WordPress 3.5′s file handling.
I noted 2 situations. Old (test) multi-site setup when upgraded to WordPress 3.5 RC3 – did not change file handling URLs.
For a fresh multisite running WordPress 3.5 RC3, files are served properly without “location ~ ^/files/(.*)$” etc.
I will wait for stable 3.5. If upgrade script does not change file-handling for old WordPress then we will need to maintain 2 configs.
In any case having extra line “location ~ ^/files/(.*)$” won’t do any harm as new WordPress will not generate any request for that. (so that line will be never used)
jhoffm34 9:55 pm on December 5, 2012 Permalink |
You can add the Links -> Add New Screen since the Link Manager will be gone. http://codex.wordpress.org/Links_Add_New_Screen
Of course, a larger question is, what are doing about the Links section? Obviously, new users won’t be able to see the Links Manager, but the core team has moved the link manager to a plugin (if I’m understanding it right?) in order to maintain support for the time being. I think that the Link Manager will also be enabled for updates that are already using the blogroll, again, for the time being. So that section of the Codex is still valuable but can be confusing and entirely irrelevant for new users.
Censorshipiswrong 8:52 pm on December 8, 2012 Permalink |
A weeks?
Ya’ll missed that December 5′th deadline by a mile. What happened?
Just wondering.
Charles Frees-Melvin 7:19 pm on December 9, 2012 Permalink |
Perhaps we need a template like a kind of depreciated for everything from functions/template tags/admin pages that indicate “These functions are still contained in WordPress. However since version 3.5 has been disabled for users who have not used them in previous versions. If needed “Click Here” to learn how to enable or find alternatives.”
Drew Jaynes (DrewAPicture) 11:14 pm on December 10, 2012 Permalink |
It would almost need to be more like a “discontinued” message than a deprecated one, especially if the functionality is still in core just not in use.
Jonathan Wold 1:30 am on December 11, 2012 Permalink |
I was taking a look at the functions (I’m interested in helping with those, in particular) and noticed that wp_send_json (and related functions) appears to be pointing to the wrong ticket. I’m guessing it corresponds to http://core.trac.wordpress.org/changeset/21679 – Yes?
Drew Jaynes (DrewAPicture) 1:34 am on December 11, 2012 Permalink |
Yes. They were all introduced as part of #21390, not 21930. I’ll update them.
Jonathan Wold 1:36 am on December 11, 2012 Permalink |
Excellent! Thanks Drew.
Jonathan Wold 1:35 am on December 11, 2012 Permalink |
Siobhan, in general, I think I can be of most help on tackling a first round of descriptions/examples for the functions. Are there any higher priorities that need attention? I’m planning to dedicate up to 2 hours and I want to be as helpful as possible within my time constraint.
Siobhan 1:30 pm on December 11, 2012 Permalink |
That would be great. I think we’ll be at our most productive if everyone tackles the docs they feel they can do best. How many do you think you could get through? I’ll stick your name beside them.
Josh Kadis 5:41 pm on December 11, 2012 Permalink |
http://codex.wordpress.org/Gallery_Shortcode should reflect the new system based on with menu_order deprecated.
Siobhan 8:27 pm on December 11, 2012 Permalink |
Added. Thanks!
Jerry Bates (JerrySarcastic) 7:43 pm on December 13, 2012 Permalink |
Making Screenshots for your Codex documentation? Have a copy of Photoshop and want to make nice looking Drop shadows like these? If so, here is the layer style you want to use in Photoshop:
Layer Options > Drop-shadow
EDIT: Make sure you expand your canvas before applying this layer style, and then trim away the blank parts before making your PNG.
Jonathan Wold 6:21 am on December 14, 2012 Permalink |
I worked with Drew and wound up tackling some of the deprecated functions and filters. That was fun!
Drew Jaynes (DrewAPicture) 7:27 am on December 14, 2012 Permalink |
You did good work. Thanks for being willing to jump in head-first!
keithics 5:43 pm on January 5, 2013 Permalink |
wp_send_json() – added examples.
keithics 5:55 pm on January 5, 2013 Permalink |
… also added some examples , edited Usage
wp_send_json_success()
wp_send_json_error()
Siobhan 11:21 pm on January 5, 2013 Permalink |
Thanks!