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: Persistent Entries not working as expected

Status	Resolved
Add-on / Version	Publisher 1.6.3
Severity
EE Version	2.10.1

Linus Design

May 29, 2015

I’m having problems getting Persistent Entries to work. This may be the bug you mentioned that 1.6.4 is going to solve, but thought I should post here in case it’s not.

I have three languages set up: en-us (this is the default), en-uk and de. I’ve published a separate entry to each of those languages, leaving the translations for the other two languages in each entry blank. I’m testing on the front-end with this code:

{exp:channel:entries channel="blog" orderby="date" sort="desc" limit="15" disable="categories|category_fields|member_data|trackbacks|pagination"}
 <h2>{title}</h2>
<p> {blog-body}<br />
{/exp:channel:entries}

When I view a specific version of the site (US, UK or German) I see 3 results returned rather than 1. The

with the {title} tag gets output for all 3, while the {blog-body} tag gets output for the current language, plus the default one when I’m looking at the UK or German version. What I need is just to see entries that have a translation in the current language. Thanks loads for any help!

BoldMinded (Brian)

Comment has been marked private.

Linus Design

Aha – 1.6.4 did indeed fix this! Great, thank you. One last question (I hope!): Say you publish an entry in all languages, but then want to remove the default language version, is there a way to do that? When editing an entry in the CP there’s a “Delete Translation” button but it doesn’t display for the default language. Don’t think this is crucial, but just worried that if my client accidentally enters something on the default language for an entry that’s meant for a regional site, there’s no way to undo that.

Thanks, Frank

BoldMinded (Brian)

Thats actually a use case I had not considered. Let me think about that would be handled.

Linus Design

No worries – thanks!

BoldMinded (Brian)

I think I’m going to close this ticket and consider it an edge case. If I hear more from people about this scenario I’ll look into it again.