Not very much going on in the year’s first week – there was a design chat.
All base controls from the core can be created with the Customize JS API, except the dropdown pages control, that renders as a select list with all pages of the site. This means, we usually need to create that control via the PHP API at the moment.
As a reaction to a wordpress.stackexchange.com question, Weston Ruter wrote a plugin that lets us create the dropdown pages control via the JS API (some details on that can be found in his answer to the question). The important part is the
print_control_templates() method that creates a control template for the JS API to use when it should create a
dropdown-pages control. This template is included in the customizer with the following call in the
add_action( 'customize_controls_print_footer_scripts', array( $this, 'print_control_templates' ) );
This week, the proposed changes to the plugin guidelines have been merged. Continue reading WordPress weekly recap #52: Plugin guideline update and more
Like in 2016 I took part in the #projekt52, which was started by Torsten Landsiedel – little difference to 2016 is that I made it this year and didn't have to give up after only a few weeks. The reason for that was a small change of my attitude.
(Almost) no topic is too small for a post
The main reason for finishing the project this year was that I made the decision to stop thinking of topics as too small or unimportant for articles (I got that idea from a tweet, but unfortunately cannot say who wrote it anymore). Maybe it saves some time for another person or is helpful for yourself if you have the problem again after a while. So if I need to search for a longer time for a problem’s solution during a project, I create a draft for that.
With that, I often can finish a draft for my weekly posts instead of the need of searching a topic first. I hope to keep that output interval and write a post per week besides my weekly recap in 2018 too 🙂
Daniel Bachhuber announced that he is going to step away from day-to-day maintenance of WP-CLI, but will be available to support the team as needed. Continue reading WordPress weekly recap #51: Daniel Bachhuber steps away from day-to-day maintenance of WP-CLI and more
My article from last week was about creating panels, sections, and controls with the JS API of the customizer. This post describes how to register settings with the Customize JS API, which usually are created via the PHP API. Continue reading Creating settings with the Customize JS API
The latest Gutenberg update comes with global reusable blocks and the possibility to lock the editor for block templates, so that the user just can edit the predefined blocks but not remove, add, or move blocks. Continue reading WordPress weekly recap #50: global reusable blocks in Gutenberg and more
Until now I mostly used the PHP API of the customizer. Since Weston Ruter’s post about the improvements of the Customize JS API in WordPress 4.9, I wanted to change that and learn more about the Customize JS API. This post shows you how to create panels, sections, and controls with that API. Continue reading Creating panels, sections, and controls with the Customize JS API
This week, the WP-CLI team introduced the first working implementation of the plugin checksum verification project, that can test the file checksums of installed plugins against the checksums from WordPress.org to verify their integrity. Continue reading WordPress weekly recap #49: testing the plugin checksum verification project and more
Until now, I do not have anything to do with JS or PHP frameworks. Okay, I don't have much to do with them now (yet?), but a bit. Here I describe my first experiences with both frameworks. Continue reading My first experiences with Vue and Laravel