[solved x 2] tricky problem: format article custom fields into a table

mrdale · 2012-07-03 18:07:18

TXP Freakin Geniuses start your engines.

I want to turn the following articles…

title:article A / cf_vintage:2007 / cf_release:syrah / cf_action:dump

title:article B / cf_vintage:2007 / cf_release:merlot / cf_action:hold

title:article C / cf_vintage:2007 / cf_release:viognier / cf_action:dump

title:article D / cf_vintage:2008 / cf_release:merlot / cf_action:drink-hold

title:article E / cf_vintage:2008 / cf_release:syrah / cf_action:hold

title:article F / cf_vintage:2006 / cf_release:syrah / cf_action:drink

title:article G / cf_vintage:2008 / cf_release:viognier / cf_action:drink

title:article H / cf_vintage:2009 / cf_release:viognier / cf_action:drink

into the following table.

Release 2006 2007 2008 2009

merlot - hold drink-hold -

syrah drink dump hold -

viognier - dump drink drink

the difficulty is that not every vintage has every release, so it’s hard to format empty cells.

Last edited by mrdale (2012-07-12 06:12:17)

els · 2012-07-03 20:46:30

Very nice :) Having a go at it now (but don’t hold your breath…)

milosevic · 2012-07-03 21:14:02

Perhaps this will fit your requirement. Not sure if I understand 100% your requirements:

<td>
<txp:custom_field name="cf_release"/>
</td>
<td>
<txp:if_custom_field name="cf_vintage" value="2006">
<txp:custom_field name="cf_action"/>
<txp:else/>-</txp:if_custom_field>
</td>
<td>
<txp:if_custom_field name="cf_vintage" value="2007">
<txp:custom_field name="cf_action"/>
<txp:else/>-</txp:if_custom_field>
</td>
<td>
<txp:if_custom_field name="cf_vintage" value="2008">
<txp:custom_field name="cf_action"/>
<txp:else/>-</txp:if_custom_field>
</td>
<td>
<txp:if_custom_field name="cf_vintage" value="2009">
<txp:custom_field name="cf_action"/>
<txp:else/>-</txp:if_custom_field>
</td>

mrdale · 2012-07-03 21:28:36

almost, but the vintages are dynamic.

els · 2012-07-03 21:38:18

mrdale wrote:

almost, but the vintages are dynamic.

I think we need (a lot of) variables. (Still trying… not quite there yet.)

mrdale · 2012-07-03 21:41:48

or a lot of nesting… also working.

els · 2012-07-03 22:16:48

If the vintages are dynamic, the number of columns can vary, right? So you could have four columns, or twenty, or whatever. The table head can be done, but I don’t see a way to determine the number of cells needed for the content. I suppose you can’t use a custom field for each vintage?

mrdale · 2012-07-03 23:59:15

your assumptions are correct. I think I’m closing in on it tho.

mrdale · 2012-07-04 03:50:38

OK, I did it, but I discovered that my old standby chh_if_data doesn’t work inside smd_each

Mighty chuffed… (requires smd_each)… see the solution here»

Last edited by mrdale (2012-07-04 04:05:59)

els · 2012-07-04 07:30:21

mrdale wrote:

Mighty chuffed… (requires smd_each)… see the solution here»

Nice! I really like this kind of tag use :) I was halfway there last night, trying to do it without plugins. But I don’t think that is possible ;)

colak · 2012-07-04 08:49:35

I was wondering if <txp:chh_if_data> could be replaced with <txp:if_custom_field name="wine_cellaring">

uli · 2012-07-04 13:22:09

There’s one thing that makes my wires melt (I just “beautified” the code to make it more readable):

<txp:variable name="vintages">
  <txp:custom_field name="wine_vintage" />
  <txp:if_first_article>
  <txp:else/>
    ,
  </txp:if_first_article>
  <txp:variable name="vintages" />
</txp:variable>

Why you put the variable inside itself, what is its content after doing so?

maniqui · 2012-07-04 13:29:57

Uli, he adds the variable to itself, at the same time it adds the value of the custom field, making a list of values.
If the first value of the variable is “dog”, and then the custom field value is “cat”, the variable will end up being “cat, dog”. On each iteration (over textpattern articles), the variable gets a new value.

uli · 2012-07-04 14:07:04

Ah, thanks, Julián, didn’t know that you can do that with a variable, thought it’d lead to a short circuit.

And b) had forgotten we’re in an article_custom loop, thus it isn’t the only call of this variable.

towndock · 2012-07-04 16:30:52

A glass of 2007 Malbec would make it all seem better.

Textpattern CMS

Textpattern CMS support forum

#1 2012-07-03 18:07:18

[solved x 2] tricky problem: format article custom fields into a table

#2 2012-07-03 20:46:30

Re: [solved x 2] tricky problem: format article custom fields into a table

#3 2012-07-03 21:14:02

Re: [solved x 2] tricky problem: format article custom fields into a table

#4 2012-07-03 21:28:36

Re: [solved x 2] tricky problem: format article custom fields into a table

#5 2012-07-03 21:38:18

Re: [solved x 2] tricky problem: format article custom fields into a table

#6 2012-07-03 21:41:48

Re: [solved x 2] tricky problem: format article custom fields into a table

#7 2012-07-03 22:16:48

Re: [solved x 2] tricky problem: format article custom fields into a table

#8 2012-07-03 23:59:15

Re: [solved x 2] tricky problem: format article custom fields into a table

#9 2012-07-04 03:50:38

Re: [solved x 2] tricky problem: format article custom fields into a table

#10 2012-07-04 07:30:21

Re: [solved x 2] tricky problem: format article custom fields into a table

#11 2012-07-04 08:49:35

Re: [solved x 2] tricky problem: format article custom fields into a table

#12 2012-07-04 13:22:09

Re: [solved x 2] tricky problem: format article custom fields into a table

#13 2012-07-04 13:29:57

Re: [solved x 2] tricky problem: format article custom fields into a table

#14 2012-07-04 14:07:04

Re: [solved x 2] tricky problem: format article custom fields into a table

#15 2012-07-04 16:30:52

Re: [solved x 2] tricky problem: format article custom fields into a table

Board footer

Release	2006	2007	2008	2009
merlot	-	hold	drink-hold	-
syrah	drink	dump	hold	-
viognier	-	dump	drink	drink