Skip to content

Improve message for config shuffle-salts result #173

Closed

Description

@ernilambar

Bug Report

Describe the current, buggy behavior

We could improve message of wp config shuffle-salts command when key does not exist.

wp config shuffle-salts WP_CACHE_KEY_SALT

Warning: Could not shuffle the unknown key 'WP_CACHE_KEY_SALT'.
Success: Shuffled the salt keys.

Activity

  1. danielbachhuber commented on Feb 16, 2024

    @danielbachhuber
    Member

    We could improve message of wp config shuffle-salts command when key does not exist.

    @ernilambar To clarify, what would be your suggested improvement?

  2. ernilambar commented on Feb 18, 2024

    @ernilambar
    MemberAuthor

    May be we can utilize report_batch_operation_results():

    wp config shuffle-salts WP_CACHE_KEY_SALT

    Warning: Could not shuffle the unknown key 'WP_CACHE_KEY_SALT'.
    Error: No configs shuffled.
    

    OR

    Warning: Could not shuffle the unknown key 'WP_CACHE_KEY_SALT'.
    Success: Shuffled 0 of 1 configs (1 skipped).
    

    wp config shuffle-salts WP_CACHE_KEY_SALT NONCE_SALT

    Warning: Could not shuffle the unknown key 'WP_CACHE_KEY_SALT'.
    Error: Only shuffled 1 of 2 configs.
    

    OR

    Warning: Could not shuffle the unknown key 'WP_CACHE_KEY_SALT'.
    Success: Shuffled 1 of 2 configs (1 skipped).
    
  3. danielbachhuber commented on Feb 18, 2024

    @danielbachhuber
    Member

    @ernilambar I'm amenable to using report_batch_operation_results().

    I would call them "salts" instead of "configs", though.

  4. ernilambar commented on Feb 18, 2024

    @ernilambar
    MemberAuthor

    @danielbachhuber Should it be Error: Only shuffled 1 of 2 salts. or Success: Shuffled 1 of 2 salts (1 skipped).?

  5. danielbachhuber commented on Feb 18, 2024

    @danielbachhuber
    Member

    @ernilambar The latter, I think

  6. ernilambar commented on Feb 19, 2024

    @ernilambar
    MemberAuthor

    @danielbachhuber I have noticed contributor-day tag in several issues. Does that mean issues should be kept for Contributor Day to be fixed?

  7. danielbachhuber commented on Feb 19, 2024

    @danielbachhuber
    Member

    @ernilambar No, only that it's a good issue for contributor day if it's still open at that time.

  8. added this to the 2.3.4 milestone on Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions