i18n error: path "errors.models.posts.postNotFound" was not found
See original GitHub issueI’m getting the following error when adding and deleting content
Technical details:
- Ghost Version: 1.21.6
- Node Version: 6.9
- Browser/OS: Chrome
- Database: SQLite
{
"name":"Log",
"hostname":"Site",
"pid":25551,
"level":50,
"err":{
"id":"b76e1d90-2c6b-11e8-8595-99a5c9cf6e1c",
"domain":"https://mertcangokgoz.com/",
"code":null,
"name":"IncorrectUsageError",
"statusCode":400,
"level":"critical",
"message":"i18n error: path \"errors.models.posts.postNotFound\" was not found",
"stack":"IncorrectUsageError: i18n error: path \"errors.models.posts.postNotFound\" was not found\n at new IncorrectUsageError (/var/www/ghost/versions/1.21.6/node_modules/ghost-ignition/lib/errors/index.js:79:23)\n at Object.findString (/var/www/ghost/versions/1.21.6/core/server/lib/common/i18n.js:152:31)\n at Object.t (/var/www/ghost/versions/1.21.6/core/server/lib/common/i18n.js:66:23)\n at Child.then (/var/www/ghost/versions/1.21.6/core/server/models/post.js:690:50)\n at Child.tryCatcher (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/util.js:16:23)\n at Promise._settlePromiseFromHandler (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:512:31)\n at Promise._settlePromise (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:569:18)\n at Promise._settlePromise0 (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:614:10)\n at Promise._settlePromises (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/promise.js:693:18)\n at Async._drainQueue (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/async.js:133:16)\n at Async._drainQueues (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/async.js:143:10)\n at Immediate.Async.drainQueues (/var/www/ghost/versions/1.21.6/node_modules/bluebird/js/release/async.js:17:14)\n at runCallback (timers.js:794:20)\n at tryOnImmediate (timers.js:752:5)\n at processImmediate [as _immediateCallback] (timers.js:729:5)"
},
"msg":"i18n error: path \"errors.models.posts.postNotFound\" was not found",
"time":"2018-03-20T18:22:58.547Z",
"v":0
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (13 by maintainers)
Top Results From Across the Web
Missing i18n keys causing translation-not-found errors in the ...
Overview of the issue Two missing i18n keys are causing translation-not-found errors in the admin health page: Motivation for or Use Case ...
Read more >rails-i18n not working for header error - Stack Overflow
The gem works but for header message it doesn't. (The 4 errors prohibited this list from being saved: part). This is what I...
Read more >The Basics of Rails I18n - Translate errors, models, and ...
This post covers the YAML file setup for error messages and model names/attribute names, and lookup using the I18n.t method.
Read more >Rails Internationalization (I18n) API - Ruby on Rails Guides
Every string inside Rails is internationalized in this way, see for instance Active Model validation messages in the activemodel/lib/active_model/locale/en.yml ...
Read more >A Comprehensive Rails I18n Guide | Phrase
rails-i18n provides locale data for Ruby and Rails. It stores basic translations like months' and years' names, validation messages, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Pushed two broken i18n keys, see https://github.com/TryGhost/Ghost/commit/e43bdad8184700752ed1c042bf5a81bc53d7f772.
Discovered by @ErisDS - thanks!
@kirrg001 I tried node version 8.9, so maybe it will not give an error. but it still gives an error, Nothing changed
note: im coming slack