Textpattern CMS support forum
#981 2012-03-25 19:45:44
- From: Germany
- Registered: 2005-01-20
- Posts: 2,561
:-) yeah, some threads have grown insanely long. The primary advantage – aside from being able to have more than 10 custom fields (which you access with the normal
txp:custom_field tag) – is the ability to make custom fields appear as other kinds of fields on the write tab and the ability to pre-populate the available choices … as described in the opening post. There’s one aspect not shown in the screenshots, and that is the ability to have your select box driven by a custom script of your own making (examples are provided) that pulls in data from elsewhere in the database.
I’ve only rarely accessed the google group, but the fee really is very reasonable and you need only pay once.
TXP Builders – finely-crafted code, design and txp
#982 2012-03-25 23:15:12
- From: Cologne
- Registered: 2006-08-15
- Posts: 3,882
- more than 10 custom fields can be set and used
The true value of this plugin is not the 10+ text input fields but the ease of use you permit to your clients by letting them click checkboxes and radio buttons, let them choose from predefined dropdown menus and select lists, enter dates via clickable calendars and times from preset menus.
Instead of the old error prone way of letting them enter these values by hand. Into 10+ good old TXP text input fields.
But if it’s just about these 10+ fields then TXP has all you need and you don’t have to buy anything. You just need some boldness and knowledge to run the right MySQL queries (and maybe G-translate).
- contributors (i.e. paid users) have to subscribe to the dedicated Google group to get new versions
As far as I can remember you get access/the plugin by mail as soon as Gerhard has received your payment. The Google group serves only as a “counter” for feature ideas and as bug tracker (again: AFAICT).
- is the link to contribute, in the first post, still valid ?
I assume that people that have subscribed here have used the link ages ago ;) (you pay once for a lifetime).
#983 2012-03-26 07:30:51
Thanks Jakob and Uli.
It was so obvious that custom fields can be used as checkboxes or radio sets – too obvious – that I forgot to mention it. It’s done now.
I’m convinced that the fee is worth it, and is even extremely low considering the work done. All I want is to ensure that the plugin will suit my needs.
So, what are these needs ?:)
Basically, I’d like to perform searches on custom fields (and-searches on absolute values and ranges).
Admin-side checkboxes and radio buttons are a plus.
Continue reading the last ~50 pages now :) I’m pretty sure answers are in them.
#984 2012-03-26 07:43:54
- Core designer
- From: Farnham, Surrey, UK
- Registered: 2009-06-11
- Posts: 2,678
Gerhard is responsive on twitter if you need to ask him a question directly in 140 characters: @gerhardlazu
#985 2012-03-26 08:16:21
#986 2012-03-26 08:50:21
tye a écrit:
Its well worth it Claire, takes txp to another level wet_haystack plugin can do searches in custom fields
Okay, I’ll explain a little bit more.
My searches would be performed on custom fields only, somehow like in the beginnings of glz_custom_fieds.
More exactly, it would look like this:
- show custom fieds on front-end like they are shown on back-end
- let the user making his choices
- select relevant articles with smd_if
(Still 25 pages to read)
#987 2012-03-26 09:41:34
- From: Leeds, UK
- Registered: 2006-01-29
- Posts: 7,585
show custom fieds on front-end like they are shown on back-end
Not wishing to fiddle Gerhard out of cash here — I’m not a massive user of this plugin so don’t take my word as gospel — but I don’t know if the plugin has a tag to output the names of the custom fields. You might have to resort to looking at the prefs table for
custom_n_set entries and iterate over them. Same applies to rendering input elements:
<txp:custom_field name="whatever" /> will render the contents, but not an input tag. Whether the plugin has the ability to render widgets for the various types of input control (or whether you can write a script that hooks into the plugin to do it) I don’t know. I’ve done this kind of ‘widget rendering’ thing in smd_bio v0.40 so if glz_cf doesn’t do it and you need to resort to PHP, you can always go look there for some copy/paste love :-)
select relevant articles with smd_if
That may be slow, depending on the number of articles that you are iterating over. I’d be tempted to use smd_query for this. Sanitize the input using that plugin’s filtering capabilities (or do it manually with a lick of PHP) and then throw the sanitized
$_POST params at the plugin to do its stuff and return a list of matching articles.
It’s not as simple as iterating over
<txp:article_custom>, especially if you have checkboxes, because you probably have to construct the query based on which items have user data in them. And HTML will omit checkbox data from the incoming stream, which may complicate things. But it’s doable, you have more control over the type of matches and is much faster as the site grows: I’ve seen it done on estate agent websites where people can do custom searches on price ranges, location, etc.
Last edited by Bloke (2012-03-26 09:42:54)
#988 2012-03-26 14:19:04
Bloke a écrit:
smd_bio […] you can always go look there for some copy/paste love :-)
I’d be tempted to use smd_query for this.
Thanks a lot for your precious (as usual) advices!
#989 2012-04-14 14:58:08
- From: Reykjavik, Iceland
- Registered: 2005-11-25
- Posts: 1,087
I haven’t done much website work lately and I have a couple of quick questions…
- I have version 1.3. Is that the current one?
- What happens to the content of my current fields when I change them to e.g. text area?
#990 2012-05-04 15:23:13
- From: Argentina
- Registered: 2009-04-20
- Posts: 401
I’d like to know how apply the plugin hak_tinymce in an especific textarea created with glz_custom_fields.
I use “custom-12” for this textarea element.
Does anyone know how to do ?
Thanks a lot