glz_custom_fields

radneck · 2010-11-09 02:07:13

eric2007 wrote:

Are there any issues with glz_custom_fields in the 4.3.0 RC that just came out?

I’ve been using the 4.3.0 RC and everything seems fine.

alanfluff · 2010-11-09 12:44:27

@ eric2007 Apologies, I’m sure you know this, but just in case you missed it (as I did), 4.3.0 is fully released now :)

alanfluff · 2010-11-10 17:44:33

Hi Gerhard/folks,

I am not sure where to post this, here or in an official 4.3.0 feedback page¹, but I’ll start here.

I am finding that a custom field of type ‘checkbox’, with multiple checkboxes, has presentational ‘lumps’ where it didn’t in 4.2.0.

It appears that it is not theme related.

It appears subtly different in Ffox Vs. Safari, but broken looking in both.

The problem is whitespace and/or alignment between checkboxes and their labels, instead of stacking up nicely, a label is spaced away from it’s checkbox, so the overall list takes up more space and the relationship between label and checkbox is less clear.

If there’s anything I can do to help solve this (I have a hammer and some nails, just no TXP-backend skills ;) — seriously, if a patch needs testing (of either part of glz_custom_fields or TXP 4.3.0), I would be happy to try it and report back.

Thanks again one and all for the superb developments happening in TXP-land.

Cheers, -Alan

¹ I’m guessing there is such a page/process, I’m just too much of a thicky to have fond it yet.

vurt · 2010-11-15 19:01:50

alanfluff wrote:

The problem is whitespace and/or alignment between checkboxes and their labels, instead of stacking up nicely, a label is spaced away from it’s checkbox, so the overall list takes up more space and the relationship between label and checkbox is less clear.

In http://path-to-txp/theme/your-theme/textpattern.css

I added this at bottom:

td#article-col-1 #advanced .glz_custom_checkbox_field span input{width:auto;}

Admittedly a quick fix, should probably be in its own theme or it will be overwritten in updates.

alanfluff · 2010-11-15 19:10:45

vurt,

You’re a STAR :D

Thank you! For me, I think as I had used bot_wtc to re-arrange the write page, I had to loose the #advanced, but that aside, it worked a treat!

And as I use my own theme — it’s a permanent fix too! Brilliant (I do feel a bit CSS-embarrassed though for not thinking of trying something like that — I think I was just bamboozled by all the newness and loveliness of 4.3.0.

Cheers!, -Alan

vurt · 2010-11-15 22:22:59

Glad I could help!

brunodario · 2010-11-29 16:51:21

Is there a way to control the output? Say, if i want to output each marked value of a radio custom field inside a <li> tag?

Example: I have custom fields with color names (white, brown, yellow) and the output it´s white | brown | yellow. I´d like it to be <li>white</li> <li>brown</li> <li>yellow</li>

wornout · 2010-11-29 17:02:56

You can use smd_each or rah_repeat for your purposes!

brunodario · 2010-11-29 17:47:43

wornout,

Great regexp plugins!

<txp:rah_repeat wraptag="ul" break="li" value='<txp:custom_field name="colors"/>' delimiter="|"> Cor <txp:rah_repeat_value />. </txp:rah_repeat>

Did the trick. Thx!

babyben · 2010-12-02 13:56:30

Edit: D’oh. Asked a question, and should have read the Textbook first. Answer was staring me in the face!

Last edited by babyben (2010-12-02 14:11:26)

phuture303 · 2010-12-31 15:53:53

Hello there,

just a simple question (I’m testing possibilities on a fresh install :-)

I’m using glz_custom_fields and the delivered script “my_images.php”. My customfield #2 (named “custom2”) shows the name of all images in a dropdown as it should, everything’s all right till here.

<txp:custom_field name="custom2" />

placed as a tag in an article publishes the id of the selected image (“2” in my case). Okay.

<txp:image id="2" />

shows the right image as it should (“txp_slug105x45.gif”). Normal. And fine :-)

But in combination:

<txp:image id='<txp:custom_field name="custom2" />' />

doesn’t work. Am I doing something stupidly wrong? Thanks for help :-)

Have a nice 2011!
David

UPDATE

Problem solved for myself:

notextile. <txp:image id='<txp:custom_field name="custom2" />' />

It seems that textile doesn’t like the phrase. But why’s that?

Last edited by phuture303 (2010-12-31 15:55:24)

alanfluff · 2010-12-31 16:16:04

Hi David,

It seems that textile doesn’t like the phrase. But why’s that?

I’m not sure why in this case this was necessary, but I think as a general rule-of-thumb it’s a good idea not to have (or allow) Textile to parse TXP code. When you do, you are relying on Textile being clever enough to work out when to ignore and when to parse, so regardless of how clever Textile is at that, it’s safer to simply not have it parse TXP code.

As noted, I may be wrong or partially wrong here, apologies if so and anyone who know’s different, please shout out so I can learn too :) Thanks!

Cheers, -Alan

Textpattern CMS

Textpattern CMS support forum

#745 2010-11-09 02:07:13

Re: glz_custom_fields

#746 2010-11-09 12:44:27

Re: glz_custom_fields

#747 2010-11-10 17:44:33

Re: glz_custom_fields

#748 2010-11-15 19:01:50

Re: glz_custom_fields

#749 2010-11-15 19:10:45

Re: glz_custom_fields

#750 2010-11-15 22:22:59

Re: glz_custom_fields

#751 2010-11-29 16:51:21

Re: glz_custom_fields

#752 2010-11-29 17:02:56

Re: glz_custom_fields

#753 2010-11-29 17:47:43

Re: glz_custom_fields

#754 2010-12-02 13:56:30

Re: glz_custom_fields

#755 2010-12-31 15:53:53

Re: glz_custom_fields

#756 2010-12-31 16:16:04

Re: glz_custom_fields

Board footer