Improve Data Presentation in admin for CPTs

[neverything]

We are working on this from the contributor day of WordCamp Switzerland 2014 today.

Meta information The basic idea is to improve the data presentation in the backend to show meta information. In a similar way the CampTix plugin does (see screenshot).

Term metaboxes Additionally we should remove the term metaboxes from the admin, but still display the information.

[JulioPotier]

I'm on it #WCEU2014

[neverything]

@BoiteAWeb thank you! Again sorry, I abandoned the ticket.

[JulioPotier]

Something like this? (dummy data)

[JDGrimes]

@BoiteAWeb — That looks nice.

[DrewAPicture]

I don't think this is something that belongs in wp-parser. It would be a great plugin but the parser itself shouldn't be dictating the admin UI of site holding the resulting parsed data outside of the basic meta boxes/UI generated by WordPress core.

[JulioPotier]

@DrewAPicture Why not, but so, do we have to hide (show_ui=false) the taxonomies by default or not? The goal is to avoid the possible edition within the edition pages.

[DrewAPicture]

IIRC the post type definitions as such can be overridden by, say, a theme or other plugin. Not sure I'm following you on "edition pages".

[JulioPotier]

here http://dl.dropbox.com/u/45956904/screenshots/baw_140929-202808.jpg

[DrewAPicture]

OK. Well again, the parser serves to parse and organize the data and nothing more. It's a utility.

This is clearly plugin/theme material.

Edit: I realize I may be coming across a bit bluntly. I really like these data presentation ideas, I just don't think there should be any aesthetic connection between the parser and the site that the parser is populating. That's what a theme or separate plugin is for.

[JDGrimes]

#14 has some similar discussion.

Also, the API may be too unstable for this yet. This is the kind of stuff I'd really like to see, but it probably should wait until the parser is more mature.

[JulioPotier]

@DrewAPicture No worry, i finally agree, i did this during the contributor day in Sofia 2014, so, this was my task. I can export this as a plugin, no problem with that.
Thanks
@JDGrimes ok seems legit too

[Rarst]

I totally think this should be in Parser in some form. Lack of data visibility is one of the most annoying workflow issues with data-heavy projects. I consider it absolutely necessary.

So on points voiced, my take is:

1. Should be in Parser, not separate.
2. Maybe a little towards bland/generic UI, keep it close to core.
3. Should be reasonably flexible so people can adjust or extend it for their Parser needs (not necessarily for initial implementation, we could take care of that later).

[atimmer]

I think something like this should be in parser, maybe just very basic. Like just looping through all meta fields starting with "_wp-parser", unpacking the serialised values and displaying them.

I think this should be easily overridable for other project, but if you do it correctly a remove_meta_box is all that should be needed.

@BoiteAWeb Can you throw this code up on a fork so work can continue on this?

[JulioPotier]

Yes, i would like to finish this, can someone give me some SQL export for all kind of data? I couldn't parse this by myself at Sofia :/

[Rarst]

Sorry, I let this slip away from me. :(

I vaguely remember someone was going to send @BoiteAWeb that export? Are you still interested in the issue?

At the moment I take over this, unless someone has significant chunk done and doesn't want it go to waste.

[atimmer]

I send @BoiteAWeb the export and he confirmed that he received it and could import it.