glz_custom_fields

frickinmuck · 2012-03-18 21:08:07

I can’t get either of these approaches to work. Tye’s approach doesn’t seem to have any effect on the output – still comes up as a select menu. Dale, with yours I get the error:

“Ooops! list_clients() cannot be called. Ensure /html/scripts/glz_custom_fields/list_clients.php can be executed.”

Any ideas what could be going wrong? I’ve tried using this to change a pre-existing select menu into a multi-select, and I’ve also tried using it to set up an entirely new one from scratch, and neither approach is working.

EDIT: Never mind, I realized I hadn’t changed the name of your function to the one I was using. This is working now:

<?php
function list_clients($custom_field, $custom_id, $custom_value) {
  $titles = array();
  $query = safe_rows('name, title', 'txp_category', "parent like 'client'");
  $titles[] = '&nbsp;';
  foreach ($query as $title) 
    $titles[$title['name']] = $title['title'];
  return glz_selectInput($custom_field, $custom_id, $titles, $custom_value, "2", true);
}
?>

Thanks so much for your help, guys!

Last edited by frickinmuck (2012-03-18 21:11:49)

frickinmuck · 2012-03-18 21:37:49

I just have one last question. How do I get it to separate the items differently in the database? Right now this:

<?php
function list_clients($custom_field, $custom_id, $custom_value) {
  $titles = array();
  $query = safe_rows('name, title', 'txp_category', "parent like 'client'");
  $titles[] = ' &nbsp; ';
  foreach ($query as $title) 
    $titles[$title['title']] = $title['title'];
  return glz_selectInput($custom_field, $custom_id, $titles, $custom_value, "2", true);
}
?>

Results in something that looks like this: First Client Name|Second Client Name|Third Client Name, and I’d like to be: First Client Name, Second Client Name, Third Client Name. Any ideas?

uli · 2012-03-18 22:16:12

frickinmuck wrote:

First Client Name|Second Client Name|Third Client Name

That’s the contents of your custom field, and you need to output it somewhere, right? In that case I’d resort to one of our Swiss army k…atalyzers, rah_replace or smd_wrap.

frickinmuck · 2012-03-18 22:30:01

Yeah, I guess I can use rah_replace, but I was hoping there would be a way to achieve this from the outset. i.e. separate the categories being input into the custom field with something other than the | with no spaces around it. Something about having them entered that way in the db bugs me.

Last edited by frickinmuck (2012-03-18 22:30:27)

jakob · 2012-03-19 07:15:36

That’s the way it comes out of glz_custom_fields rather than out of the db so you’d likely have to edit the plugin to get different output.

If you already have code setup to work with a comma-separated list, you can convert it to a comma-separated txp:variable using what Uli said and plug that variable into your code. Alternatively rah_repeat and smd_each can also process each item without pre-converting to commas.

CeBe · 2012-03-25 17:06:23

I’ve been reading the 50 first pages of this thread this afternoon, trying to figure out what the plugin does and what it doesn’t. Nearly 48 pages left and probably other answers in them, but this is what I understood so far, and what I still wonder :

it is a back-end plugin and there’s no front-end tag provided (though it used to)
more than 10 custom fields can be set and used ; edit: not only as text fields but also as radio sets, checkboxes
contributors (i.e. paid users) have to subscribe to the dedicated Google group to get new versions
is the link to contribute, in the first post, still valid ?

Thank you !

Last edited by CeBe (2012-03-26 07:09:14)

jakob · 2012-03-25 19:45:44

:-) 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.

uli · 2012-03-25 23:15:12

CeBe wrote:

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).

CeBe · 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.

philwareham · 2012-03-26 07:43:54

Gerhard is responsive on twitter if you need to ask him a question directly in 140 characters: @gerhardlazu

tye · 2012-03-26 08:16:21

Its well worth it Claire, takes txp to another level wet_haystack plugin can do searches in custom fields

CeBe · 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)

Textpattern CMS

Textpattern CMS support forum

#961 2012-03-18 21:08:07

Re: glz_custom_fields

#962 2012-03-18 21:37:49

Re: glz_custom_fields

#963 2012-03-18 22:16:12

Re: glz_custom_fields

#964 2012-03-18 22:30:01

Re: glz_custom_fields

#965 2012-03-19 07:15:36

Re: glz_custom_fields

#966 2012-03-25 17:06:23

Re: glz_custom_fields

#967 2012-03-25 19:45:44

Re: glz_custom_fields

#968 2012-03-25 23:15:12

Re: glz_custom_fields

#969 2012-03-26 07:30:51

Re: glz_custom_fields

#970 2012-03-26 07:43:54

Re: glz_custom_fields

#971 2012-03-26 08:16:21

Re: glz_custom_fields

#972 2012-03-26 08:50:21

Re: glz_custom_fields

Board footer