Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Question about Publisher Playa support
| Status | Resolved |
| Add-on / Version | Publisher 1.0.3 |
| Severity | Trivial |
| EE Version | 2.5.2 |
Mike C
Sep 03, 2013Hi Brian -
Just curious about the scope of Playa support with Publisher on the front end…
We have a template pulling in some related entries via Playa. Both the parent template entry and the related entries have additional language versions saved.
When we view an entry from the parent template in any non-default language, the related Playa entries that are pulled into that template always show up with the default language content (ie. they don’t respect the current language we’re viewing their parent template in).
My hunch is that is the way it is supposed to work and that if we want those Playa entries to get parsed with the language content to match the parent they’re being requested from, we’ll need to roll our own solution to bridge this gap.
However, I thought I’d ask you about this first just incase this should/could already be working and we’ve either missed something or run into a bug.
Thanks,
Mike
BoldMinded (Brian)
It should be full support. It doesn’t matter how deep the template is, its the query in the hook that gets the correct data.
Do you have the persistent playa setting turned on or off? Make sure the following hooks are in the exp_extensions table:
playa_fetch_rels_query, playa_field_selections_query, and playa_save_rels
Mike C
Persistent playa is on and those hooks are there. Let me do some more thorough testing to re-confirm that things aren’t behaving as expected. I’ll get back to you either way.
BoldMinded (Brian)
There have been some updates to the whole P&T support libraries in Publisher since 1.0.3 too. Maybe backup the current version you have and try 1.0.7 to see if it fixes the issue. The fixes mostly revolve around cases in which you use the limit or offset parameters on the Playa or Matrix tags.
Mike C
Ok - good to know. We will try 1.0.7 - it’s on our list but we’ve been updating some other third party modules to play nice with Publisher on this project.
Mike C
Ok - further checking reveals Playa working correctly. The issue was a third party field type not saving edits in different languages.