Closed GoogleCodeExporter closed 9 years ago
Thanks for the kind words! Yeah, I'm really trying to make this thing put WP
on the map as a CMS and take over some of the crufty plugins out there that
cause so many headaches (e.g. eCommerce plugins). I'm bummed that problems
with the WP repo caused some headaches for early adopters of the plugin, so it
got some bad ratings, but I think all that repo stuff has been ironed out --
still lots to do before version 1 though. I'm guessing that realistically
there probably are 800+ active users, and that's not too bad. I'm hoping the
import/export feature will help get the word out and make it easy for people to
share what they're doing with their sites.
Yes, I've been stroking my beard on how to best handle custom formatting of the
entire post edit/create pages, including the "Custom Field" meta box wrapper...
there are a couple other tickets related to formatting that I'd like to address
at the same time (e.g. issue 53, 65, and issue 34). I'm merging this issue
into number 34 to help me keep the requests organized.
Here's what I'm thinking (your comments are welcome):
1. Fix issue 65 so users can provide custom templates again using
[+placeholders+] for various form components. I want to avoid having users
write any PHP code. The MODx-stuff chunk formatting is brilliant for this
stuff... so you could do something like <div id="my_id">[+my_field_here+]</div>
or get more granular with [+my_field.label+], etc.
2. Add an attribute for each custom field definition that would describe which
meta box it belonged to. The default one would be the standard "Custom
Fields". I'm guessing that this would require another menu item that would
allow users to manage different types of meta boxes... define whether they
display below the post or on the right-hand column, and I think WP 3.1.1 now
has that hidden control @ the top of the page that allows you to show/hide
various meta boxes. Or... perhaps more simply, just a checkbox that would
determine if the custom field displays in its own meta box or not. That would
be much easier to export.
3. Provide another template that describes each meta box. This would allow you
to format the "Custom Fields" meta box, for example... use your own html and
labels, etc.
Original comment by fireproofsocks
on 27 Apr 2011 at 2:50
2. As for the interface part, I would suggest taking a look at More Fields
plugin for inspiration.
Original comment by mamoun.d...@gmail.com
on 27 Apr 2011 at 11:02
In short, More Fields way to handle it is to provide them in two-level. To add
any custom field, you SHOULD first have at least one meta-box. So you first add
meta-box, configuring some options for it like its label, and then add as many
custom fields as you want inside it.
Original comment by mamoun.d...@gmail.com
on 27 Apr 2011 at 11:06
Thanks, that answers my question. That is a better architecture because it
normalizes the meta box data. I just have to figure out the best way to store
that data...
Original comment by fireproofsocks
on 27 Apr 2011 at 11:55
Original issue reported on code.google.com by
mamoun.d...@gmail.com
on 27 Apr 2011 at 2:25