Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#13 2010-11-22 15:51:50
- vurt
- Member
- Registered: 2010-10-22
- Posts: 50
Re: Display 5 most recent articles with same custom field value
redbot wrote:
I suspect you misunderstood how the plugins works. I hope it’s more clear now.
Yes I did misunderstand. Thank you! Now works like a charm with no need to sort.
Offline
Re: Display 5 most recent articles with same custom field value
I have a similar need, but when I use the customfieldname attribute, I get the Textpattern’s notice that this attribute isn’t found!
I am running TXP 4.3.0.
Offline
#15 2011-02-24 12:00:08
- uli
- Moderator
- From: Cologne
- Registered: 2006-08-15
- Posts: 4,313
Re: Display 5 most recent articles with same custom field value
Until you describe your situation a little more verbose: Follow the link in Els’ signature named “Check the names of your custom fields”.
In bad weather I never leave home without wet_plugout, smd_where_used and adi_form_links
Offline
Re: Display 5 most recent articles with same custom field value
husainhk wrote:
I have a similar need, but when I use the customfieldname attribute, I get the Textpattern’s notice that this attribute isn’t found!
Apologies if I’m misunderstanding, but you need to use the actual custom field name as the attribute. E.g.,
<txp:article_custom product="4" />
if you have a custom field named “product”. Check out the link suggested by Uli to make sure you’re using a valid custom field name.
Code is topiary
Offline
Re: Display 5 most recent articles with same custom field value
I am trying to get this snippet work:
<txp:article_custom section=“something” customfieldname=“my_field” limit=“10” form=“some-form” />
When I load the page, I get: Textpattern Notice: Unknown tag attribute: customfieldname
:(
Offline
Re: Display 5 most recent articles with same custom field value
Sorry guys, am laughing and am furious at my silliness!!
Should have used the actual custom field’s name as the attribute … whereas I was using ‘customfieldname’ literally :)
Offline