Ticket #2004 (closed defect: fixed)

Opened 3 years ago

Last modified 5 months ago

Pages page should page

Reported by: matt Assigned to: hailin
Priority: normal Milestone: 2.6
Component: Administration Version: 2.0
Severity: normal Keywords: needs-patch
Cc:

Description

For people that have > 100 pages listing them all doesn't make much sense. We should improve this by offering paging for more than 50 and also search.

Attachments

pages page should page proof.patch (13.1 kB) - added by Jairus on 04/09/08 16:50:52.
dirty proof-of-concept for paging on wp 2.3

Change History

02/12/06 05:41:54 changed by markjaquith

  • keywords set to bg|needs-patch.

03/23/06 16:08:00 changed by robmiller

This would be pretty complex in terms of the hierarchy - wouldn't you end up having to generate the full hierarchy then chop the list down to the first X entries?

If the consideration is screen space, then perhaps some kind of tree view might be better?

11/29/06 23:14:07 changed by matt

  • milestone changed from 2.1 to 2.2.

03/27/07 20:01:31 changed by foolswisdom

  • keywords changed from bg|needs-patch to needs-patch.
  • milestone changed from 2.2 to 2.4.

08/05/07 11:56:35 changed by leonid

There is a Search Pages plugin which seems to work just fine for searching, not paging though. http://www.internetofficer.com/wordpress/search-pages/

01/08/08 00:31:35 changed by thee17

  • keywords changed from needs-patch to needs-patch old-inactive-9mos-ticket.

02/12/08 09:07:07 changed by pishmishy

  • milestone changed from 2.5 to 2.6.

Bumping milestone for feature freeze.

03/30/08 11:03:52 changed by Nazgul

  • status changed from new to closed.
  • resolution set to wontfix.
  • milestone deleted.

No traction in almost 2 years, so closing as wontfix.

Feel free to re-open if you have additional information/patches/suggestions/...

03/31/08 16:39:53 changed by lloydbudd

  • keywords changed from needs-patch old-inactive-9mos-ticket to needs-patch.
  • status changed from closed to reopened.
  • resolution deleted.
  • milestone set to 2.6.

Re-opening, this is a bad experience issue for people with a large number of pages, because the page can take a long time to load.

As more people adopt WP as a general purpose CMS, it will likely soon become more urgent.

I understand that pages having children pages makes this a potentially challenging problem.

(follow-up: ↓ 11 ) 04/03/08 11:22:56 changed by Denis-de-Bernardy

+1 to the tree view idea

(in reply to: ↑ 10 ) 04/03/08 14:55:28 changed by Jairus

A collapsible tree view (like pageMash) doesn't necessarily address the scaling issue, even if it addresses usability concerns. (You could theoretically use something like an AJAX tree which only requests data about branches as they're opened, but that won't solve problems for installs with large numbers of pages at the root level.)

From a UI point of view, page hierarchy complicates things for the user, if they have a large number of pages paginated, and they're trying to find a specific item. I think the ideal solution would allow for both a flattened view (ie: sortable title/id/date columns) and a nested view that displays parent/child relationships (kind of like the current interface).

04/03/08 17:33:37 changed by lloydbudd

Relates to #6561

04/09/08 16:50:52 changed by Jairus

  • attachment pages page should page proof.patch added.

dirty proof-of-concept for paging on wp 2.3

04/09/08 16:55:56 changed by Jairus

A student here wrote up a quick-and-dirty proof of concept for paging the 'manage pages' page on 2.3. It's very rough around the edges and needs a lot of work (it doesn't display parent/child information), but it'll display 'manage pages' in 5-10 seconds with 4000 pages in the db, instead of it taking 5-10 minutes.

04/14/08 16:05:32 changed by ryan

  • owner changed from anonymous to hailin.
  • status changed from reopened to new.

04/15/08 23:23:10 changed by hailin

  • status changed from new to assigned.

It appears that the idea "demand load the category list to manage thousands of categories" can be applied here.

However, currently that needs some improvement (see #6677) Once we have some test mileages on that idea and like it, we will design a good, long-term solution for this issue.

07/08/08 19:58:07 changed by ryan

  • status changed from assigned to closed.
  • resolution set to fixed.