EE4 compatibility updates:

  • Publisher is EE4 and EE5 compatible, but it does not currently support the Fluid field.
  • Reel is EE4 and EE5 compatible, but it does not currently support the Fluid field.

Ticket: Language Mixup of englisch and german in the Frontend

Status Client Wait
Add-on / Version Publisher 2.10.3
Severity
EE Version 5.0.1

Matthias Ballmann

Oct 26, 2018


hi brian,

We have a strange phenomenon since the last update of Publisher (V 2.10.2): A mixture of English and German texts is displayed in the frontend, both on the English and the German pages. For example, a German title is mixed with an English subtitle and an English text. The marginal column is then again in German. Please find some screenshots attached.

In the backend, however, all entries are correct - in the English language version, there is only English content, in the German language version, there is only German content.

If you then save the entries again in the English and/or German version, the error disappears and everything is displayed correctly. However, the error often occurs again during the next editing of an entry.

This is very uncanny, because it makes Publisher seem very unreliable - and we can’t explain to our customer why this happens. However, since we are about to launch the website next week and nothing fundamental has changed on the pages, we believe that the error has something to do with the last update of Publisher.


Thank you for help.
Kindest regards,
Matthias

 

 

 

 

#1

BoldMinded (Brian)

Oct 26, 2018

Hey, Matthias, I’m at the ee conference tmrigjt now so it may be a day or twlo before I can look into this. I apologize for the inconvenience.

#2

BoldMinded (Brian)

Oct 28, 2018

This _might_ be a remnant of a bug in a previous version. Edit and re-save the field settings for the fields that are showing the English text, then re-save the entry and see what happens.

#3

Matthias Ballmann

Oct 29, 2018

well, re-saving the entry always seems to fix it.
I edited the field and re-saved, but since re-saving normally seems to help, there’s no difference.

#4

BoldMinded (Brian)

Oct 29, 2018

Find out what the field ID is, so when editing the entry, what is the ID in the URL? Then check to see if there is a column in the exp_publisher_data table contained a column with the same ID, e.g. field_id_X. If there is no field_id_X before saving the field settings, then field_id_X is there after saving the field settings, then that should fix the issue after you re-save the entry.

#5

BoldMinded (Brian)

Oct 29, 2018

Also, make sure there is a row in your exp_extensions table that has these values:

class: Publisher_ext
method: before_channel_field_save
hook: before_channel_field_save

#6

BoldMinded (Brian)

Oct 29, 2018

It looks like the hook is there, and the data is where it is supposed to be. It should be showing the correct translations on the front-end. Are you positive there is no caching or anything else that would prevent the correct data from showing?

https://screenshots.firefox.com/5DhM9xeXtqznBYY4/kv18.kunstverein.de

#7

Matthias Ballmann

Oct 30, 2018

so, have you all tested the things you wrote me already now? Or should I still check that?

At first I also thought the problem might have something to do with a proxy at the client or the cache of their browsers. But it also occurs here in our office or at my home if I change something on the pages.

#8

BoldMinded (Brian)

Oct 30, 2018

I tested the things I mentioned. That screenshot is a result of what I wanted you to test. That field that is showing the wrong translation in your screenshot clearly has the data in the database, so I’m wondering what else may be happening. Have you tried making a brand new test template, with only a basic entries tag in it, and just that field? E.g.

test.group/index.html

{exp:channel:entries entry_id="2006" dynamic="no"}
    {text_randspalte}
{
/exp:channel:entries} 

Then change the languages and see what renders?

#9

Matthias Ballmann

Oct 30, 2018

I just updated the ticket with two new screenshots – it’s not just one field: it’s the subline and the marginal column, so these two fields.

#10

BoldMinded (Brian)

Oct 30, 2018

Did you try that simple entries tag test in a new template with both fields?

#11

BoldMinded (Brian)

Oct 30, 2018

Matthias, I checked this page and it appears to be rendering the correct content in that left column. https://www.kunstverein.de/institution/newsletter

So is this resolved and working for you as expected?

#12

Matthias Ballmann

Oct 31, 2018

i changed and resaved all the corresponding fields in which the error occurs… and then resaved the entry. i did that last week, though, and still the error occurred again yesterday.
what is the best way to narrow down the problem?

#13

BoldMinded (Brian)

Oct 31, 2018

You said the error occurred again yesterday? What do you mean? It occurred on a new entry or the text reverted to the old/incorrect value? Because what I’m seeing on this page still looks correct: https://www.kunstverein.de/institution/newsletter

#14

BoldMinded (Brian)

Oct 31, 2018

Comment has been marked private.

#15

BoldMinded (Brian)

Oct 31, 2018

If you don’t see this, then it may indicate what the problem is.

#16

Matthias Ballmann

Nov 08, 2018

Comment has been marked private.

#17

BoldMinded (Brian)

Nov 08, 2018

Matthias, you still haven’t responded to this question:

You said the error occurred again yesterday? What do you mean? It occurred on a new entry or the text reverted to the old/incorrect value? Because what I’m seeing on this page still looks correct: https://www.kunstverein.de/institution/newsletter

