Playa

Luke, I had this problem too. I was on php 4.x.x and Playa requires php 5. Once we upgraded to php 5 it worked (well, I can’t get the js and css to show up, but everything else worked).

Thanks Adam, I’m on php 5 so that’s not the source of the problem in my case. I’ve got Playa working now although I’m not really sure why, I suspect it happened when I upped my PHP memory limit from 16 to 64 meg.

It seems like the Tiny MCE (not LG Tiny MCE) extension and playa don’t play(!) nicely with each other.

When Tiny MCE is enabled, none of the css or js files get included for playa.

BUT I’ve got a big list of things I want to do with the extension (custom status support…

Does anybody know how to hack this thing to make custom statuses work now? Basically I want anything except for status = closed to be available, and count towards the limit.

Curious if anyone has been able to use data stored by playa through the search weblog parameter and if so how?

For example in the following:

{exp:weblog:calendar switch="calendarToday|calendarCell" weblog="events" search:event-relationships="Principals" show_future_entries="yes" show_expired="yes"}

I have event weblog entries being associated with entries from another weblog. Would like to be able to filter the events displayed in a calendar by specific entry titles of related weblogs. After some initial digging it seemed the search parameter may be used, but my efforts above are not working. The event-relationship field has been set to allow search.

Wow, I’m getting the REL bug with Playa too. I’m on EngineHosting, which is PHP 5.1.6 and they give 64MB PHP memory. This is a mysterious problem. Playa’s functions appear to be integral to what we’re wanting to do, so this is very frustrating.

Hi Brendon, what is your weblog structure like, do you have a lot of blogs and a lot of entries already set up in EE? Another thing I did which may have made this bug go away was to simplify my weblog structure.

I’m using this with MSM. If MSM compatibility is a problem I can gladly move to another separate install. That’s something I’ll have to test on a localhost install.

I have a single-weblog site with a couple hundred entries.

On this new site which would use Playa, I have six weblogs. Four of them have zero entries currently. One has 85 entries, and the other 13. The relationships I am trying to set up would link each of the 85 entries to some of the 13.

Currently only one of the 85 entries has any of the relationships established. I was shocked to see the REL error.

Hmm.. I would definitely try using Playa on the same server with a clean install of EE.. first with MSM, then if the problem persists without it.. Sorry, thats the best advice I can offer at the mo.. I’m not sure if there is any history of problems with MSM

Is anyone else using Playa with the Cloner extension: http://expressionengine.com/downloads/details/cloner/ ?

When I have both enabled, when I go to edit certain entries I get a blank screen. If I disable cloner, the edit works again.

Any ideas?

This REL error is a real mystery. Thinking it might be due to conflict with the Multiple Site Manager, I went to a new install of EE 1.6.4 and Playa 1.0.9 – no other extensions, no complex weblog configurations. And then I set up the two weblogs between which I want to show relationships, put two entries in each. That can’t be too burdensome for Playa to accommodate.

Still throwing the REL error. The other explanations offered – bad PHP version, not enough PHP memory – don’t seem applicable as I am using EngineHosting. Unless there are other EngineHosting users experiencing this error…

To follow up on my crestfallen message above, I found that on the new, “clean” install of EE, although Playa doesn’t work the standard ExpressionEngine Related Entries tag did, briefly, show results. Then it went into the REL errors. And, oddly, on the MSM-enabled sandbox where I originally failed with Playa, the Related Entries tag still doesn’t work – that dang REL error keeps appearing.

I’m going to try another hosting setup (we’re on EngineHosting now) to see if there’s just something related to the hosting environment, but I’m disappointed with this because Related Entries was one of the core features I wanted to use on this site we’re developing.

It turns out that the failure of Related Entries under plain-vanilla ExpressionEngine was the key to solving my problem. My Playa installation works great now.

First of all, it appears there is no problem with the Playa extension. Now that everything is working fine, I see Playa is as wonderful as it first appeared to be when reading about its power and usability. I’m glad I can use it now.

What fixed my problem? Well, once I found that Related Entries from the base install of EE failed for me, I got to wondering whether EngineHosting really was giving me PHP 5 as their Control Panel indicated. Whoops! Turns out, my PHP version is 4.3.9. Cut-and-paste Mark Huot’s PHP 4 fix for the Weblog Module and everything started working for me.

Want to check your own PHP version? Paste the below into a template in which PHP is enabled:

<?php
// prints e.g. 'Current PHP version: 4.1.1'
echo 'Current PHP version: ' . phpversion();
?>

And you may have a breakthrough like I did today.

Moral of the story? Trust, but verify.

I’ve been trying to figure this out pretty much all day now, and I’m not about to go hacking someone else’s Extension … I want the first item in the list to be the “primary” related item, and the others to be secondary. In weblog world I could do a limit=”1” with a specified order to make the first item the primary. Then use offset=”1” to get the rest.

Thus, my issue boils down to these two things:

1) I cannot use limit=”N” in {related_entries}. If I do it displays nothing.

2) I cannot use offset=”N” in {related_entries}. Same issue, displays nothing.

Any help would be appreciated!

Thanks, Sean (Paramore | Redd Online Marketing)