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: Playa selections not honored in entry’s alternate language

Status Resolved
Add-on / Version Publisher 1.4.0
Severity Critical
EE Version 2.8.1

Matt Stein

Jul 01, 2014

Hi Brian,

This Publisher integration has been really smooth, and I’m down to one issue that’s either a bug or user error. We’ve got an English page with a Spanish translation, wherein Playa is used to pull in some simple entries for a slideshow.

What we’d like is to relate different Playa entries for the English and Spanish version. This seems easy enough; switch to Spanish, relate different entries, Publish. The correct set is stored in `exp_publisher_data` with the relevant language ID, something like “[123] [foo] Foo\n [456] [bar] Bar\n” where *foo* and *bar* are the correct entries for that translation.

The front-end of the site, however, continues to show the Playa relationships from the default (English) version of the entry, and re-loading the entry fields in the control panel continues to show the same original Playa relationships as though they were never updated.

Assuming I’ve made sense describing the problem, have I made a bad step or assumption somewhere?

I’m adding an EE login for the production server. Note that it’s safe to experiment in Spanish right now since that version of the site is hidden unless you’re logged in as a Super Admin.

- Matt

#1

BoldMinded (Brian)

Sounds like you have the persistent relationships setting turned on. Have you tried turning it off?

#2

Matt Stein

Another case of insufficient RTFM. Of course that works just fine—thank you and my apologies!

Login to reply