Re: [plugin] [ORPHAN] sed_pcf: Packed Custom Fields.

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?

Re: [plugin] [ORPHAN] sed_pcf: Packed Custom Fields.

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.

Re: [plugin] [ORPHAN] sed_pcf: Packed Custom Fields.

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.

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…

Re: [plugin] [ORPHAN] sed_pcf: Packed Custom Fields.

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

Re: [plugin] [ORPHAN] sed_pcf: Packed Custom Fields.

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