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 / Publisher Low Search upgrade gone wild

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

Caroline C. Blaker

Jul 15, 2015

Description:

With an upgrade from EE 2.6.x to 2.10.1, we upgraded Publisher and Publisher Low Search. We have 2 issues:

1. The Spanish side is only selectively producing Spanish (http://www.inbstaging.com.php54-4.ord1-1.websitetestlink.com/es), when the site before the upgrade (still live: http://inbweb.com/es) is entirely in Spanish . The bits that are getting selectively skipped are entirely housed in Channel:entries.

2. Publisher low search is out of whack. - The should-be Spanish titles are displaying in English on the Spanish side and neither side has any low_search_excerpt fields displaying. I see that some changes have been made to Low Search like the addiition of a language to the collection - however, this apepars to assign a language to a collection that natively has 2 languages - and there’s a lack of docs about re-tooling this between versions between Low and you, so we’re luffing in the wind on this one - unsure if it’s something we need to do or something we need to undo/redo.

The un-upgraded version is still live and can be used for comparison here: http://inbweb.com/

Detailed steps to reproduce the issue(s):
1. Go to http://www.inbstaging.com.php54-4.ord1-1.websitetestlink.com/ and click the translate button up top.

2. Search for “bank” on the English side
3. Search for “banca” on the Spanish side

BoldMinded (Brian)

I assume you upgraded Low Search as well?

BoldMinded (Brian)

Also, are you using this version of the extension? https://devot-ee.com/add-ons/publisher-low-search

Or the old version? https://github.com/litzinger/publisher_low_search

Caroline C. Blaker

Low Search was also upgraded. Additionally, we have the commercial (new) version of PLS.

BoldMinded (Brian)

Would you be able to take a few minutes and create a fresh install of EE, Publisher, Low Search, and Publisher Low Search and create a couple of test entries in a couple languages and see if its indexing correctly? This may sound like a lot to ask, but it shouldn’t take but an hour or so, and it will help me identify if its a global issue, or something created as a result of upgrading.

Caroline C. Blaker

If we were able to provide FTP to this test site, would that be enough? You could create whatever entries.

BoldMinded (Brian)

I see the FTP information attached to the ticket, but I only login to FTP when absolutely necessary, not as the first step in debugging. Its too much of a time sink for me. If you can create that clean environment with only those 3 add-ons and replicate the issue there, then it’ll tell me that it’s a broader issue in general or if its an issue with upgrading. I’ll also try to replicate it locally either way after this to confirm I can replicate it too, and then if I need to I’ll login to the FTP, but if I can replicate it locally I’ll avoid the FTP if I can. Its much harder for me to debug via FTP, and on a couple of occasions I spent several hours debugging in a customer’s environment only to discover it was an issue created by the customer, not the add-ons. Not saying this is the current case, just explaining why I try to avoid FTP debugging if at all possible 😊

Caroline C. Blaker

Understood - I’ll get that env created.

As a side note, I’d love to know about issues that are created by the customer too as I’m brand new to this entire scenario.

If we are using Structure, do you want that on there (the version we are using is the most up-to-date.)

BoldMinded (Brian)

One of the issues was the customer was using Stash heavily, and just didn’t use the right template parameters, so it ended up not being an add-on issue just user error, but it took me forever to realize thats what it was. Another ended up being a poorly configured server which was out of my control.

Caroline C. Blaker

Hi!

I’m working with a very capable team and they were interested in updating the ticket like so:

“Switching the field type did not make a difference. However, I did locate the entry in the database and the translated and english version updates are in the correct location. It appears that whatever publisher is using to pull the language translation for entries is not working. However, Phrases still work in the system.”

We are comparing apples to apples with the un-upgraded site which, again, works.

We are capable of any kind of PHP troubleshooting you can throw at us. We just need direction.

#10

Caroline C. Blaker

In other detail: “looks like its just rich text fields, like Expresso”

#11

BoldMinded (Brian)

I assume this comment is referring to the indexing process? “It appears that whatever publisher is using to pull the language translation for entries is not working”

#12

Caroline C. Blaker

yes, publisher is not translating channel entries, but phrases

But it is storing data in the publisher_data table (edited)

#13

BoldMinded (Brian)

So the low_search_index table is where the what should be translated data is not appearing as translated? Or its in the output of the search results tag that stuff isn’t translated?

#14

Caroline C. Blaker

We have 3 issues:

Normal channel:entries output from Rich Text fields isn’t being translated on the Spanish page (non-default language)
Titles in search:results tags isn’t being translated.
low_search_excerpt isn’t showing up in either language.

#15

BoldMinded (Brian)

For #1, are any other add-ons installed, such as Content Elements? The only time in recent memory that a normal text field wasn’t displaying translated content was b/c it was inside of CE, which is a CE bug, or something else was modifying data/conflicting with Publisher.

2 and #3, thanks, that gives me something to focus on. I may not be able to dive into this though until early next week.

#16

Caroline C. Blaker

For #1 - Content Elements is not installed. Structure is in use. The site has a lot of add-ons, but Structure appears to be the only one at Publisher’s level.

Here’s a code snippet of what’s not working, being just one:

{homepage_slides}
<li>

{exp:ce_img:pair src="{slide_main_image}"}
{made}
{/exp:ce_img:pair}


{exp:ce_img:pair src="{slide_name_image}"}
{made}
{/exp:ce_img:pair}

{exp:channel:entries channel="homepage"}

{exp:ce_img:pair src="{slide_main_image}" filter="grayscale"}
{made}
{/exp:ce_img:pair}


<div class="slidetext">
<h1><a href="http://{slide_button_url}">{slide_headline}</a></h1>
{slide_text}
<a href="http://{slide_button_url}class=boxbtn">{slide_button_label}</a>
</div>
{/exp:channel:entries}
</li>
{/homepage_slides}

Visible here, at the top: http://www.inbstaging.com.php54-4.ord1-1.websitetestlink.com/es

You can see below that inclusions (like the blog entry) are not translated whereas the headline for the blog is.

#17

Caroline C. Blaker

Just kidding. This code:

{exp:channel:entries channel="homepage"}

{homepage_slides}
<li>

{exp:ce_img:pair src="{slide_main_image}"}
{made}
{/exp:ce_img:pair}


{exp:ce_img:pair src="{slide_name_image}"}
{made}
{/exp:ce_img:pair}

{exp:ce_img:pair src="{slide_main_image}" filter="grayscale"}
{made}
{/exp:ce_img:pair}


<div class="slidetext">
<h1><a href="http://{slide_button_url}">{slide_headline}</a></h1>
{slide_text}
<a href="http://{slide_button_url}class=boxbtn">{slide_button_label}</a>
</div>
</li>
{/homepage_slides}
{/exp:channel:entries}

#18

BoldMinded (Brian)

What is homepage slides? Matrix or Grid? Is it the slides_text field that is not working? Its details like this that can entirely change where I need to look to debug and re-create the issue.

#19

Caroline C. Blaker

They are actually Playa fields for a slide channel. Thank you!

Just keep asking me questions and I’ll keep answering.

#20

Caroline C. Blaker

The slide_text/ slide_headline fields are not translating and the link is to the Eng page too.

#21

BoldMinded (Brian)

What happens when you display those same fields from an entries tag without using Playa?

#22

BoldMinded (Brian)

Caroline, I can’t replicate #2 and #3. The title, excerpt and other custom fields are showing the translated version in the low search results tag properly. Have you tried un-installing the Publisher Low Search Extension and re-installing it and re-indexing the collections?

#23

BoldMinded (Brian)

Also can’t replicate #1. Playa tags are displaying translated title and custom fields just fine inside of an entry loop.

Are you sure there is no caching or something else interfering with the rendering? I think at this point you’re going to have to replicate these issues in a new/clean environment before I can spend more time debugging.

#24

Caroline C. Blaker

Ok -

We got this settled with this info: https://getsatisfaction.com/low/topics/low-search-publisher-upgrade-gone-wild

Turns out there was an extension interfering with the ‘channel_entries_query_result’ hook. Disabling took care of this.

I’m interested in any info you might have on what a practiced developer might do to fix the extension that needed to be disabled - since I think we still need it. Stuff to Google is ok 😊

Thanks so much for all of your effort in helping us!

#25

BoldMinded (Brian)

This doesn’t surprise me in the least. 9 times out of 10 if I can’t replicate the issue its bc of a conflict. What extension did you disable to make it work again? There should be a way to fix it but sometimes if the other addon is the cause then it’s up to that dev to fix it. I can take a look and fix it on my end of that turns out to be the problem, just need to know what extension it is.

#26

BoldMinded (Brian)

Caroline, can you tell me what extension you disabled to correct this so I can look into a permanent fix if its something on my side? Thanks.

#27

Caroline C. Blaker

The plugin was called Order Entries and I believe it was internal, not something most people will have an issue with.

The important thing is to go query:

Select class from exp_extensions where hook ='channel_entries_query_result'

This will give you the names of all the candidates that might need to be disabled to rectify the error.