Make WordPress Core

Opened 7 years ago

Closed 7 years ago

#41102 closed defect (bug) (maybelater)

Deprecate current_user_can_for_blog() and replace it with current_user_can_for_site()

Reported by: pmbaldha's profile pmbaldha Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:

Description

Since we're striving towards an API with site/network terminology in favor of blog/site long-term, we should consider deprecating current_user_can_for_blog() in favor of a current_user_can_for_site()

Change History (1)

#1 @flixos90
7 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to maybelater
  • Status changed from new to closed

Thanks for opening a ticket @pmbaldha!

However, we currently have a policy in core to only deprecate functions and improve their naming if there are more severe reasons for deprecating, for example improving performance or other technical internals of the function. Even though better names would generally help, a simple rename of a function carries a higher burden on backward compatibility than its benefits would justify.

We can revisit this once there is a more technical reason for the function to be deprecated, or in the case that we actually focus on renaming functions to follow the new conventions.

Note: See TracTickets for help on using tickets.