Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Suggestion: saveTranslation(s)? #51

Open
andreCatita opened this issue Jun 3, 2016 · 0 comments
Open

Suggestion: saveTranslation(s)? #51

andreCatita opened this issue Jun 3, 2016 · 0 comments

Comments

@andreCatita
Copy link

andreCatita commented Jun 3, 2016 •
edited
Loading

Hello,

From what I can see, it seems that afterUpdate only triggers for 'relations'.
If we have a model, that is only using the 'relation' relation.
It won't update.
It will only update, if we call multilingual() or localized().
Am I mistaken or is it so?
Couldn't you tweak that afterUpdate, to trigger the update for BOTH relations (relations and relation)?

Thanks.
igorveremsky added a commit to igorveremsky/yii2-multilingual-behavior that referenced this issue May 25, 2018
@igorveremsky
fix error with update translations only if translations populate (O…
9644b07 
…mgDef#51)
OmgDef added a commit that referenced this issue May 29, 2018
@OmgDef
Merge pull request #73 from igorveremsky/master
3a903c3 
fix error with update translations only if `translations` relation populate (#51)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andreCatita