You are not logged in.
What if. . . .
Think of this as glz_custom_fields, bot_cf_names, and bot_wtc rolled together and put on steroids.
I think it is safe to say that there is a general consensus that one of Txp’s great features is custom fields. There are a multitude of plugins whose job is to create additional database fields in one flavor or another — glz_custom_fields for the write tab, smd_bio (as well as a couple of others) for the user/authors tab, ign_users for an alternate user databse, smd_tags, tru_tags, and rss_unlimited_categories, just to name a few.
As of Textpattern 4.2.0 the ability to extend custom fields was enhanced. A few plugins have come out or been updated to leverage that.
I’m wondering if it can be taken further. A custom field plugin to rule them all . . . . ;-P
It is not unusual to run into a post on the forum hoping for, dreaming of, or asking for speciality custom fields. Custom fields for images, links, files, and most recently, sections. Sometimes there’s even a request for a plugin to add a whole new tab for specific content like videos or otherwise create entirely custom interfaces.
There is a CMS called Symphony that has some of the feeling of Txp, but lacks the polish of Txp, and is much more challenging to get your head around . . . or at least it has been for me. :)
They have a couple of ideas that I think are worth borrowing. One is what I’m going to call Data Templates. That’s what I’m wondering if we could create a plugin around.
The Proposed Solution
This plugin would:
It seems like we can pretty much do most of these things already – but it requires a number of plugins, hacks, customizations, etc. This plugin would simplify everything and create a single interface.
But, the first question needs to be: Is such a plugin possible with Textpattern? How close could we get? Second – Is there be enough interest in something like this to make it happen?
Okay – I’ll throw this out there for thoughts, critique, etc.
Last edited by maverick (2011-03-15 17:12:42)
Symphony CMS is impressive — powerful, elegant, and as extensible as a CMS could well be, in terms of content management. (Of course you have to learn XSLT to use it, the initial learning curve for the system itself is quite steep, and out of the box there is quite a bit of work to do to set up the framework for a custom site. But I digress.) I haven’t looked into it closely enough to really understand what’s going on behind the scenes, w/r/t database schema etc.
For another approach to extending content types, see Escher. The 0.9.0 release allows custom metadata and custom content fields for the Page content type, and the latest development version allows custom metadata fields for all content types. So, not as wide open as Symphony CMS, but very extensible.
Txp 5 will represent, at least, a move in the direction of this kind of extensibility. How much remains to be seen, but suffice it to say the days of never having to use
JOIN in a Txp query are coming to an end.
Symphony CMS is impressive
See also ProcessWire — I prefer it over Symphony so far, as it feels very easy to set up in comparison.
In fact, I’m using ProcessWire right now when I need features like those that Mike mentioned.
Last edited by maruchan (2011-03-15 19:47:46)
I agree with your dreaming – the process of shoe-horning data fields into articles is not ideal. I’ve had this requirement in the past but haven’t worked out the best way of achieving it. Separate database tables are great but they’re invisible to the standard search functionality – and you can’t use TXP tags to access the data. Custom fields can be given meaningful names but really they need to be viewed in a table. The closest I could come to an idea was to have a Multi-Article Write tab which displayed a number of articles’ custom fields in a table – so the user could see & edit all the data fields in one go.
Last edited by gomedia (2011-03-15 22:04:43)