-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Possible bugs in message command when saving to DB #19927
Comments
Do you have a fix for it? |
Hi @atrandafir ,
|
Hi @OndrejVasicek indeed it is the same bug as your issue. And indeed the code block was a bit hairy to understand and fix, and also the logic involved. But I think the way it works right now should be good and we shouldn't get any surprise. I tried to think of most of the use cases so hopefully we should have everything covered. But maybe in the future if this is ever rewritten, listing all the use cases and maybe do some testing would be a good idea in order make sure no new bugs appear. |
* added pcntl to requirements check * Fix #13920: Fixed erroneous validation for specific cases * Fix #13920: Added my name to CHANGELOG.md * trim(): Passing null to parameter #1 ($string) of type string is deprecated * Added section about Unsafe Reflection in Security best practices doc (#19948) Co-authored-by: Bizley <[email protected]> * Update CHANGELOG.md * Fixed tests. * Fix #13920: Add unit test * Update `bower-asset/inputmask`, `bower-asset/punycode`. * added CHANGELOG line * Fix order. * fix: #19978 - Mistake in Korean translation * fix: keep doublequote * Do not duplicate log messages in memory * Update framework/log/FileTarget.php Co-authored-by: Bizley <[email protected]> * Update concept-di-container.md Сслка "Конфигурация приложения" была не верной, она вела на страницу "Service-locator'a" * Update CHANGELOG.md * release version 2.0.49.1 * prepare for next release * Revert changes in `mimeTypes.php` from 4a1f2c6 restores #19936 * update actions/checkout to v4 * Fix mime type generator * Added note * Update structure-controllers.md (#20003) добавил пропущенное слово "как" * Update CHANGELOG.md 2.0.49.2 changelog * release version 2.0.49.2 * prepare for next release * New methods: BaseActiveRecord::loadRelations() and BaseActiveRecord::loadRelationsFor(). * Fixed a bug where the yii serve command would break if a custom router was supplied and it had a space in the path * Fix `MaskedInputAsset::class`. * Fix #19927: Fixed `console\controllers\MessageController` when saving translations to database: fixed FK error when adding new string and language at the same time, checking/regenerating all missing messages and dropping messages for unused languages * Added 'zh' into 'framework/messages/config.php' (#19995) --------- Co-authored-by: Tobias Munk <[email protected]> Co-authored-by: Tim Fischer <[email protected]> Co-authored-by: Tim Fischer <[email protected]> Co-authored-by: Alexander Makarov <[email protected]> Co-authored-by: Oleg Poludnenko <[email protected]> Co-authored-by: Bizley <[email protected]> Co-authored-by: Sonia Zorba <[email protected]> Co-authored-by: Tobias Munk <[email protected]> Co-authored-by: Akbar Herlambang <[email protected]> Co-authored-by: lubosdz <[email protected]> Co-authored-by: Yuriy Bachevskiy <[email protected]> Co-authored-by: Robert Korulczyk <[email protected]> Co-authored-by: salehhashemi1992 <[email protected]> Co-authored-by: PowerGamer1 <[email protected]> Co-authored-by: Brad Bell <[email protected]> Co-authored-by: Alexandru Trandafir Catalin <[email protected]> Co-authored-by: Nabi KaramAliZadeh <[email protected]>
What steps will reproduce the problem?
First part - Set up messages and make them save to DB
https://www.yiiframework.com/doc/api/2.0/yii-i18n-dbmessagesource
common/config/messages.php
Also make sure you create the required tables by running the migration as instructed in API link.
Now add some translations inside some php files in your application:
Then run the messages command with your configuration file:
Until here, everything should have worked as expected and the translations are also working fine.
If you look into the DB you have both the source messages and the translation messages (NULL) rows inserted. You just have to edit the translations rows and add your translations.
Second part
This is where the
bugs
occur.Add a new language into your configuration file:
And also add a new translation string somewhere inside your application:
Now run the messages command again:
What is the expected result?
What do you get instead?
Additional info
The text was updated successfully, but these errors were encountered: