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: Publisher/Safecracker playa fields

Status Resolved
Add-on / Version Publisher 1.0.4
Severity Trivial
EE Version 2.5.5

brygeaux

Aug 16, 2013

Hallo,

I just noticed that when displaying a Safecracker form in draft mode that the playa fields still show the ‘open’ entry’s data. All the other fields I display correctly show the ‘draft’ entry’s data.

When editing the draft in the CP it correctly shows the ‘draft’ playa field’s data, and the exp_playa_relationships table has both the open and draft entry’s correct data.

Just another thing with Safecracker I guess.

#1

BoldMinded (Brian)

Did you try adding publisher_status=”draft” to the playa field or safecracker tag? Or maybe the parent entries tag?

#2

brygeaux

Well, it’s a multi-select playa field. I don’t see any easy way of replicating that in a safecracker form while still bringing in the draft’s values.

But yeah, the

{field:playa_field publisher_status="draft"}

doesn’t work for me.

#3

BoldMinded (Brian)

You don’t need to add the publisher_status to the playa field. It definitely saves the draft properly as is, I just ran several tests. This is what my form tag looks like:

{exp:safecracker channel="zoo_visitor" return="zoo_visitor_example/profile/success" publisher_status="draft" entry_id="18"
safecracker_head="yes" include_jquery="yes"}

<input type="hidden" name="publisher_save_status" value="draft" />
<input type="hidden" name="publisher_view_status" value="draft" />
<input type="hidden" name="lang_id" value="{publisher:current_language_id}" />

{field:member_playa}

{/exp:safecracker}

Make sure those hidden fields are present.

#4

brygeaux

I’ve tried it on a barebones site and still can not reproduce the success. Login info sent via email

#5

BoldMinded (Brian)

This is fixed in the 1.0.7 release.

Login to reply