WordPress.org

Making WordPress.org

Opened 2 years ago

Closed 2 years ago

Last modified 4 months ago

#3678 closed defect (wontfix)

Add WP_CACHE_KEY_SALT to WordPress.org secret-key service

Reported by: kraftbj Owned by:
Milestone: Priority: normal
Component: API Keywords:
Cc:

Description

Originally posted by @paulschreiber at https://core.trac.wordpress.org/ticket/44425 . Cross-posting here for the API side of the request.

Currently, the WordPress.org secret-key service

https://api.wordpress.org/secret-key/1.1/salt/

generates AUTH_KEY, SECURE_AUTH_KEY, LOGGED_IN_KEY, NONCE_KEY, AUTH_SALT, SECURE_AUTH_SALT, LOGGED_IN_SALT and NONCE_SALT.

It would be helpful if it also generated WP_CACHE_KEY_SALT. That way, people who install the object-cache.php drop-in would be less likely to experience unexpected behaviour.

See also: https://github.com/Automattic/wp-memcached/issues/31

Change History (2)

#1 @obenland
2 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

I think I agree with Otto's comment here. If someone is qualified enough for a drop-in, I think it's reasonable to expect them to also define that constant.

#2 @paulschreiber
4 months ago

I think I agree with Otto's comment here. If someone is qualified enough for a drop-in, I think it's reasonable to expect them to also define that constant.

This argument is like saying "real programmers don't use syntax coloring." No purity tests, please.

I had to update 20 sites today ... by hand ... because the salts API (and therefore wp cli, which uses it) still doesn't support WP_CACHE_KEY_SALT.

Note: See TracTickets for help on using tickets.