Video: How to Add Feature Boxes With Icons in WordPress

WPBeginner - WordPress Tutorials originally appeared at http://www.youtube.com/watch?v=srNS6Y7kx4E

REST API meeting summary, Feb 4

The core REST API team, members of the WordPress.com API team, and other interested developers met to discuss the REST API.  Full logs of the meeting are available on Slack.

Existing endpoints

The meeting opened with a discussion of the existing endpoints: what is and isn’t ready. @rmccue summarized:

• The main focus has been on the 4 “core” objects in WordPress: posts, terms, comments, and users.
• Posts
  • Password-protected posts are going to be ignored from the API until we have a good solution.
  • Meta
    • Post (and other) meta has been pushed out into a separate feature plugin led by @jeremyfelt. Discussion is on the github repo.
    • The main issue is that there’s no differentiation between meta fields. Meta could be added via the Custom Fields meta box, or by a plugin.
    • Enhancing register_meta() in core would allow opt-in to the meta REST API – requiring some core work. See the patch on #35658 for details.
    • There is no current way to explicitly register meta as public.
    • We need to support object meta (post, user, comment, term) and object types (custom post types, etc)
  • Media
    • Mostly complete (it’s a custom post type).
    • Some special handling around uploading media.
  • Autosaves and post previews
    • Tricky, but we think we have a solution for that moving forward.
    • Working on them in a separate feature plugin instead.
    • This will be an enhancement to the API in the future, and doesn’t block compatibility.
• Terms
  • Work great.
• Users
  • Works great; undergoing final review.
• Comments
  • Works; custom comment types are harder until core better supports them.

Merge proposal and discussion

An extensive discussion ensued regarding the possibility and appropriateness of merging the endpoints into core. The discussion continued for over an hour; mainly covering whether we should merge the 4 core endpoints, or wait for a complete API before merging…  and what the definition of a complete API is.

The REST API team’s proposal is that we merge the 4 core objects in the REST API with full read, create, update, delete support, then add more peripheral features when they’re ready. 

@matt argued that we wait until the API supports everything you can do in wp-admin before merging.

The discussion revolved around these proposals and what is best for the WordPress project. Would merging the existing well developed endpoints sooner help or hinder developer adoption, and further iteration/improvement? Would delaying the endpoint merge help or hinder progress?

Here are some key comments from the discussion.

• @rmccue  The approach to the API needs to change from “the API team creates all of the API” to “the API team controls the general shape of the API, and each team works with it”
• @danielbachhuber Options / a Site Resource is more easily viable, as are Plugins and Themes. Widgets and Menus essentially need to be reinvented before they’ll work in a REST API
• @jnylen It’s a question of when, and how much testing can be done first. Shipping an API that is read-only and incomplete in several key areas feels like a big mistake.
• @kadamwhite we’re shipping an API with write capabilities but only cookie-based auth will be supported OOTB.
• @matt  I would be pretty skeptical of merging a partial API into core…  no partial endpoints in core. let’s design a complete API, not half-do it.
• @rmccue The API is specifically structured around progressive enhancement
• @jorbin I think only supporting the four core object types allows for some amazing themes and amazing content editors to be created, but doesn’t allow for full wp-admin replacements. I’m ok with that.
• @jnylen From what I’ve seen so far, I’m most concerned about shipping individual endpoints with missing features.
• @jorbin I think the best way to pick up the pace is to get key things locked up and get the four core object types in core. This would help core develop API-first for those features
• @codebykat On the WPCOM side, we’re committed to taking the plunge, but we’re not there yet which means things are untested.
• @jnylen I think this needs more testing at large scale before shipping, including some of the more difficult and obscure features of WP.
• @drew Shipping with full wp-admin replacement capability is unrealistic, imo. We need something flexible and stable that developers can use as solid jumping off point. All the rest can get separately iterated.
• @mike I think that, realistically, to ship the API… we need an MVP, and I don’t think that defining our goalpost as “all of wp-admin” fits that criteria.
• @matt Full wp-admin coverage is a firm goalpost, it gives us a super clear criteria for when it should be merged into core. is everything possible in wp-admin, possible through the API?

REST API meeting summary, Feb 4 by Adam Silverstein was originally posted at https://make.wordpress.org/core/2016/02/05/rest-api-meeting-summary-feb-4/

Call for Trac Tickets and Recap of 1/29/2016 Bug Scrub

On Friday, January 29 at 17:00 UTC, we had our regularly scheduled bug scrub. As a reminder, for the 4.5 release, trac bug scrubs will be held weekly each Friday at 17:00 UTC. Bug scrubs are held in the #core channel of WordPress Slack.

The Slack archive for last week’s meeting begins here: https://wordpress.slack.com/archives/core/p1454086872000605

During the bug scrub, the following tickets were covered:

#35216, #27048, #35010, #34887, #35243, #32602, #26571, #33717, #14853, #34996, and #14134

Tomorrow, on Friday, February 4 2016 at 17:00 UTC the bug scrub will run approximately 1 hour. Participants need not be present for the full duration, and everyone is welcome to attend.

