I think you are hinting here at trigger words, same thing as with ranges. This is very interesting from a programming point of view, it got me all excited : ). It’s definitely doable and has already been included on the new features list. The functionality that you are talking about here will be known as |Image Categories| (so that we know it’s a trigger expression).
this sounds excellent! my donation has been sent :) in the meantime i’m going to think about what other tasty treats could be thrown into the mix.
- Registered: 2007-02-08
- Posts: 55
Brilliant Gerhard! Thanks for developing this. There’s a million and one ways I can imagine this being useful.
I had managed to cobble together a way of doing this using new functions in
txp_article.php, and mod the database to make custom fields searchable, but it was never, ever going to be as slick as this!
Expect a tenner from me soon.
PS. recently put together a list/review of my top ten TXP plugins, now I have to start again from scratch!
Last edited by kevinmcdougall (2007-09-17 11:02:03)
I’m currently using rss_thumbpop for a site and the way its set up, the user has to manually type an image category name into a custom field, and then the plugin takes that image category name to output a specific gallery for that article.
Have you ever tried using asy_wondertag to automatically feed attribute values to rss_thumbpop. I’ve used it several times, works like a charm. The key is using identical image and article category names where appropriate. Of course it would be nice to have content-independent categories (ala xPattern) for just this purpose.
Another one: what about using this for keywords? In a multiple-authors website, it’s easy to misspell keywords. If I write a Texpattern article on a blog, what’s his keyword: textpattern, Textpattern, TXP? And there’s the possibility of typos. So when the article’s keywords area is selected, the user would have an (alphabetically sorted) overlay of existing keyword. He can click to the ones he wants, or add his new ones (that will be displayed for the next use of this functionality).
this can already be done with tru_tags if that’s any help
- Plugin Author
- Registered: 2005-03-12
- Posts: 1,253
Yup, this is a great plugin, covering a functionality we’ve waited for several long years. Well done Gerhard!
Another suggestion: local, context, explanations (micro documentation). From the user point of view, maybe he has a Help button for each custom field, or an overlay that appear when he select this specific custom field area. Of course, the webmaster would have to write the micro-documentation (probably at the same stage as setting up the custom field and choices themselves).
I would love to see this as well. For instance, I have an IA that would break, if someone would enter the wrong custom_field values in the wrong fields. Custom field names on this install are mostly IA specific, and don’t give the User a clue, which custom_fields have to be populated, and with which data, if there is not a detailed custom made client manual.On one section, specific fields are used, while others have to remain emty, on another section other fields are used, and so on.
As I can see from Gerhard’s notes, section specific custom fields are on the roadmap for version 2.
How about this one ?
⌃ ⇧ < ⎋ ⌃ ⇧ >
- Plugin Author
- Registered: 2006-12-07
- Posts: 108
* help in multiple languages (any translators wanting to offer for this?)
I could help out with a German translation.
- Plugin Author
- From: Kansas, USA
- Registered: 2004-02-29
- Posts: 482
Gerhard, you might want to be more specific in your original post about exactly how people can go about paying you for this miraculous plugin. ;-)
(Yes, I found it. I just don’t want anyone else to have to hunt.)
I don’t have use for this myself just yet, but I recently wrapped up work with a client that may need exactly what you’ve done as their site expands. Good stuff.
- From: Madrid, Spain
- Registered: 2005-09-19
- Posts: 375
Good work, nice plugin! If you need spanish translation, I can do it.
how I can obtain the value of checbox that comprises of custom_1_set. For example, if custom Set has 4 checkbox and is 2 checked, how I obtain the value of each one separately?
How it is used the tag conditional for custom fields for custom set of checkbox?