#18

Matthias Ballmann

Nov 09, 2018

oh, sorry… there were so many messages…
well, when I wrote you about this I already saved the entry again which made the error disappear.

shall I wait next time and mail you when the error reappears?
our client had this yesterday but I can tell them to leave the page as is to let you inspect it.

#19

BoldMinded (Brian)

Nov 09, 2018

Sorry, but can you clarify these two statements?

shall I wait next time and mail you when the error reappears?
our client had this yesterday but I can tell them to leave the page as is to let you inspect it.

To me those two sentences sound like the error is not happening, but the page is being left as it is so I can inspect it because the error is still happening?

#20

BoldMinded (Brian)

Nov 09, 2018

Is there another page this is happening on? If so what is the url and entry_id?

#21

Matthias Ballmann

Nov 09, 2018

i’m sorry if i didn’t express myself so clearly. the mistake that english and german are swapped in the frontend has occurred on many different pages and different channels so far.

However, the custom fields where the error occurs are present in all these channels and on all pages. So far we assume that this is the case with three custom text fields (subtitle, margin column and main text).

Changing these fields and saving them again has not yet created any abrasion.

The error does not always occur - we cannot predict when and on which page suddenly swapped text will be displayed in the frontend. The contents in the backend are always displayed correctly.

We have noticed that the error usually disappears if you save the entry again. So my question was whether the next time the error occurs we should not save the entry again but write you a mail instead?

#22

BoldMinded (Brian)

Nov 10, 2018

Yes, if you see this happen again don’t re-save the entry until I can look at it. Ideally you can re-create it in a stripped down template, no embeds, header, footer, etc, just a single entries tag if possible, which makes it easier for me to debug.

#23

Matthias Ballmann

Nov 28, 2018

hi brian,

There are basically every day cases where German texts end up in the English sections and vice versa. However, since the website is new and only recently online, there are quite a lot of visitors on it… and our customer then fixes such errors quickly by saving them again.

Right now I have found such an error myself, in a place where it is not immediately noticeable. Can you have a look at it?

The URL is https://www.kunstverein.de/mitglieder/mitglied-werden ... and you see both the German and the English version in the column far left the text block:

„All membership fees are tax deductible
A Kunstverein membership also makes a great gift!
Download the Bylaws of the Kunstverein (PDF)“

But of course the German text is entered in the backend of the German version…

„Alle Mitgliedsbeiträge sind steuerlich absetzbar.
Sie haben auch die Möglichkeit, eine Mitgliedschaft im Kunstverein zu verschenken. 
Satzung des Kunstvereins zum Download (PDF)“

The ID of the entry is 1587.

I will update this ticket with all login details.

#24

BoldMinded (Brian)

Nov 28, 2018

Matthias, I’m pretty convinced that this is an issue with your environment (possibly duplicate entry rows), not Publisher itself, otherwise I’d have more similar reports and would be able to reproduce it myself. With that said, you’ll need to simplify the issue. Create a brand new template, with only an entries tag in it, and just the field that is showing the wrong content, e.g.

debug.group/index.html

{exp:channel:entries channel="foo" entry_id="1"}
    
<h1>{title}</h1>
    
{field_that_is_showing_wrong_content}
{
/exp:channel:entries} 

I can’t debug something like this when a full template is being used, there are too many other things to distract from the issue (I don’t mean visually, I mean all the code that is run that is not related to the issue) which makes it very very difficult to debug. So in order for me to really take a look at this, I need it reproduced in the simplest form possible, such as in my example code above. No CSS, no embeds, no snippets, no other module tags, just the entries tag and that is it.

#25

BoldMinded (Brian)

Nov 28, 2018

Also, what is the name of the field in that left column? What is its field id? Is it {randspalte}?

Field ID is #27

#26

BoldMinded (Brian)

Nov 28, 2018

Is this happing to only entry 1587 and only the randspalte field? If so, have you tried deleting entry 1587 and re-creating it?

#27

Matthias Ballmann

Dec 03, 2018

hi brian,

sorry I just saw your reply because I didn’t get an email as ususal.
no, it’s not just happening in this entry – deleting such an entry was our first idea but there are many others that showed the same phenomenon.
this entry is just an example, because the last times it happend the places were more prominent.

often it is in the {randspalte}-field but also in the {untertitel}, which is the subline for most entries.
The mixup occurs most frequently in these fields.

#28

BoldMinded (Brian)

Dec 03, 2018

How many entries does this affect? How much effort would it be to delete those fields entirely, re-add them, and update the entries again with the content?

Have you tried setting up a very basic test case that I mentioned in comment #24?

#29

Matthias Ballmann

5 days ago

hi brian,

Sorry for the break - we had to wait for feedback from the customer because they know their content better and know how many entries they have used these two possible fields.
Unfortunately, this is the majority of the 2300 entries,

Since there is a bit more time this week, I will try your suggestion from #24.

Login to reply

Contact

For add-on support, please use the Support section. General inquries and pre-sale questions can be sent to support@boldminded.com.