Wordpress admin area plugin to manage my data in Excel-like way?

pkhunter

Hi. Love this tool. I've downloaded it and tried it with the jEditable, and it's such a stellar combination. I'm wondering, before I embark on writing a plugin myself, if there's a Wordpress admin area plugin to write all my posts/pages in this way?

Note that this is not like "Wp table reloaded" etc which are just to show tables on the user-facing website. I mean I want to enter all my data and edit it using DataTables, which is much nicer than Wordpress' original editing...too much back and forth clicking. I'd much rather edit everything in one go (DataTables + jEditable) in one place.

Secondly -- is there a limit to the number of rows that can be shown? Of course depends on a user's browser resources etc, but what's a recommended limit? I'd like to have all the records/posts loaded in one place and searchable. Sometimes this could be upwards of 15,000 posts. What's the recommendation here, load everything so the "Search" and sorting work, or can the search also pull in NEW data from the server (instead of what's already available in the grid on the client side)?

Thanks!

allan

> I'm wondering, before I embark on writing a plugin myself, if there's a Wordpress admin area plugin to write all my posts/pages in this way?

As far as I am aware, you would be the first to embark upon such a mission :-).

> Secondly -- is there a limit to the number of rows that can be shown?

No - however as you say you need to consider the browser - the more records there are, the more you are asking it to do (particularly for sorting, filtering etc). These are my typical guidelines:

1. DOM sourced data, or Ajax sourced without deferred rendering: ~5000 rows
2. Ajax sourced (or JS array) with deferred rendering: ~15000 rows
3. >15000 rows, use server-side processing which will cope with millions no problem (since its up to the server to handle the heavy work and SQl engines are designed for exactly this sort of thing).

Allan

allan

One other thing - also consider your target browser platform - Chrome etc will cope with an order of magnitude more rows in client-side processing than IE8 for example and several orders of magnitude more than IE6...

Allan