The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
This post summarizes the dev chat meeting from September 6th (agenda, Slack archive).
required for validationdev-feedback or 2nd-opinion on #41746
This past Wednesday, the weekly new contributor meeting was held in the #core Slack room. Here is a recap of the meeting. A full chat log is also available.
Participants: @adhun @afercia @alfonso100 @asalce @azaozz @boonebgorges @coderkevin @cousett @davidmosterd @desrosj @flixos90 @harryjackson1221 @jack50n9 @joemcgill @joyously @katmoody @mapk @mp518 @mrasharirfan @nicbertino @pbearne @psdtohtmlguru @ryankanner @sergeybiryukov @sygnoos @thomasplevy @tjnowell @xkon @yahil
If your expertise is not in code, but rather accessibility, the a11y team meets weekly, every Monday at 17:00UTC in the #accessibility Slack room. All are welcome!
Meetings are held regularly for many of the Core components and Make WordPress teams. Attending these meetings is a great way to get a feel for how progress is made within the project and find ways you can offer help.
@boonebgorges has recently spent some time constructing a new section of the WiordPress Core Handbook, “Writing PHPUnit Tests“.
__construct() functions within each factory class is currently the best place for this information.
The next meeting will take place in the #core slack channel on Wednesday, September 6, 19:00 UTC. Please feel free to drop in with any questions or tickets you’d like to discuss!
Thanks to everyone who attended! As always, please feel free to leave a comment below or reach out to any of the moderators (@adamsilverstein, @desrosj, @stevenkword, @welcher) with questions on Slack. Or, feel free to reach out to any core developer or component maintainer with questions specific to certain core areas.
This post summarizes the dev chat meeting from August 30th (agenda, Slack archive).
input type=“file”. If yes, any takers to do that?This post summarizes the dev chat meeting from July 26th (agenda, Slack archive).
This post is a summary of the latest weekly Media component meeting, which took place in #core-media on Slack, on Thursday, June 29 at 18:00 UTC. The purpose of these meetings are to move priority tasks forward, provide feedback on issues of interest, and review media focused tickets on Trac.
Attendees:
@joemcgill, @sergeybiryukov, @mikeschroder, @adamsilverstein, @desrosj, @azaozz, @karmatosed, @matias, @youknowriad, @mkaz, @joen.
Transcript: https://wordpress.slack.com/archives/C02SX62S6/p1498759231771175
Our agenda this week focussed on getting a better understanding of the current product vision for working with media in Gutenberg in order to coordinate priorities and ensure future improvements to the media component align with the needs of the new editor experience.
The major takeaway from this conversation was that Gutenberg intends to handle the UI flows for editing media within post content inside the editor itself rather than relying on the wp.media.frame modal for these actions. The image gallery block in Gutenberg is a good example of this change.
The current screen in the media modal for editing gallery settings
A preview of editing image gallery settings in the Gutenberg sidebar
By handling post-level setting in the editor, people can immediately preview changes in the editor. This change reduces the burden of the current media modal to act primarily as media library, and as a way to manage media information that applies site-wide. This should also make it more clear when changes will affect a media item site-wide, which is a nice UX win.
To prepare for this shift, we need to document the current flows that will need to be adjusted in order to support this separation between managing post-level data and site-wide media library data.
Additionally, the Gutenberg team asked for help creating blocks for additional media elements like video, audio, etc. The Gutenberg GitHub repo now contains a “media” label for collecting issues that relate to the media component.
Earlier this week, @desrosj ran a separate bug scrub focussed on new tickets on the Media component. We plan on running separate scrubs throughout the 4.9 release cycle. If you’re interested in helping with that effort, please contact @desrosj or @joemcgill on Slack.
Welcome back the latest issue of Week in Core, covering changes [40857-40877]. Here are the highlights:
Ticket numbers based on trac timeline for the period above. The following is a summary of commits, organized by component.
Thanks to @bridgetwillard, @adamsilverstein, @afercia, @azaozz, @bhargavbhandari90, @circlecube, @dimadin, @flixos90, @francina, @iandunn, @iseulde, @jenblogs4u, @johnbillion, @johnroper100, @melchoyce, @michelleweber, @obenland, @ocean90, @psiico, @rcutmore, @soniakash, @sudar, @swissspidy, @voldemortensen, and @zachwtx for their contributions!
Welcome back the latest issue of Week in Core, covering changes [40827-40856]. Here are the highlights:
Ticket numbers based on trac timeline for the period above. The following is a summary of commits, organized by component.
media_sideload_image(). [40842] #19629
https when necessary. [40843] #36451
video shortcode (primarily for Video widget) to work around ME.js 2.22 bug. [40847] #32417, #39994, #40866
Thanks to @apmarshall @obenland, @hedgefield, @reportermike, @ryelle, @rclations, @westonruter, @adamsilverstein, @apmarshall, @azaozz, @bridgetwillard, @celloexpressions, @iandunn, @jnylen0, @johnbillion, @juhise, @karmatosed, @leemon, @matveb, @melchoyce, @mikeschroder, @mohanjith, @obenland, @ocean90, @pento, @peterwilsoncc, @peterwilsoncc, @Soean, @timmydcrawford, @voldemortensen, and @westonruter for their contributions!
This post summarizes the dev chat meeting from May 24th (agenda, Slack archive).
needs-dev-note
Welcome back the latest issue of Week in Core, covering changes [40771-40826]. Here are the highlights:
Ticket numbers based on trac timeline for the period above. The following is a summary of commits, organized by component.
wp_check_browser_version(). [40822] #40839
wp_dashboard_rss_control(), for consistency with the changes to wp_dashboard_cached_rss_widget() in [33183] and [33192]. [40802] #32804, #40702
WP_Customize_Manager, WP_Customize_Control, WP_Customize_Setting, and WP_Customize_Selective_Refresh. [40804] #39671
@since tags and phpdoc descriptions to the Custom_Image_Header class. [40788] #21785, #40231
author_name before sending to JS. [40809] #39955
set_param() for some requests. [40815] #40344
Last-Modified headers with authenticated requests. [40805] #40444
X-WP-Deprecated* headers as often. [40782] #40787
isHostedVideo method on VideoWidgetControl to allow plugins to extend for recognizing services beyond YouTube and Vimeo. [40810] #39994, #40808
change event in addition to input event. [40785] #32417, #40805
Thanks to @4nickpick, @abhishekfdd, @adamsilverstein, @adamsoucie, @afercia, @arena, @arshidkv12, @azaozz, @BharatKambariya, @bradyvercher, @bridgetwillard, @coffee2code, @coreymckrill, @darshan02, @dd32, @desrosj, @emirpprime, @gma992, @iandunn, @iandunn, @iseulde, @Italian polyglots team, @iv3rson76, @jenblogs4u, @jeremyfelt, @jjcomack, @jnylen0, @joedolson, @joemcgill, @joen, @johnbillion, @juhise, @ketuchetan, @kraftbj, @leewillis77, @LiamMcArthur, @matveb, @melchoyce, @michalzuber, @michelleweber, @mihai2u, @MikeLittle, @mikeschroder, @mp518, @mrahmadawais, @netwe, @nitin, @kevadiya, @nobremarcos, @obenland, @ocean90, @odysseygate, @pento, @postpostmodern, @rellect, @rensw90, @rianrietveld, @riddhiehta02, @rmccue, @ryelle, @sagarjadhav, @sagarprajapati, @Samantha Miller., @sami.keijonen, @SergeyBiryukov, @sloisel, @sstoqnov, @stubgo, @swissspidy, @tejas5989, @timmydcrawford, @TimothyBlynJacobs, @topher1kenobe, @truongwp, @westonruter, and @zinigor for their contributions!
A new editor API was added in #35760. It makes it possible to dynamically instantiate the editor from JS. There are two parts to it:
wp_enqueue_editor().There are three new methods added to the wp.editor namespace:
wp.editor.initialize()wp.editor.remove()wp.editor.getContent()(See wp-admin/js/editor.js for more info.)
The default WordPress settings are passed to the initialize() method automatically, and can be overridden by passing a settings object on initialization, similarly to using wp_editor() in PHP.
In addition there are several custom jQuery events that are fired at different stages during initialization:
wp-before-tinymce-init is fired before initialization and can be used to set or change any editor setting. It passes the settings object.tinymce-editor-setup is fired after initialization has started but before the UI is constructed. It passes the editor instance object.tinymce-editor-init is fired when the TinyMCE instance is ready (same as the init event in TinyMCE).Here’s an example of how to add few of the default TinyMCE buttons to the toolbar:
jQuery( document ).on( 'tinymce-editor-setup', function( event, editor ) {
editor.settings.toolbar1 += ',alignleft,aligncenter,alignright';
});
Here is another example of how to add a custom button:
jQuery( document ).on( 'tinymce-editor-setup', function( event, editor ) {
editor.settings.toolbar1 += ',mybutton';
editor.addButton( 'mybutton', {
text: 'My button2',
icon: false,
onclick: function () {
editor.insertContent("It's my button!");
}
});
});
For more information please see the TinyMCE documentation.
Update: there were four “private event hacks” in the default imageplugin left over from the initial TinyMCE 4.0 implementation back in WordPress 3.9. These hacks were also removed as that plugin has changed significantly in the latest TinyMCE version.