We’ll start with a list of pre-submitted tickets, before going to an open floor.

If you would like to submit a ticket for consideration for the bug scrub, please comment below with the ticket number. If you have extensive knowledge of the ticket, attending or adding accompanying text which provides a brief description of each ticket, its current status, and what needs to happen for the ticket would be appreciated. Bug scrubs are a great way to get extra eyes on tickets, feedback on patches, or suggestions on future routes.

Call for Trac Tickets and Recap of 1/29/2016 Bug Scrub by Chris Christoff (chriscct7) was originally posted at https://make.wordpress.org/core/2016/02/04/call-for-trac-tickets-and-recap-of-1292016-bug-scrub/

Week in Core, Jan. 26 – Feb. 2 2016

Hi everybody! Welcome back to the latest issue of Week in Core, covering changes from January 26th [36407] – February 2nd [36470], changesets [36407-36470]. Here are the highlights:

• 64 commits
• 16 contributors with props
• 83 tickets created
• 6 tickets reopened
• 45 tickets closed

Ticket numbers based on trac timeline for the period above.

Note: If you want to help write the next WordPress Core Weekly summary, check out the schedule over at make/docs and get in touch in the #core-weekly-update Slack channel.

Code Updates

Networks and sites

• Replace “blog” usage with “site” in docs. [36417] [36416] #35417

Database

• Allow loading when only the mysqlnd extension is loaded. [36434] #33261

Performance

• Add a close() method to wpdb, for when the connection needs to be manually closed. [36433] #34903

Customizer

• Fix searching for available nav menu items by updating reference to nonce. [36432] #35617
• Export nonce, theme, and url app settings in preview as exported in pane. [36414] #27355, #35617
• Improve parity between JS Setting models in preview with JS Setting models in pane. [36407] #27355, #35616

Media

• In wp_read_image_metadata() make sure that IPTC keywords are UTF8 encoded. [36429] #35316

Menus

• Avoid displaying two spinners when adding selected menu items. [36427] #35682
• After [36379] prevent “Quick Search” form submission when pressing Enter. [36426] #35374
• Remove a redundant and unused 0 parameter from the Delete Menu link on the nav menus admin screen. [36419] #35641

Comments

• Add back $req variable in comments_template(). Reverts [36322]. [36425] #35473
• Add a back link to wp_die() comment form submission error display. [36424] #4332
• Fix set up/tear down of post types in comment query test. [36415] #35633

Install

• Improve the install page language chooser button style. [36423] #34547

UI

• Remove all the occurrences of the old CSS clearfix. [36422] #26396

Multisite

• Add the global cache group sites to restore_current_blog() and wp_start_object_cache(). [36413] #32450
• Add the global cache group networks to restore_current_blog(). Missed in [36258]. [36411] #35251

General

• Simplify action placement in update_metadata(). [36420] #35652
• Revert changes to wp_validate_redirect()  [35792]. This causes a regression and causes redirects to potentially fail. [35792]  #5114, #34028
• Pass additional params to get_archive_links filter. [36418] #35573

Docs

• Document the difference between site_url() and home_url(). [36408] #35238

External Libraries

• Update Random_Compat to the latest version (1.1.6). [36421] #35665

Props

Thanks to @afercia, @boonebgorges, @dd32, @ericlewis, @helen, @jorbin, @kouratoras, @nexurium, @ocean90, @pento, @rachelbaker, @sebastianpisula, @shamess, @Shelob9, @westonruter, and @wonderboymusic for their contributions!

Week in Core, Jan. 26 – Feb. 2 2016 by Andrew Rockwell was originally posted at https://make.wordpress.org/core/2016/02/04/week-in-core-jan-26-feb-2-2016/

Core Dev chat notes for Feb 3

Announcements

• @danielbachhuber announced a WP REST API meeting, happening tomorrow in #core-restapi on Slack: Thursday, February 4, 2016, 11:00 PM GMT. Full details are posted on the make/core blog.
• A reminder that the feature plugin decision deadline is coming up next week, Feb 10th.
• For the “Field Guide” posts, @jorbin proposed organizing around “focuses” and called on any feature plugins that get merged to make a post highlighting the following: anything with potential to break backwards compatibility along with significant new classes, functions, and hooks that you expect plugin, theme, and site developers to use. The goal is to have everything published before beta2.

Feature Plugin Updates

• Customizer Device Preview: @celloexpressions
  • Very close. Has UI/UX approval, a11y approval.
  • Waiting for fixes after dev review and security audit.
  • Consensus is that, pending the above, it is approved to merge in 4.5.
  • See #31195 and the related make post.

• Application Passwords: @georgestephanis
  • Application passwords got split off from two factor auth, so we’re only talking about application passwords (Two-Factor is not dead, and will come back at a later date)
  • Lets you use an application password for XMLRPC and the REST API, instead of your normal password or oAuth 1.
  • Questions and discussion around whether there is a large enough use case to make this a core feature. Consensus is that at this point, it doesn’t benefit enough end users to warrant inclusion, but might after or when the REST API endpoints land in core.

Focus Status Updates

