Title: updates – Make WordPress Core

---

#  Tag Archives: updates

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
1:04 am _on_ February 10, 2021     
Tags: [auto-update ( 24 )](https://make.wordpress.org/core/tag/auto-update/),
[auto-updates ( 13 )](https://make.wordpress.org/core/tag/auto-updates/), [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/),
[feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[feature-autoupdates ( 26 )](https://make.wordpress.org/core/tag/feature-autoupdates/),
updates   

# 󠀁[Upgrade/Install Component meeting summary – February 9, 2021](https://make.wordpress.org/core/2021/02/10/upgrade-install-component-meeting-summary-february-9-2021/)󠁿

These are the weekly notes for the [Updates/Install component](https://make.wordpress.org/core/components/upgrade-install/)
meeting that happened on Tuesday February 9, 2020. You can [read the full transcript](https://wordpress.slack.com/archives/CULBN711P/p1612893731032900)
on the _coreCore Core is the set of software required to run WordPress. The Core
Development Team builds WordPress.-auto-updates_ SlackSlack Slack is a Collaborative
Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community
has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
channel.

This meeting was focused on the **Rollback Failure Update** Feature PluginFeature
Plugin A plugin that was created with the intention of eventually being proposed
for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/),
which is a project led by [@afragen](https://profiles.wordpress.org/afragen/).

## Contribute to the Rollback Failure Update feature plugin

For now, this feature plugin is located on [@afragen](https://profiles.wordpress.org/afragen/)’
s GitHub account: https://github.com/afragen/rollback-update-failure.

Everyone is welcome to contribute. Please feel free to get in touch with the [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/)
team on Slack.

### Quick recap of the feature plugin goals

This is a feature plugin based on the [Pull Request](https://github.com/WordPress/wordpress-develop/pull/860)
proposed in the TracTrac An open source project by Edgewall Software that serves
as a bug tracker and project management tool for WordPress. ticketticket Created
for both bug reports and feature development on the bug tracker. #51857. The assumption
is that most of the errors in large plugins/themes occur during the `copy_dir()`
part of `WP_Upgrader::install_package()`. Trac ticket [#52342](https://core.trac.wordpress.org/ticket/52342)
brought more error reporting to `copy_dir()` and Trac ticket [#52831](https://core.trac.wordpress.org/ticket/52381)
provides a filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output. hook in order to do the actual rollback in the event of a pluginPlugin A
plugin is a piece of software containing a group of functions that can be added 
to a WordPress website. They can extend functionality or add new features to your
WordPress websites. WordPress plugins are written in the PHP programming language
and integrate seamlessly with WordPress. These can be free in the WordPress.org 
Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party./theme update failure. As of WordPress
5.7-beta1 both of these tickets are in core.

There was much discussion regarding the thought that adding additional IO processes
for the zip and unzip process could result in server timeout issues on resource 
starved shared hosts.

Activating the feature plugin will result in the creation of a ZIP file of the installed
plugin/theme being updated every time an update is performed. The unzip process 
only occurs during testing or a `WP_Error` resulting from `WP_Upgrader::install_package()`.

## Next steps

 * The Upgrade/Install team will publish a Feature Plugin proposal on Make/Core;
 * The feature plugin will be released on 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/)
   plugins repository;
 * A MetaMeta Meta is a term that refers to the inside workings of a group. For 
   us, this is the team that works on internal WordPress sites like WordCamp Central
   and Make WordPress. ticket will be opened on the Meta Trac in order to ask the
   meta team to create a new GitHubGitHub GitHub is a website that offers online
   implementation of git repositories that can easily be shared, copied and modified
   by other developers. Public repositories are free to host, private repositories
   require a paid subscription. GitHub introduced the concept of the ‘pull request’
   where code changes done in branches by contributors can be reviewed and discussed
   before being merged by the repository owner. [https://github.com/](https://github.com/)
   project in the WordPress.org GitHub account. [@afragen](https://profiles.wordpress.org/afragen/)
   will lead this projet on the WordPress GitHub account;
 * Provide visibility to the feature plugin;
 * Test, learn, iterate.

[#auto-update](https://make.wordpress.org/core/tag/auto-update/), [#auto-updates](https://make.wordpress.org/core/tag/auto-updates/),
[#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/), [#feature-autoupdates](https://make.wordpress.org/core/tag/feature-autoupdates/),
[#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/georgestephanis/) [George Stephanis](https://profiles.wordpress.org/georgestephanis/)
3:52 pm _on_ December 11, 2015     
Tags: [feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[two-factor ( 12 )](https://make.wordpress.org/core/tag/two-factor/), updates   

# 󠀁[2FA! 2FA! 2FA!](https://make.wordpress.org/core/2015/12/11/2fa-2fa-2fa/)󠁿

Howdy, all! I’m back, and we’re getting the Two-Factor Train rolling again!

We had our first meeting yesterday at the usual time (22:00 UTC / 5pm Eastern) in
[#core-passwords](https://make.wordpress.org/core/tag/core-passwords/).

https://wordpress.slack.com/archives/core-passwords/p1449784908000119

Following some critical feedback and discussions both at the Community Summit and
at WordCampWordCamp WordCamps are casual, locally-organized conferences covering
everything related to WordPress. They're one of the places where the WordPress community
comes together to teach one another what they’ve learned throughout the year and
share the joy. [Learn more](https://central.wordcamp.org/about/). US, we’re adjusting
our focus. Technical feasibility is turning out to be far less of a concern than
ensuring we don’t create an undue support burden by users getting locked out and
providing a way back in.

Previously, we had been anticipating the primary way to override a loss of their
second factor would be either adding a constant or modifying the database records(
either directly or via a shell tool such as WP-CLIWP-CLI WP-CLI is the Command Line
Interface for WordPress, used to do administrative and development tasks in a programmatic
way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/)).
However, we have had a number of concerns from assorted interested parties, and 
the fact of the matter is that it is feeling like too high of a barrier for many
WordPress users. As [@macmanx](https://profiles.wordpress.org/macmanx/) (new Forums
Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to
the rest of the project, make sure issues are raised and addressed as needed, and
coordinates cross-team efforts.) summarized in our chat yesterday,

> I’ll say it this way: We want users to be able to secure their sites with 2FA,
> not sit back and watch outdated abandoned sites pile up because they locked themselves
> out and simply give up when when we mention FTPFTP FTP is an acronym for File 
> Transfer Protocol which is a way of moving computer files from one computer to
> another via the Internet. You can use software, known as a FTP client, to upload
> files to a server for a WordPress website. [https://codex.wordpress.org/FTP_Clients](https://codex.wordpress.org/FTP_Clients),
> Database, or SSHSSH Secure SHell - a protocol for securely connecting to a remote
> system in addition to or in place of a password..

So, there are several things that have been brought up:

####  Require a constant in `wp-config.php` to enable 2FA

The idea being that, by adding a constant to wp-config, the user has demonstrated
that they know how to use FTP and edit files on their server manually, so if all
goes to heck, they have the ability and knowledge to take the constant back out,
so they can get back into their site adminadmin (and super admin).

I feel that this is a bad idea, because it violates many of the [WordPress Core Philosophies](https://wordpress.org/about/philosophy/).
It wouldn’t work out of the box, and we’re no longer designing for the majority.
It results in us adding not only an option, but an option that’s hard to set.

If we have to hide it behind a constant, I feel that it shouldn’t even be in CoreCore
Core is the set of software required to run WordPress. The Core Development Team
builds WordPress., and would be better left as a pluginPlugin A plugin is a piece
of software containing a group of functions that can be added to a WordPress website.
They can extend functionality or add new features to your WordPress websites. WordPress
plugins are written in the PHP programming language and integrate seamlessly with
WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party..

(yes, I know Multisitemultisite Used to describe a WordPress installation with a
network of multiple blogs, grouped by sites. This installation type has shared users
tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts).
See also **network**, **blog**, **site** runs this way, but there are other reasons
that was merged into core)

####  Require multiple providers being enabled

The idea here being that if the user has two, there is less likelihood of getting
locked out as they’d have a backup. However, for myself, I can’t tell you how many
times I’ve downloaded backup codes and promptly lost them. Or how many times my 
phone has been destroyed (washing machines and phones shouldn’t be friends). There’s
still a lot of opportunity for things to go wrong, especially on the scale of powering
a quarter of the web. Edge cases become commonplace. 🙁

####  Send Text Messages

No can do, this would require a third-party server to send them through, and that’s
plugin territory.

####  Leave Emailed Codes as an always-available fallback

This, I feel is our best option.

There are some concerns regarding the large percentage of WordPress sites that are
on servers that can’t send email (as high as 25% by some guesstimates I’ve heard
floated), so we’d need to send a code and make sure it gets received before turning
on the actual two-factor login prompt.

While it doesn’t provide the best security (if someone breaks into your email address,
they could both reset your password and get the incoming authentication code), it
is 1) no worse than the status quo, 2) not our responsibility to keep secure, and
3) if they’ve broken into your email, you probably have bigger concerns.

We can certainly include a filterFilter Filters are one of the two types of Hooks
[https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output. for methods to disable / add from plugins, and so if someone wants to disable
email manually, they totes can. By explicitly disabling the Core security feature,
they’re then demonstrating that they know enough to fix it if it goes wrong.

In the end, my feelings were largely best summed up by [@michael-arestad](https://profiles.wordpress.org/michael-arestad/),
describing the two ways of balancing ease of use versus airtight security:

>  Ease-of-use: core potential
>  Airtight security: plugin town

And we can always ship the plugin ourselves to let folks disable Email, but that
feels like if it were in wp-admin that we’d be giving them just enough rope to hang
themselves. 🙁

===

Now, none of this is finalized, so if you disagree, please voice your concerns in
the comment section below. I’m hoping that we’ll get enough discussion that we’ll
be able to confidently make a final decision on what path we’re taking at next week’s
meeting — which will be on Thursday at 5pm Eastern / 22:00 UTC in [#core-passwords](https://make.wordpress.org/core/tag/core-passwords/)

[#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/), [#two-factor](https://make.wordpress.org/core/tag/two-factor/),
[#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/danielbachhuber/) [Daniel Bachhuber](https://profiles.wordpress.org/danielbachhuber/)
9:30 pm _on_ November 2, 2015     
Tags: [chats ( 25 )](https://make.wordpress.org/core/tag/chats/),
[feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [shortcode UI ( 18 )](https://make.wordpress.org/core/tag/shortcode-ui/),
[shortcodes ( 30 )](https://make.wordpress.org/core/tag/shortcodes/), updates   

# 󠀁[Shortcake (Shortcode UI) chat summary – November 2nd, 2015](https://make.wordpress.org/core/2015/11/02/shortcake-shortcode-ui-chat-summary-november-2nd-2015/)󠁿

Present: [@danielbachhuber](https://profiles.wordpress.org/danielbachhuber/), [@goldenapples](https://profiles.wordpress.org/goldenapples/),
[@matth_eu](https://profiles.wordpress.org/matth_eu/)

Logs: https://wordpress.slack.com/archives/feature-shortcode/p1446494424000273

 * We released Shortcake v0.6.0. [Read through the full release notes](http://fusion.net/story/225765/introducing-shortcake-v0-6-0-cream/).
 * Weekly meetings are on hold until January. Between now and then, we’ll be thinking
   about what we need to do to put forth a coreCore Core is the set of software 
   required to run WordPress. The Core Development Team builds WordPress. proposal.
   [@matth_eu](https://profiles.wordpress.org/matth_eu/) might put together sketches.
 * We missed the boat on getting a Shortcake representative to the community summit,
   and are researching ways to helicopter [@goldenapples](https://profiles.wordpress.org/goldenapples/)
   to said community summit boat.

Next chat: sometime in January 2016

[#chats](https://make.wordpress.org/core/tag/chats/), [#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/),
[#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#shortcode-ui](https://make.wordpress.org/core/tag/shortcode-ui/),
[#shortcodes](https://make.wordpress.org/core/tag/shortcodes/), [#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/danielbachhuber/) [Daniel Bachhuber](https://profiles.wordpress.org/danielbachhuber/)
7:42 pm _on_ October 5, 2015     
Tags: [chats ( 25 )](https://make.wordpress.org/core/tag/chats/),
[feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [shortcode UI ( 18 )](https://make.wordpress.org/core/tag/shortcode-ui/),
[shortcodes ( 30 )](https://make.wordpress.org/core/tag/shortcodes/), updates   

# 󠀁[Shortcake (Shortcode UI) chat summary – October 5th, 2015](https://make.wordpress.org/core/2015/10/05/shortcake-shortcode-ui-chat-summary-october-5th-2015/)󠁿

Present: [@danielbachhuber](https://profiles.wordpress.org/danielbachhuber/), [@goldenapples](https://profiles.wordpress.org/goldenapples/),
[@matth_eu](https://profiles.wordpress.org/matth_eu/)

Logs: https://wordpress.slack.com/archives/feature-shortcode/p1444071794000007

 * Matt’s making process on support for encoding HTMLHTML HyperText Markup Language.
   The semantic scripting language primarily used for outputting content in web 
   browsers. in attributes. Gallery functionality is also almost done, but there’s
   one small bugbug A bug is an error or unexpected result. Performance improvements,
   code optimization, and are considered enhancements, not defects. After feature
   freeze, only bugs are dealt with, with regressions (adverse changes from the 
   previous version) being the highest priority..
 * Than started work on trying to add some filters that can be used to handle floated/
   non-blockBlock Block is the abstract term used to describe units of markup that,
   composed together, form the content or layout of a webpage using the WordPress
   editor. The idea combines concepts of what in the past may have achieved with
   shortcodes, custom HTML, and embed discovery into a single consistent API and
   user experience. previews. It still some work to go, as it’ll involve overriding
   some methods deep in mce.view.
 * Daniel will hit up the backlog when he has a moment, as there are a number of
   unanswered open issues.
 * We discussed inline editing and [agreed upon an ideal abstraction](https://github.com/fusioneng/Shortcake/issues/116#issuecomment-145644910).

Next chat: [same time and place](https://make.wordpress.org/core/2015/04/01/shortcake-shortcode-ui-has-a-weekly-meeting-time-mondays-at-7-pm-utc/)

Next release: [v0.6.0](https://github.com/fusioneng/Shortcake/milestones/v0.6.0)–
Tuesday, November 3rd

[#chats](https://make.wordpress.org/core/tag/chats/), [#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/),
[#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#shortcode-ui](https://make.wordpress.org/core/tag/shortcode-ui/),
[#shortcodes](https://make.wordpress.org/core/tag/shortcodes/), [#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/joemcgill/) [Joe McGill](https://profiles.wordpress.org/joemcgill/)
10:21 pm _on_ September 5, 2015     
Tags: [feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[media ( 92 )](https://make.wordpress.org/core/tag/media/), [respimg ( 6 )](https://make.wordpress.org/core/tag/respimg/),
updates   

# 󠀁[Responsive Images Feature Plugin Update](https://make.wordpress.org/core/2015/09/05/responsive-images-feature-plugin-update/)󠁿

Following up on our [first official project update](https://make.wordpress.org/core/2015/08/25/responsive-image-support-update/),
here’s a brief status update to keep everyone informed about the progress we’ve 
made.

## Updates

 * Released [v2.4.0](https://wordpress.org/plugins/ricg-responsive-images/) early
   last week, fixing several bugs and adding a few filters ([changelog](https://wordpress.org/plugins/ricg-responsive-images/changelog/)).
   Please test on your sites and leave us feedback!
 * Created placeholder tickets for adding `srcset` and `sizes` support ( [#33641](https://core.trac.wordpress.org/ticket/33641))
   and improving the compression settings of Imagick ( [#33642](https://core.trac.wordpress.org/ticket/33642)).
 * [@jaspermdegroot](https://profiles.wordpress.org/jaspermdegroot/) is digging 
   into the content filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
   They provide a way for functions to modify data of other functions. They are 
   the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
   manner, and should never have side effects such as affecting global variables
   and output. approach to support responsive images for old posts. Performance 
   tests and details [on GitHub](https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images/pull/144).
   Feedback appreciated!

## Next Steps

We’re ready to create an initial patchpatch A special text file that describes changes
to code, by identifying the files and lines which are added, removed, and altered.
It may also be referred to as a **diff**. A patch can be _applied_ to a codebase
for testing. candidate for coreCore Core is the set of software required to run 
WordPress. The Core Development Team builds WordPress.. We’ll be working on that
over the next week, with a more detailed update at that time.

Check out the [logs from our last meeting](https://wordpress.slack.com/archives/feature-respimg/p1441393327000613)
and join us for the next one on [Friday at 19:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20150911T1900)
in [#feature-respimg](https://wordpress.slack.com/messages/feature-respimg/).

Questions? Please leave feedback below, or ask anytime in [#feature-respimg](https://wordpress.slack.com/messages/feature-respimg/).

[#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/), [#media](https://make.wordpress.org/core/tag/media/),
[#respimg](https://make.wordpress.org/core/tag/respimg/), [#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/swissspidy/) [Pascal Birchler](https://profiles.wordpress.org/swissspidy/)
6:31 am _on_ September 2, 2015     
Tags: [embeds ( 10 )](https://make.wordpress.org/core/tag/embeds/),
[feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[feature-oembed ( 10 )](https://make.wordpress.org/core/tag/feature-oembed/), updates

# 󠀁[oEmbed Feature Plugin Update](https://make.wordpress.org/core/2015/09/02/oembed-feature-plugin-update/)󠁿

After [kicking off the oEmbed feature plugin](https://make.wordpress.org/core/2015/07/17/oembed-feature-plugin/)
a couple of weeks ago, it’s high time for another status update.

In case you have missed it, the [oEmbed API](https://wordpress.org/plugins/oembed-api/)
pluginPlugin A plugin is a piece of software containing a group of functions that
can be added to a WordPress website. They can extend functionality or add new features
to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. makes WordPress an oEmbed provider,
allowing you to embed blogblog (versus network, site) posts just like YouTube videos
or tweets. Of course everything happens with security and ease-of-use in mind.

![oEmbed Feature Plugin](https://make.wordpress.org/core/files/2015/09/oembed-feature-
plugin-update-september-1-1024x523.png)

Embedding a post is super simple!

We made some great progress over the last few weeks. The highlights are:

 * Improved test coverage, which led to many fixed bugs
 * Auto-resizing of the embedded iframeiframe iFrame is an acronym for an inline
   frame. An iFrame is used inside a webpage to load another HTML document and render
   it. This HTML document may also contain JavaScript and/or CSS which is loaded
   at the time when iframe tag is parsed by the user’s browser. so it looks great
   on every screen
 * It seamlessly integrates with the REST APIREST API The REST API is an acronym
   for the RESTful Application Program Interface (API) that uses HTTP requests to
   GET, PUT, POST and DELETE data. It is how the front end of an application (think“
   phone app” or “website”) can communicate with the data store (think “database”
   or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/),
   but also works perfectly without it

The plugin is very stable so far. We’re looking into bringing it to WordPress.comWordPress.
com An online implementation of WordPress code that lets you immediately access 
a new WordPress environment to publish your content. WordPress.com is a private 
company owned by Automattic that hosts the largest multisite in the world. This 
is arguably the best place to start blogging if you have never touched WordPress
before. [https://wordpress.com/](https://wordpress.com/) for testing, but of course
we also need _your_ help to bring this further! [Download the plugin from the repository](https://wordpress.org/plugins/oembed-api/)—
play with it, break it, and help us fixing all bugs that may appear. We’re always
looking for areas to improve.

We’re now mainly working on getting it into shape for an eventual coreCore Core 
is the set of software required to run WordPress. The Core Development Team builds
WordPress. merge proposal and implementing the different oEmbed response types. 
This means supporting embedding attachment posts and posts with different post formats.

Please, test and report both errors and suggestions either on [GitHub](https://github.com/swissspidy/oEmbed-API)
or our [#feature-oembed](https://wordpress.slack.com/messages/feature-oembed/) SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)
channel. Anyone is welcome to join us!

**Next chat:** [September 7 2015 9pm UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20150907T2100)

[#embeds](https://make.wordpress.org/core/tag/embeds/), [#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/),
[#feature-oembed](https://make.wordpress.org/core/tag/feature-oembed/), [#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/danielbachhuber/) [Daniel Bachhuber](https://profiles.wordpress.org/danielbachhuber/)
8:16 pm _on_ August 31, 2015     
Tags: [chats ( 25 )](https://make.wordpress.org/core/tag/chats/),
[feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [shortcode UI ( 18 )](https://make.wordpress.org/core/tag/shortcode-ui/),
[shortcodes ( 30 )](https://make.wordpress.org/core/tag/shortcodes/), updates   

# 󠀁[Shortcake (Shortcode UI) chat summary – August 31st, 2015](https://make.wordpress.org/core/2015/08/31/shortcake-shortcode-ui-chat-summary-august-31st-2015/)󠁿

Present: [@danielbachhuber](https://profiles.wordpress.org/danielbachhuber/), [@matth_eu](https://profiles.wordpress.org/matth_eu/)

Logs: https://wordpress.slack.com/archives/feature-shortcode/p1441047764000146

 * v0.5.0 was [released last Wednesday](http://fusion.net/story/182883/introducing-shortcake-v0-5-0-sugar/).
 * We picked a release date for v0.6.0: Tuesday, November 3rd.
 * Opened a [bunch of issues to work on](https://github.com/fusioneng/Shortcake/issues?utf8=%E2%9C%93&q=label%3Acore-integration+)
   for final coreCore Core is the set of software required to run WordPress. The
   Core Development Team builds WordPress. integration.
 * Triaged the issue backlog a bit.

Next chat: [same time and place](https://make.wordpress.org/core/2015/04/01/shortcake-shortcode-ui-has-a-weekly-meeting-time-mondays-at-7-pm-utc/)

Next release: [v0.6.0](https://github.com/fusioneng/Shortcake/milestones/v0.6.0)–
Tuesday, November 3rd

[#chats](https://make.wordpress.org/core/tag/chats/), [#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/),
[#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#shortcode-ui](https://make.wordpress.org/core/tag/shortcode-ui/),
[#shortcodes](https://make.wordpress.org/core/tag/shortcodes/), [#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/georgestephanis/) [George Stephanis](https://profiles.wordpress.org/georgestephanis/)
2:31 pm _on_ August 31, 2015     
Tags: [feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[two-factor ( 12 )](https://make.wordpress.org/core/tag/two-factor/), updates   

# 󠀁[Two-Factor Auth Update](https://make.wordpress.org/core/2015/08/31/two-factor-auth-update/)󠁿

It’s been a couple weeks since our last update, but we’ve had some solid headway
in the last couple days!

Current status of default providers:

 * Email: In and works.
 * FIDO U2F: In and works, but only for PHPPHP The web scripting language in which
   WordPress is primarily architected. WordPress requires PHP 7.4 or higher 5.3+(
   library dependency, non-trivial to revise for 5.2)
 * Backup Codes: In and works.
 * TOTP (Google Authenticator): Pull request open (several, actually), I expect 
   to see it merged in the next couple days.

For the providers that are in and works, there may be minor issues either via code
architecture or enhancements like better ui / ajax or whatnot — it’s just easier
to solve those via small pull requests to master, versus endlessly debating in a
pull request without actually merging it in. 🙂

Application Passwords are also included in the pluginPlugin A plugin is a piece 
of software containing a group of functions that can be added to a WordPress website.
They can extend functionality or add new features to your WordPress websites. WordPress
plugins are written in the PHP programming language and integrate seamlessly with
WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. currently, however I’m not sure 
whether they should be a part of it or not in the end — they are included to allow
users who use two-factor authentication to still use xml-rpc functionality, which
can’t support two-factor authentication.

For TOTP, we will need to be able to generate QR codes, and the de facto standard
library I’ve found for generating them locally seems to be https://github.com/kazuhikoarase/
qrcode-generator — which has both PHP and JS implementations and is MIT licensed.
I’m currently leaning towards the JS implementation, but I’d be fine with PHP instead.
Either way works just as easily.

Please, [test](https://wordpress.org/plugins/two-factor/) and report both errors
and suggestions either on [GitHub](https://github.com/georgestephanis/two-factor/issues/new)
or on [our Slack channel — #core-passwords](https://wordpress.slack.com/messages/core-passwords/).

As always, our next chat will be on Thursday at 5pm Eastern, in [#core-passwords](https://make.wordpress.org/core/tag/core-passwords/).

[#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/), [#two-factor](https://make.wordpress.org/core/tag/two-factor/),
[#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/joemcgill/) [Joe McGill](https://profiles.wordpress.org/joemcgill/)
11:35 pm _on_ August 25, 2015     
Tags: [feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[media ( 92 )](https://make.wordpress.org/core/tag/media/), [respimg ( 6 )](https://make.wordpress.org/core/tag/respimg/),
updates   

# 󠀁[Update: Responsive Image Support for Core](https://make.wordpress.org/core/2015/08/25/responsive-image-support-update/)󠁿

The responsive image team has been meeting regularly for a while. After our meeting
earlier this week, we realized that make/coreCore Core is the set of software required
to run WordPress. The Core Development Team builds WordPress. needs an update on
what’s been going on with the RICG (Responsive Images Community Group) feature pluginFeature
Plugin A plugin that was created with the intention of eventually being proposed
for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/),
as well as to request feedback on a few questions.

Our meetings are in [#feature-respimg](https://wordpress.slack.com/messages/feature-respimg/)
each [Friday at 1900 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260619T1900),
so please come and chat to give feedback or if you’re interested in helping out!

## Background

Several years ago, [a ragtag group of web professionals](http://responsiveimages.org/)
identified a need for new HTMLHTML HyperText Markup Language. The semantic scripting
language primarily used for outputting content in web browsers. markup which would
allow developers to declare multiple sources for an image—allowing devices to select
the image source that was most appropriate for its own capabilitiescapability A **
capability** is permission to perform one or more types of task. Checking if a user
has a capability is performed by the `current_user_can` function. Each user of a
WordPress site might have some permissions but not others, depending on their role.
For example, users who have the Author role usually have permission to edit their
own posts (the “edit_posts” capability), but not permission to edit other users’
posts (the “edit_others_posts” capability).. Fast forward to today and all major
browsers have either implemented these new tools or currently have them under consideration
for development.

With that as background, the RICG has been working on an [_Official WordPress Feature Plugin™_](https://wordpress.org/plugins/ricg-responsive-images/)
to test the viability of adding responsive image support natively into WordPress.
Specifically, our aim is to automatically add `srcset` (using `w` descriptors) and`
sizes` attributes to the image markup generated by WordPress. According to the [WordPress.org plugin directory](https://wordpress.org/plugins/ricg-responsive-images/stats/),
there are over 10k active installs, so we’ve definitely seen an interest in this
functionality.

There are two main pieces of functionality included in the pluginPlugin A plugin
is a piece of software containing a group of functions that can be added to a WordPress
website. They can extend functionality or add new features to your WordPress websites.
WordPress plugins are written in the PHP programming language and integrate seamlessly
with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party., which can be considered separately
for inclusion in core:

 1. Logic for producing responsive image markup
 2. Advanced image compression (via ImageMagick)

## Responsive Image Markup

There is a lot to consider when proposing a change to the way WordPress outputs 
image markup, so I want to be clear about some of our assumptions going in:

 * Responsive image support should be added ‘invisibly’ without introducing new 
   settings for users to worry about.
 * WordPress, out of the box, should only deal with resolution switching, and not
   the [art direction use case](https://usecases.responsiveimages.org/#art-direction)
   for now. In other words, we would not be adding any APIAPI An API or Application
   Programming Interface is a software intermediary that allows programs to interact
   with each other and share data in limited, clearly defined ways. or adminadmin(
   and super admin) UIUI User interface for outputting different cropped images 
   at specific breakpoints. (For more information about use cases and all things
   related to responsive images, I’d recommend reading the terrific [Responsive Image 101](http://blog.cloudfour.com/responsive-images-101-definitions/)
   series by Jason Grigsby).
 * Provide this functionality using default and available user-defined sizes (via`
   add_image_size()`) for source sets rather than creating an additional set of 
   crops. This choice is based on [early feedback from Nacin](https://wordpress.slack.com/archives/feature-respimg/p1419393836000051)
   regarding file-count concerns on some shared hosts.
 * Provide filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
   They provide a way for functions to modify data of other functions. They are 
   the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
   manner, and should never have side effects such as affecting global variables
   and output. hooksHooks In WordPress theme and development, hooks are functions
   that can be applied to an action or a Filter in WordPress. Actions are functions
   performed when a certain event occurs in WordPress. Filters allow you to modify
   certain functions. Arguments used to hook both filters and actions look the same.
   so theme/plugin authors can extend/override defaults.
 * All sizes of an image (i.e., `_wp_attachment_metadata['sizes']`) with the same
   aspect ratio are resized versions of the same image, not custom art directed 
   crops. This assumption has been okay so far, but there may be be plugins that
   replace the default image sizes with art directed crops that maintain the same
   aspect ratio. We’ll need to determine how to handle these cases.

### Questions to Consider

 1. How should we handle markup embedded in post content?
 2.  * Currently, we embed the `srcset` attribute directly into posts with `sizes` 
       added as a data attribute to make it easier for theme authors to filter the `
       sizes` attribute later. It’s tricky to decide when it’s appropriate to add layout
       relative markup to the database, but WordPress is currently doing this to a 
       certain extent by adding width/height attributes to images, so this may be the
       best solution for now.
     * Instead, a more elegant solution would be to filter the content on output. This
       would avoid saving layout markup in the database, and extend support to posts
       with images that were published before the feature became available. We have
       [a proof of concept](https://github.com/ResponsiveImagesCG/wp-tevko-responsive-images/pull/144/files)
       but are unsure if adding another filter to `the_content` is appropriate. Confirmation
       either way on this question would help us move forward.
 3. Should we support `srcset` and `sizes` in older browsers?
 4.  * The plugin includes the [picturefill.js](https://scottjehl.github.io/picturefill/)
       polyfill, which provides support for older browsers, but would be a new dependency
       for core.
     * We could view `srcset` and `sizes` as a progressive enhancementenhancement Enhancements
       are simple improvements to WordPress, such as the addition of a hook, a new 
       feature, or an improvement to an existing feature. and only provide support 
       in WordPress for newer browsers. In that case, we could drop the polyfill and
       save WordPress an extra JSJS JavaScript, a web scripting language typically 
       executed in the browser. Often used for advanced user interfaces and behaviors.
       dependency. Note that this polyfill is written by the same people writing and
       implementing the spec. We consider it to be very reliable.
 5. Should we turn responsive image support on by default?
 6.  * “Decisions not options.” We propose that responsive images are enabled by default
       in core, with filters provided for disabling or modifying the feature.
     * If core does not want responsive images enabled by default, they could be enabled
       through a `current_theme_supports()` flag. Themes would have to “opt-in” to 
       the feature.

## Advanced Image Compression

The second potential enhancement introduced through our plugin is an improvement
to the default ImageMagick compression settings currently being used in core. RICG
contributor Dave Newton has done great research on the [best compression settings for ImageMagick](http://www.smashingmagazine.com/2015/06/efficient-image-resizing-with-imagemagick/),
and included them as an opt-in option within the plugin.

The updated settings are absolutely _killer_ when there are sufficient CPU and memory
resources on the host server. In our trials, [file sizes have decreased by >50%](http://www.smashingmagazine.com/2015/06/efficient-image-resizing-with-imagemagick/#the-results-or-is-this-even-worth-it)
compared to the default core settings.

However, on limited servers, these new settings could cause problems. We are iterating
on them to find the right balance between the file-size savings and the CPU resources
required to process large files.

## Final Notes

We need your help!

New features need lots of feedback and testing. Help us test these enhancements 
by installing the [latest version of the plugin](https://wordpress.org/plugins/ricg-responsive-images/)
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/).

Be sure to enable advanced image compression and tell us how it does with your setup
so we can gather more feedback.

If you know of plugins that heavily modify or interact with custom image sizes or
art-directed crops, please leave a comment below so we can test it with this feature.

Have thoughts on the questions above? Let us know in the comments!

Want to get involved? We meet each week in [#feature-respimg](https://wordpress.slack.com/messages/feature-respimg/)
on [Friday at 1900 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260619T1900).

[#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/), [#media](https://make.wordpress.org/core/tag/media/),
[#respimg](https://make.wordpress.org/core/tag/respimg/), [#updates](https://make.wordpress.org/core/tag/updates/)

 [  ](https://profiles.wordpress.org/danielbachhuber/) [Daniel Bachhuber](https://profiles.wordpress.org/danielbachhuber/)
8:11 pm _on_ August 24, 2015     
Tags: [feature plugins ( 122 )](https://make.wordpress.org/core/tag/feature-plugins/),
[meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [shortcode UI ( 18 )](https://make.wordpress.org/core/tag/shortcode-ui/),
[shortcodes ( 30 )](https://make.wordpress.org/core/tag/shortcodes/), updates   

# 󠀁[Shortcake (Shortcode UI) chat summary – August 24th, 2015](https://make.wordpress.org/core/2015/08/24/shortcake-shortcode-ui-chat-summary-august-24th-2015/)󠁿

Present: [@danielbachhuber](https://profiles.wordpress.org/danielbachhuber/), [@goldenapples](https://profiles.wordpress.org/goldenapples/),
[@miqrogroove](https://profiles.wordpress.org/miqrogroove/), [@azaozz](https://profiles.wordpress.org/azaozz/)

Logs: https://wordpress.slack.com/archives/feature-shortcode/p1440442841000013

 * We triaged the remaining issues for v0.5.0. Daniel will be picking them up over
   the next day.
 * A big project for v0.6.0 will be to go through coreCore Core is the set of software
   required to run WordPress. The Core Development Team builds WordPress.’s feature
   pluginFeature Plugin A plugin that was created with the intention of eventually
   being proposed for inclusion in WordPress Core. See [Features as Plugins](https://make.wordpress.org/core/handbook/about/release-cycle/features-as-plugins/)
   guidelines and identify what we need to change to be valid.
 * Spent time discussing [@miqrogroove](https://profiles.wordpress.org/miqrogroove/)
   [summary of shortcode problems](http://www.miqrogroove.com/blog/2015/shortcode-v44/),
   and proposed solutions

Next chat: [same time and place](https://make.wordpress.org/core/2015/04/01/shortcake-shortcode-ui-has-a-weekly-meeting-time-mondays-at-7-pm-utc/)

Next release: [v0.5.0](https://github.com/fusioneng/Shortcake/issues?utf8=%E2%9C%93&q=milestone%3Av0.5.0+)–
this week (a bit overdue)

[#feature-plugins](https://make.wordpress.org/core/tag/feature-plugins/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/),
[#shortcode-ui](https://make.wordpress.org/core/tag/shortcode-ui/), [#shortcodes](https://make.wordpress.org/core/tag/shortcodes/),
[#updates](https://make.wordpress.org/core/tag/updates/)

# Post navigation

[← Older posts](https://make.wordpress.org/core/tag/updates/page/2/?output_format=md)