WordPress.org

Make WordPress Core

Opened 5 years ago

Last modified 10 months ago

#31039 reviewing enhancement

Move retrieve_password() from wp-login.php

Reported by: jfarthing84 Owned by: SergeyBiryukov
Milestone: Future Release Priority: normal
Severity: normal Version:
Component: Login and Registration Keywords: has-patch dev-feedback needs-refresh
Focuses: Cc:
PR Number:

Description

Once considered in #20279, I am able to propose a sane way to separate retrieve_password() from wp-login.php.

Attachments (4)

31039.patch (11.9 KB) - added by jfarthing84 5 years ago.
Separate retrieve_password() from wp-login.php
31039.3.patch (10.9 KB) - added by dimadin 5 years ago.
31039.2.patch (11.3 KB) - added by jfarthing84 20 months ago.
31039.4.patch (10.0 KB) - added by jfarthing84 20 months ago.

Download all attachments as: .zip

Change History (12)

@jfarthing84
5 years ago

Separate retrieve_password() from wp-login.php

#1 @jfarthing84
5 years ago

  • Keywords has-patch dev-feedback added

#2 @dimadin
5 years ago

I propose that we don't add new functions like in previous patch and instead we just copy existing function, introduce new parameter to switch from reliance on $_POST inside of a function.

There is quick and untested patch attached below to give you an impression.

Also, @jfarthing84 hasn't mentioned why should we do this. Thing is that it's impossible to retrieve password the other way than creating your own function. For example, lets say that you have a custom login form outside wp-login.php, you can't access this function so you need to create new one. I already did this a couple of times so that why I'm proposing making this function available to all users.

@dimadin
5 years ago

#3 @jfarthing84
3 years ago

  • Type changed from defect (bug) to enhancement

#4 @jfarthing84
20 months ago

  • Keywords needs-refresh added

I would love to see this get into core. I am ready to rebase my patch if a developer would chime in.

#5 @jfarthing84
20 months ago

Disregard 31039.2.patch as I accidentally included some changes from another proposed patch.

#6 @SergeyBiryukov
14 months ago

  • Milestone changed from Awaiting Review to 5.0
  • Owner set to SergeyBiryukov
  • Status changed from new to reviewing

#7 @SergeyBiryukov
12 months ago

  • Milestone changed from 5.0 to 5.1

#8 @pento
10 months ago

  • Milestone changed from 5.1 to Future Release

This ticket needs reviewing and further consideration.

Note: See TracTickets for help on using tickets.