• Customizer: @westonruter, @celloexpressions
  • Customizer Pane Resize (#32296): Stalled.
    • UX concerns from @celloexpressions need to be addressed before it can continue.
  • Selective Refresh (#27355): Getting very close.
    • Selective refresh works well together with postMessage JS-updates, as the JS update can apply an immediate (approximate) preview while the Ajax request is being made to get the actual rendered content
    • Selective refresh `partials` have associated selectors and settings, so shift-clicking on any of the containers will focus on the corresponding control in the pane.
  • Customizer notification area (#35210): Needs help!
    • In progress, but an initial patch based on available mockups is needed here.
    • This is a dependency for the setting validation model (#34893) and creating page stubs via nav menus (#34923).
  • Transactions (#30937): Punting due to dependency on the REST API and on selective refresh.

• Image Improvements: @joemcgill
  • Main focus on improving the default Imagick compression settings, some progress this week identifying the main hurdles there.
  • Could use additional opinions on #28474 (animated gif resizing) and whether it’s worth pursuing.
  • Could use some additional eyes on #34359 (particularly on multisite installs)
  • Weekly meeting is Friday at 20:00 UTC.

• Multisite/WP_Site: @jeremyfelt
  • WP_Site is in with only minor issues surfacing.
  • Considering a `sites` endpoint for the REST API – primary use right now would be to refactor the My Sites menu.
  • A new repository for the site(s) endpoint has been set up on github.
  • Some renewed interest in a network settings API (or expanding the settings API to include networks)
  • Make/core post coming soon.

• Editor: @azaozz, @iseulde
  • Going through and fixing edge cases for the inline link dialog. Please test!
  • Next will be the extending of “editing shortcuts”.

View the full logs on Slack.

Core Dev chat notes for Feb 3 by Adam Silverstein was originally posted at https://make.wordpress.org/core/2016/02/04/core-dev-chat-notes-for-feb-3/

Thar be a WP REST API meeting tomorrow

Curious as to when the WP REST API endpoints will land in WordPress core? Me too!

We’re meeting to discuss the State of the REST API just under 24 hours from now in #core-restapi on Slack: Thursday, February 4 at 23:00 UTC

The primary points of discussion are:

• Existing Post, Term, User and Comment endpoints.
• New Site, Widgets, Menus, Plugins and Themes endpoints we started on Friday.
• REST API clients — those that exist, and those that don’t yet.
• Happy fun authentication methods.

See you there!

Thar be a WP REST API meeting tomorrow by Daniel Bachhuber was originally posted at https://make.wordpress.org/core/2016/02/03/thar-be-a-wp-rest-api-meeting-tomorrow/

WordPress 4.4.2 Security Update is Out, Update Immediately

WordPress update recommendation. https://www.searchenginejournal.com/wordpress-4-4-2/155741/

WordPress 4.4.2, a security update for all versions, is now available for download. WordPress is recommending that everyone update their sites immediately.

Originally posted at The WP Guy - WordPress Web Design

No Title

How to use annotations and cards in YouTube videos to link out to a landing page (or anywhere else) on your website.

Let's clear some confusion and create a clear, easy guide on linking (adding clickable links) from inside your Youtube video.

Originally posted at The WP Guy - WordPress Web Design

4.4.2 Release Candidate

A Release Candidate for WordPress 4.4.2 is now available. This maintenance release is scheduled for tomorrow, Tuesday, February 2, but first it needs your testing. This release fixes 17 issues reported against 4.4 and 4.4.1.

WordPress 4.4 has thus far been downloaded over 20 million times since it’s release on December 8. Please test this release candidate to ensure 4.4.2 fixes the reported issues and doesn’t introduce any new ones.

Contributors

Thank you to the following 11 contributors to 4.4.2:

afercia, berengerzyla, boonebgorges, chandrapatel, chriscct7, dd32, firebird75, ivankristianto, jmdodd, ocean90, salvoaranzulla

Fixes

A total of 17 fixes are included in this RC (trac log). Notable fixes include:

• #35344 – Strange pagination issue on front page after 4.4.1 update.This was a very visible issue for certain users with specific settings. While remnants of this issue still exist (see #35689), the bulk of it has been fixed and is ready for testing.
• Comments – A total of 6 issues were fixed within the Comments component.
  • #35419 – Incorrect comment pagination when comment threading is turned off
  • #35402 – per_page parameter no longer works in wp_list_comments
  • #35378 – Incorrect comment ordering when comment threading is turned off
  • #35192 – Comments_clauses filter (issue)
  • #35478 – 4.4 Regression on Querying for Comments by Multiple Post Fields
  • #35356 – wp_list_comments ignores $comments parameter

Download & Test

We need your help to ensure there are no issues with the fixes in 4.4.2. Please download the RC and test!

4.4.2 Release Candidate by Samuel Sidler was originally posted at https://make.wordpress.org/core/2016/02/01/4-4-2-release-candidate/

Video: How to Add a Fullscreen Responsive Menu in WordPress

WPBeginner - WordPress Tutorials originally appeared at http://www.youtube.com/watch?v=CsA-AOKxziw