Support Forum

Logoleptic · Tweet

I think I might have use for this, but I’m not sure. I’m currently using two custom fields to hold “tasks” for projects in my portfolio (e.g. “Search engine optimization and submission”). These tasks end up in an unordered list that goes into a definition list for each project on the main portfolio page and at the bottom of every individual portfolio article.

Right now I’m just dumping raw HTML into these custom fields, since there’s not any structured way to do it. I’ll probably have to continue using two fields, but I’m wondering if this plugin might give me a way to let visitors filter my portfolio by specific tasks. Is this possible, or am I really looking for more of a tagging plugin?

nabrown78 · Tweet

This plugin looks like it might solve my too-few-custom-fields problem. For anyone that has used it, have you noticed any glitches or performance issues?
Thanks.

sparkybarkalot · Tweet

I’m running TXP 4.0.5 and sed_pcf_if_value is failing on me. I’m getting errors saying that ‘custom’, ‘section’, and ‘variable’ aren’t attributes of sed_pcf_if_value. I’ve triple checked my tag code, even copying and pasting the code directly from this thread in case I was misyping something, but still getting those errors.

Anyone else having this problem and / or have any suggestions?

Thanks for a really, really nice plugin.

net-carver · Tweet

All

version 0.3 is available.

It adds the sed_pcf_for_each_value tag which acts as an iterator over a CSV field. It’s based on wet_for_each_image so if you know how powerful that is you’ll see the advantage of the new tag.

Available from the download page in normal and compressed formats.

pieman · Tweet

Hello

Would I be right to say that you can only retrieve values associated with pre-defined names using this plugin?

I’ve already posted what I’m trying to achieve here, but the crux of it is that my ‘names’ can’t be set beforehand, and I’d like to output both these variable ‘names’ and associated values in a definition list.

thanks
Stu

net-carver · Tweet

Stuart

Sorry, it doesn’t currently do what you want — it only gets/tests data via a known name.

I’ll think about putting an iterator in for name-value pairs that will operate in a similar way to the new sed_pcf_for_each_value tag.

pieman · Tweet

OK, thanks anyway. If you find the time to add that later I’d find it really useful.

pieman · Tweet

Hello Steve

I abandoned the previous search, but I have a new problem! I’m trying to use sed_pcf_for_each_value, but so far I’ve not been able to output anything.

I have an article which contains 4 valid article IDs in a custom field called related-article-IDs. In my article form I have

<txp:sed_pcf_for_each_value name="related-article-IDs"><txp:article_custom id="{value}" form="article_nav" /></txp:sed_pcf_for_each_value>

and in the article_nav form
<li><a rel="bookmark" title="read full article" href="<txp:permlink />"><txp:title /></a></li>

One thing I’m not sure of in the help, is that for sed_pcf_for_each_value you specify an attribute called ‘name’ to hold the custom field to access, whereas in the other tags you’ve used ‘custom’ as the attribute. Is that deliberate? I’ve tried both just incase, but no luck yet.

Hopefully I’m doing something obviously wrong. Any help appreciated.

cheers
Stu

ps. there’s a typo there too:
3. As an enclosing tag… <txp:sed_pcf_for_each_value>... your stuff here...<txp:sed_pcf_for_each_value />
the trailing slash should be at the start of the closing tag I think…

pieman · Tweet

I should point out a couple of things

the custom field holds a simple, comma separated string 16,18,20,21
the txp:sed_pcf_for_each_value code isn’t written an article form, but pulled from another form which is called with the txp:output_form tag, so I don’t think it’s an issue with articles within articles. I’ll investigate this further though just incase

Bloke · Tweet

Steve

Only just got round to trying this excellent plugin out. I was getting close to running out of custom fields and this has saved the day, woohoo!

Couple of things I spotted with v0.3.108:

It doesn’t mention that you need sed_plugin_library in the docs as far as I can see
When I did install the library, the plugin still failed with an invalid call to sed_lib_extract_packed_variable_section(). Looks like you’re intending to rename the functions in a later version of the library(?) I grabbed v0.2 from your site so, unless I missed something, I manually renamed the function calls for now
Might be worth mentioning that the custom field names should be all lower case (i.e. if the field was defined as My Field you require custom="my field" in the plugin. It may even be "my-field", I don’t know). I’m not entirely sure but I think this automatic lower-casing behaviour occurred in 4.0.5 or 4.0.6 cos it caught me out in my plugins

Anyway, kudos to you yet again. Another blinding plugin. Many thanks.

Last edited by Bloke (2008-03-01 20:01:41)

Txp Network Links

Textpattern Support Forum

2007-01-24 01:10:02

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2007-06-01 19:57:03

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2007-08-05 16:25:43

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-01-02 08:05:35

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-01-30 22:59:07

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-01-31 05:46:08

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-01-31 07:04:14

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-02-11 20:17:18

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-02-11 20:21:17

Re: [ORPHAN] sed_pcf: Packed Custom Fields.

2008-03-01 20:00:52

Re: [ORPHAN] sed_pcf: Packed Custom Fields.