Playa 1.2 - MSM Support, "Open" Statuses setting, bug fixes and other enhancements

@kscot: I’m having the same issue. I have two fields right next to each other in the same weblog entry. One is a regular relationship field and it works fine, the other is a Playa field and I’m getting nothing from it, even though I have multiple open entries selected. Still trying to figure out what’s going on.

ExpressionEngine 1.6.6, Build: 20081212 Playa 1.3.3 PHP 5.2.5 mySQL 5.0.67

When I try to display a related entry, doesn’t matter if it;s playa or a regular one, I get a bunch of PHP errors in my page:

Notice: Undefined index: uitgever in /www/htdocs/client/http/system/extensions/ext.playa.php on line 1774

Notice: Undefined index: field_id_ in /www/htdocs/client/http/system/extensions/ext.playa.php on line 1784

I use EE 1.6.6, PHP5 and playa 1.3.3

Both the displayed entry and the related entry are located in another site than that they are displayed in (so I use MSM and try to display entries and related entries from site2 on site1),

The errors concern my REGULAR relationships, not the playa fields.

If I disable Playa related entries work as expected.

I tried disabling all my extentions, but Playa, to no effect.

Anyone any ideas? Thank you in advance.

I’ve been trying to test and see why my Playa field may not be outputting anything, but I can’t seem to recreate it on a local install with the same EE version and build.

Thanks for trying!

So it must be something in my install/ configuration? Any ideas what might cause the errors? How could the index be undefined at the front, but perfectly findable and editable at the controlpanel?

Anyway; I’ll delve in further, I really need the Playa extension for one of the functions.

Thank you.

After some more research, I’ve found the following. I have this on my template:

extras: {article_extras}

{related_entries id="article_extras"}
  <a href="#">{title}</a>

{/related_entries}

Playa outputs the content of the field in the first instance. When it’s in the related entries tag, nothing is output.

Same specs as above:

ExpressionEngine 1.6.6 Build: 20081212 Playa 1.3.3

I’ve delved a bit deeper. The issues/ bugs I appear to have discovered:

Playa is not truly cross site?

I am displaying entries AND related entries on a different site. Playa does not seem to take the site=”” id into account in the exp:weblog:entries?

When in line 1765 I set the site_id explicitly to ‘2’ it works as expected (that is the id of the site the entries are located in, they are presented in site with id ‘1’)

All fields presented by playa are XHTML?

Does Playa take the specified formatting of the custom fields in the related entries? in my instance it seems that Playa makes them all xHTML fields? When in line 1105 I set the field type explicitly to ‘none’ it is none, but it should be the type of the field as defined in the custom fields of that weblog.

It’s a pity because I would like to use this wonderful extension as it makes a couple of things very user friendly for my editors and me.

Thanks in advance.

I count Playa at the top of the list of MUST USE plugins for nearly every EE site I develop.

Recently, Leevi Graham released “NSM Publish Plus” which appears to be the holy grail of workflow some of my clients have been asking for.

Here’s the catch: Playa disables Quick Save and NSM Publish Plus requires it to be available.

Is there any way to make these two MUST HAVE plugins play nice-nice? I don’t believe I can live without either one now that I know NSM Publish Plus exists!

I count Playa at the top of the list of MUST USE plugins for nearly every EE site I develop. Recently, Leevi Graham released “NSM Publish Plus” which appears to be the holy grail of workflow some of my clients have been asking for. Here’s the catch: Playa disables Quick Save and NSM Publish Plus requires it to be available. Is there any way to make these two MUST HAVE plugins play nice-nice? I don’t believe I can live without either one now that I know NSM Publish Plus exists!

Leevi brought that to my attention a couple days ago. We’re working on a solution, but for now, here’s what you can do:

Open up /extensions/playa/playa.js in a text editor, and remove the line that reads:

quick_save_btn.disabled = true;

(line #521 in Playa 1.3.3)

That should get them to play nicely, however it will not fix the issue where your Playa relations don’t get saved on Quick Save.

Thanks Brandon! I’ll probably wait for a future update that includes a workaround in the code. When I purchase this extension, it looks like I’ll need about 5 copies initially, and then will expand that to about 21+ for all the sites my company runs internationally. Good news for you!

I just set up a page for Playa on Get Satisfaction.

Going forward, please use that venue for support rather than the EE forums.

Thanks!

I’ll take a look at NSM Publish Plus and Playa integration tonight. Hopefully I should be able to come up with something.

I count Playa at the top of the list of MUST USE plugins for nearly every EE site I develop. Recently, Leevi Graham released “NSM Publish Plus” which appears to be the holy grail of workflow some of my clients have been asking for. Here’s the catch: Playa disables Quick Save and NSM Publish Plus requires it to be available. Is there any way to make these two MUST HAVE plugins play nice-nice? I don’t believe I can live without either one now that I know NSM Publish Plus exists!

I’ve just checked in an update to playa that adds quicksave, preview and NSM Publish Plus integration. Fingers crossed Brandon will be able to release a new version soon 😉

Many thanks, Leevi!

I’ll try to release the update tonight. I need to fix an MSM-related bug as well.

-Brandon

Is there anyway Playa can grab users from the DB? rather than entries from the weblog?

I don’t mind a dirty hack, just working on a sort of user access control.

Thanks!