Skip to:
Content

bbPress.org

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#3052 closed task (fixed)

Split "Upgrade" tools into new section

Reported by: johnjamesjacoby Owned by: johnjamesjacoby
Milestone: 2.6 Priority: high
Severity: normal Version: 2.2
Component: Tools Keywords: commit
Cc:

Description

bbPress's database upgrades deserve their own section under "Tools."

They are unique in a few ways:

  • You only really need to run them once
  • They don't "Repair" anything, really
  • As we point more users to important upgrades, a dedicated page is a better experience
  • Large forums are unique, in that these types of upgrades will more frequently require monitoring than WordPress traditionally will

Maybe more importantly, I've already done all the work here (and it confirmed my suspicions) so let's do it.

Attachments (1)

Screen Shot 2017-02-03 at 11.41.15 AM.png (295.6 KB) - added by johnjamesjacoby 3 years ago.

Download all attachments as: .zip

Change History (5)

#1 @johnjamesjacoby
3 years ago

  • Owner set to johnjamesjacoby
  • Resolution set to fixed
  • Status changed from new to closed

In 6279:

Tools: Introduce new "Upgrade Forums" tools section.

  • Uses some awesome trickery to reuse as much of the "Repair Forums" API as possible
  • Introduces a few new functions to handle the output of the new screen
  • Removes hard-coded referencs to bbp-repair page, to allow usage on any relevant page (including new bbp-upgrade)
  • Makes components & overhead lists smarter, and only includes items relevant to the current view

Fixes #3052.

#2 @johnjamesjacoby
3 years ago

In 6280:

Tools: Map bbp_tools_upgrade_page capability to minimum admin capability. See #3052.

#3 @johnjamesjacoby
3 years ago

In 6281:

Tools: Separate wp_usermeta clean-up from database upgrade routines.

Clean-up should be run after upgrades, not during. This way all results can be verified by the admin.

See #3052.

#4 @johnjamesjacoby
3 years ago

In 6282:

Tools: Break tools.php up into separate files. See #3052.

Note: See TracTickets for help on using tickets.