-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repeater fields are wrongly displayed as translatable #459
Comments
Yep, definitely a bug. |
@tobias-kuendig could you test PR fix #461 @mjauvin ? Thanks! |
This removes the language toggle from the input fields but it looks like it prevents the values from being persisted to the database completely. After reloading the form the input fields of the repeater are empty. |
@tobias-kuendig thank you for your input, will ping @mjauvin on this one ;) |
@tobias-kuendig are you sure that's caused by this? Could be the issues with build 450. |
The PR contains only one additional condition for the if statement. If I add it the values are no longer saved. Could it be that the frontend now uses the default repeater inputs (not the translate ones) but the logic to store the values still wants to take the data from the Edit: I'm on Build 450 btw |
@tobias-kuendig I tried saving a repeater field with this PR applied and its values get saved as it should, even if the field is not marked as translatable |
Maybe that's the issue with the latest build and MLRepeater, still haven't tested it, yet. |
I AM using the latest build (450)
…On Mon, Apr 1, 2019 at 9:49 AM Denis Denisov ***@***.***> wrote:
Maybe that's the issue with the latest build and MLRepeater, still haven't
tested it, yet.
***@***.***#commitcomment-32985893
<octobercms/library@fd83904#commitcomment-32985893>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#459 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB65vnYUPDI_VqPhjsjyyVVN4loMMTreks5vcg5QgaJpZM4cTui0>
.
--
Marc
|
Demo plugin: https://github.com/tobias-kuendig/translatable-repeater-test
|
@tobias-kuendig @mjauvin if one of you can make a PR from the discussion in octobercms/library@fd83904#commitcomment-32985893 we can get that fix tested and merged in. |
@LukeTowers are you suggesting changing references to $_POST in MLRepeater for the equivalent using Laravel's Request object ? |
Even when disabling the Rainlab.Translate, I get problem saving repeater fields now... |
@mjauvin fix has been merged in |
RainLab.Translate is 1.5.0 Should this problem be fixed in these releases? |
it's working fine with PR #461 applied |
🤦♂️ Once #461 is merged this issue is resolved 👍 |
@TuxCod no, it's in 1.6.0, you have 1.5.0. Enable edgeUpdates if you want to get the latest changes from the marketplace. |
@LukeTowers still same problem :( current version = 1.6.7 |
Repeater fields are NOT translatable. Currently, you need to add the repeater name to the translatable array and add a repeater item PER LANGUAGE. |
@mjauvin thanks |
@mohamed-aitlqadi how did you fix this? mine doesn't not showing the trans language on October CMS build 470. Models:
Fields:
|
@muhammad-ihsan |
@muhammad-ihsan ou cannot translate sub-fields within a repeater, you need to add seperate repeater entries per language. #461 fixed this bad behavior (which didn't event do the right thing in the first place) |
I have the following model:
with the following form:
Since the repeater field is called
name
andname
is marked astranslatable
I end up with this:This isn't what I was expecting, since the repeater field is actually "called"
additional_properties.name
.What makes matters worse is that when I hit save, the model's
name
value gets updated to what was entered in the repeatersname
field (in this case"Property name"
).To me this is unexpected behaviour. The translatable fields should be aware of their context (being inside a repeater). What do you think?
The text was updated successfully, but these errors were encountered: