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: :entries loops returns untranslated results

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

Nick Benson

May 20, 2015

After the upgrade to Publisher 1.6.3, exp:channel:entries and exp:structure:entries are showing all entries that match the criteria of the various parameters, regardless of whether or not a translation exists for the current language. It does show the translated content when it exists (it’ll show the French title of an entry when looking at the /fr/ part of the site), but, it’ll also show all of the untranslated English entries that match the parameters.

Let’s pretend that “English Title 1” is the only entry translated to French.

Assume the following code:

<h1></h1>

Output from example.com/group/template:
English Title 1
English Title 2
English Title 3

Output from example.com/fr/group/template:
Translated French Title for English Title 1
English Title 2
English Title 3

We don’t want to see English Title 2 or English Title 3 on that page, as they haven’t been translated.

It’s worth noting that exp:low_search:results and exp:structure:nav are also being used, and are working as they should be - only entries that have been translated are returned by them.

 

#1

BoldMinded (Brian)

That basically sounds like you have the persistent entries setting turned on. You can turn it off globally, or per entries tag by adding publisher_enable_persistence=”n”

#2

Nick Benson

It sure does; all three settings for persistence in the control panel are already set to “no” though, I’m afraid.

#3

Nick Benson

Looks like adding publisher_enable_persistence=”n” to the template solves the problem though, which is an excellent temporary solution for the deployment coming up tomorrow, thanks!

Will have to get a fix to listen to the control panel settings for the next update though, of course.

#4

BoldMinded (Brian)

K, I’ll dive into it later this week. I spent 4.5 hours last night on another bug, so I’m kind of wiped and can’t bear to look at my computer again tonight.

#5

BoldMinded (Brian)

Comment has been marked private.

#6

Nick Benson

Build included in previous private comment appears to resolve this, thank you! Mark as closed at your leisure.

Login to reply