We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Playa 2 Documentation

Development and Programming

viewcreative's avatar
viewcreative
116 posts
16 years ago
viewcreative's avatar viewcreative

Hi,

We’ve purchased a licence for Playa 2, but can’t actually get it to return any values in the template. Does any one know (Brandon!?) if any proper documentation exists? http://brandon-kelly.com/playa really doesn’t give much away. Alternatively if anyone can cast any light on the issue, we’d be very grateful.

Here’s the markup, and the entries are definitely related correctly.

{exp:weblog:entries limit="1" weblog="page" status="Main Navigation|Secondary Navigation|open"}
<h1>{title}</h1>
{body}
<h3>Related Documents</h3>
<ul>
{related_documents}
<li>{title}</li>
{/related_documents}
</ul>
{/exp:weblog:entries}

We’re using FieldFrame & Gypsy, the rest of the weblog entry variales are coming through and the name of the field is indeed ‘related_documents’ but as Playa 2 is a FieldFrame field type and Gyspy is also one of Brandon’s extensions I can’t imagine it being that.

Thanks in advance and apologies if I’m being a tool.

       
Brandon Kelly's avatar
Brandon Kelly
257 posts
16 years ago
Brandon Kelly's avatar Brandon Kelly

Hi Matt,

Do the related entries have a custom status? By default, Playa only shows entries with a status of “open”. To override that, use one of these methods:

{related_documents status="open|My Custom Status"}

or

{related_documents status="not closed"}
       
viewcreative's avatar
viewcreative
116 posts
16 years ago
viewcreative's avatar viewcreative

Hi Brandon,

Thanks for getting back to me so quickly.

I’ve actually just figured it out this second. I had the FieldFrame ‘Path to your “fieldtypes” folder’ set to a relative path, I’ve now set it to an absolute path and everything seems to be working as expected.

Thanks for the status pointer, that could well have been another potential stumbling block.

Cheers

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.