Skip to content

Application Passwords: Clarify that the environment type must be `loc… - #13954

Closed
Vedanshmini26 wants to merge 3 commits into
WordPress:trunkfrom
Vedanshmini26:fix/57388-app-passwords-local-environment
Closed

Application Passwords: Clarify that the environment type must be `loc…#13954
Vedanshmini26 wants to merge 3 commits into
WordPress:trunkfrom
Vedanshmini26:fix/57388-app-passwords-local-environment

Conversation

@Vedanshmini26

@Vedanshmini26 Vedanshmini26 commented Oct 3, 2026

Copy link
Copy Markdown

On sites without HTTPS, the Application Passwords section of the user profile screen says:

If this is a development website, you can set the environment type accordingly to enable application passwords.

This suggests setting WP_ENVIRONMENT_TYPE to development. However, wp_is_application_passwords_supported() only allows local:

return is_ssl() || 'local' === wp_get_environment_type();

So following the message leaves the feature unavailable, and the same notice keeps showing.

This PR updates the message to name the required value:

If this is a local development website, you can set the environment type to local to enable application passwords.

The support check itself is unchanged. Allowing development would enable Application Passwords over plain HTTP on development sites, which can be publicly reachable. Only the message needed correcting.

Testing Instructions

  1. On a site without HTTPS, add define( 'WP_ENVIRONMENT_TYPE', 'development' ); to wp-config.php.
  2. Go to Users > Profile and scroll to Application Passwords.
  3. Before: the notice says to set the environment type "accordingly" for a development website.
  4. After: the notice says to set the environment type to local.
  5. Change the constant to local and reload. The Application Passwords form appears.

Trac ticket: https://core.trac.wordpress.org/ticket/57388

@Vedanshmini26
Application Passwords: Clarify that the environment type must be `loc…
7560e9c 
…al`.

On sites without HTTPS, the user profile screen told administrators that application passwords could be enabled on a "development website" by setting the environment type accordingly. However, `wp_is_application_passwords_supported()` only allows the `local` environment type, so setting it to `development` left the feature unavailable.

This updates the message to state that the environment type must be set to `local`.

Fixes #57388.
@github-actions

github-actions Bot commented Oct 3, 2026 •
edited
Loading

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props sheldorofazeroth, peterwilsoncc.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions

github-actions Bot commented Oct 3, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 64091
GitHub commit: 4b2afb9

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions Bot closed this Oct 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Vedanshmini26 @peterwilsoncc