BoldMinded

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: Custom fields are not saved per language

Status Resolved
Add-on / Version Bloqs 2.8.3
Severity
EE Version 3.5.15

Service Desk

Jun 28, 2018

Hi there,

We have 3 languages for a site. Everything is setup and working except the translation self. When i switch a language and change a custom field to a different value, the value is saved for all translations.

I checked all setting, but cannot find out how this can be happen.

Can you check for me if the settings are correct?

Best,
REin

#1

Dunique

Comment has been marked private.

#2

BoldMinded (Brian)

I’m going to need a lot more information before I can help.

Is this a new install of Publisher or did you just upgrade from a previous version? If so, what version #? Did this issue just start happening with the new 2.8.3 version or was it happening with an older version too?

You said custom fields… what type of custom fields? Textarea, text, Wygwam, Relationship, Grid, Fluid, Bloqs, text/wygwam/relationship inside of Grid? etc etc

What is your view status of the entry? Is it defaulting to view drafts or the published version? Are you saving the translation as a draft or published version?

#3

BoldMinded (Brian)

Is the channel you’re editing an ignored channel? Or are the fields ignored?

What specific entry are you editing (please provide an entry id) and in what specific channel (channel name)? I don’t want to hunt through your CP to see what you’re seeing… I need to be pointed directly to the problem entry.

#4

Dunique

>> Is this a new install of Publisher or did you just upgrade from a previous version? We upgrade from 2.7.x (last version number of the 2.7 release)

>> was it happening with an older version too? Yes it was also happening with the 2.7.x version

>>You said custom fields… what type of custom fields? Textarea, text, Wygwam, Relationship, Grid, Fluid, Bloqs, text/wygwam/relationship inside of Grid? etc etc Text field

>>What is your view status of the entry? I Published

>> is it defaulting to view drafts or the published version? Draft is disabled.

>> Are you saving the translation as a draft or published version? As a published version

>> Is the channel you’re editing an ignored channel? Or are the fields ignored? No

>>What specific entry are you editing (please provide an entry id) and in what specific channel (channel name)? I don’t want to hunt through your CP to see what you’re seeing… I need to be pointed directly to the problem entry. I send you a link… The entry ID = 1 and the channel = homepagina

Let me know.

#5

BoldMinded (Brian)

Is this happening in the CP only or on the front-end?

#6

Dunique

>>Is this happening in the CP only or on the front-end? both

#7

BoldMinded (Brian)

Thanks for the follow up. I’m a bit confused though, you said it was happening in in 2.7.x… how long has this been happening for you?

#8

Dunique

yes, it was happening in 2.7.x and i thought it was a bug. So i updated to 2.8.x

Not sure how long this is happening, but it seems from the beginning. The customer just started with the translation, so we didnt notice. And because other fields are working as expected.

#9

BoldMinded (Brian)

Is this happening on all entries? You said other fields are working as expected, which fields are those? Does this happen on new entries or just existing ones? What have you done so far to debug the issue?

I’m just trying to figure out what may have changed recently to cause this and find the source of the problem.

#10

Dunique

>>Is this happening on all entries? It seems happen to just the entry_id=1 \

>>You said other fields are working as expected, which fields are those? Any other field. For example the field “Alternatieve titel” for entry_ID=25

>>Does this happen on new entries or just existing ones? Both new and existing

>>What have you done so far to debug the issue? check the publisher settings, but did not change anything as it looks good for me.

#11

BoldMinded (Brian)

Comment has been marked private.

#12

Dunique

Thats correct, because you are posting it into the “content” channel. The “content” channel is working as i said before. The problem is inside the “homepage” channel (entry_id=1) Note, it has a limit of 1.

#13

BoldMinded (Brian)

Can you remove the limit and create an new entry in that channel to replicate the issue? Then I’ll take a look at it.

#14

BoldMinded (Brian)

Few questions…

What was the first version of Publisher you installed? Do you remember which versions you upgraded to each time? E.g did you skip any versions or upgrade to every release? Have you added any custom fields to the site recently? If so, are those the fields you’re having trouble with? Do old fields work? Most importantly, what do you get when you run the following query on your database?

select * from exp_extensions where class = 'Publisher_ext' and method = 'before_channel_field_save';
#15

Dunique

>> Can you remove the limit and create an new entry in that channel to replicate the issue? Then I’ll take a look at it. I removed the current entry, and create a new entry (id=50) Problem still exists

>>What was the first version of Publisher you installed? 2.7.10

>>Do you remember which versions you upgraded to each time? E.g did you skip any versions or upgrade to every release? We upgraded from 2.7.10, where this problem already exists, to the current 2.8.3 version

>>Have you added any custom fields to the site recently? If so, are those the fields you’re having trouble with? Do old fields work? No, we didnt added new fields. Fields in the other channel are working though.

>>Most importantly, what do you get when you run the following query on your database?

extension_id | class | method | hook | settings | Priority | version | enabled 199 | Publisher_ext | before_channel_field_save | before_channel_field_save | | 5 | 2.8.3 | y

#16

BoldMinded (Brian)

Ok, I don’t see what you’re referring to. I edited #50, the home page, and its saving and displaying the translations fine.

English, non-default language https://screenshots.firefox.com/eKfiF2gXwObxAmKO/www.roebke.nl

Netherlands, default language https://screenshots.firefox.com/uJLGfBBpOoKZ1tMv/www.roebke.nl

At this point I’m going to have to ask you to create a video screen cast displaying the issue as you see it.

#17

Dunique

Sure, here you go: https://drive.google.com/file/d/1zfxXHv6oiWjDsbR-PUaAXbfSNlfku8Dy/view?usp=sharing

#18

BoldMinded (Brian)

It looks like the field_id_43 column is not in the exp_publisher_data table for some reason. I re-saved the settings on your “Afbeelding titel” field, which added the column. It should save correctly now. If this happens on any other fields just re-save the settings.

#19

Dunique

wow that simple…. still weird it was not in the correct table though. Will test it today and let you know.

#20

Dunique

Yes, seems to working! Thanks for your help.

#21

Dunique

Comment has been marked private.

Login to reply