Make WordPress Core

Opened 12 years ago

Closed 12 years ago

#25659 closed defect (bug) (fixed)

Move upgrader_process_complete from update-core.php to Core_Upgrader

Reported by: nacin's profile nacin Owned by: dd32's profile dd32
Milestone: 3.7 Priority: normal
Severity: normal Version:
Component: Upgrade/Install Keywords: has-patch commit
Focuses: Cc:

Description

upgrader_process_complete was placed in admin/includes/update-core.php because the subsequent hook, _core_updated_successfully, has a redirect set up. However, that redirect only occurs when you are updating from < 3.4. Thus, we don't care about whether the upgrader_process_complete fires, which we use for languages.

We can thus move it to Core_Upgrader, where it belongs, and for consistent with other Upgrader classes. It also, after the move, needs $this passed to it — again, for consistency with other Upgrader classes.

Attachments (2)

25659.diff (1.1 KB) - added by nofearinc 12 years ago.
moving the upgrader_process_complete hook
25659.2.diff (1.0 KB) - added by dd32 12 years ago.

Download all attachments as: .zip

Change History (6)

@nofearinc
12 years ago

moving the upgrader_process_complete hook

#1 @nofearinc
12 years ago

  • Keywords has-patch needs-testing added

Some proposal based on your request.

#2 @nacin
12 years ago

  • Owner set to dd32
  • Status changed from new to assigned

It needs to end up in Core_Upgrader::upgrade(), looks like that patch adds it to a theme upgrader class. But yeah, the gist is correct.

@dd32
12 years ago

#3 @dd32
12 years ago

  • Keywords commit added; needs-testing removed

25659.2.diff should be all that's required here.

#4 @nacin
12 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 25861:

Move upgrader_process_complete for core to its proper place in Core_Upgrader.

This means it will be firing as a JS redirect is taking place if the update is from pre-3.4. Acceptable.

props dd32.
fixes #25659.

Note: See TracTickets for help on using tickets.