#2841 closed enhancement (fixed)
Update "Repair Tools" screen to use a list table
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | 2.6 | Priority: | normal |
Severity: | normal | Version: | 2.1 |
Component: | Tools | Keywords: | commit |
Cc: |
Description
The "Repair Tools" screen is getting difficult to navigate with so many tools in there. Why don't we bring it up to speed with all that WordPress has to offer.
- Search
- Filters
- Columns & rows
- Bulk actions
- Single action links
Steps:
- Converting our existing UI
- Convert to
WP_List_Table
- Move feedback messages into tools vs. callback repair methods
Attachments (3)
Change History (15)
#2
@
10 years ago
Now would be a good time to add a "Last Ran" column and save a timestamp in the options table for each test. Would be interesting to see when each repair tool was used last. Could also keep a counter for each one too. Hmmmm.
#4
@
10 years ago
Can we add an id to the run links? At least for now so I can test the menu_order thing.
#7
@
10 years ago
Also can we add a data-nonce attribute to the links with an indiv nonce? That way they're right there for ease of use.
#10
in reply to:
↑ 1
@
9 years ago
Replying to johnjamesjacoby:
Todo: use a
WP_List_Table
subclass (which bbPress has avoided needing until now)
Replying to johnjamesjacoby:
Now would be a good time to add a "Last Ran" column and save a timestamp in the options table for each test. Would be interesting to see when each repair tool was used last. Could also keep a counter for each one too. Hmmmm.
Replying to tharsheblows:
Also can we add a data-nonce attribute to the links with an indiv nonce? That way they're right there for ease of use.
The above 3 items appear to be outstanding for this ticket @johnjamesjacoby Do you want to tackle these here for 2.6?
If not, we can move these to new tickets and mark this as fixed :)
In 5885: