Closed septembre2018 closed 2 years ago
@septembre2018 quick question. Are you following the guide at https://gist.github.com/shadcn/23d2cff86eb68836774f877a3ecc88a3?
no, I've tried with my server where I've install a drupal instance as I did with starter kit. I'll try with the guide
HI, I've strictly follow the guide and I still have the same error and I don't know where to investigate...
OK this might sound like an easy fix but I just had this error as well and clearing the cache on the Drupal site fixed it. Can you give it a try?
Clearing cache didn't change the situation. I've "reset" the local permission on the dev folder and it finally work... Thank you for patience.
Hello
I'm getting the exact same error with my Umami installation - error : Initial locale argument was not passed into serverSideTranslations
I have followed the install guide to the letter. I also have cleared the caches several times. Everything seems to be working but when I click on any node, the error pops up.
@septembre2018 could you please tell me in more detail which permissions were to blame?
Hi, As I remember, it was due to a misconfiguration on the Drupal Instance. It was a mix of permissions on server side folders incorrectly sets (because the umami db is inside a file) and the language recognition settings of drupal.
Thank you for a quick answer. I deleted everything and started from scratch. Everything is working now.
I think that for some reason the required Drupal patches in composer.json failed to apply. That was probably the reason for the error for me.
I also can't seem to trigger the patches
Composer version 2.5.4 2023-02-15 13:10:06
PHP 8.1.16 (cli) (built: Feb 16 2023 07:22:21) (NTS)
composer.json
composer install
Edit: 🙈 I placed my patches
in the wrong object.
Hello,
I'm trying to test the new example-umami out of the box. While I'm trying to access to a node i'll get the error : Initial locale argument was not passed into serverSideTranslations
Errors logs :
error - Error: Initial locale argument was not passed into serverSideTranslations at _callee$ (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/next-i18next/dist/commonjs/serverSideTranslations.js:172:19) at tryCatch (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:86:17) at Generator._invoke (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:66:24) at Generator.next (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:117:21) at asyncGeneratorStep (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24) at _next (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9) at /Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/asyncToGenerator.js:32:7 at new Promise (<anonymous>) at /Users/septembre/Documents/GitHub/japi/test-umami/node_modules/@babel/runtime/helpers/asyncToGenerator.js:21:12 at serverSideTranslations (/Users/septembre/Documents/GitHub/japi/test-umami/node_modules/next-i18next/dist/commonjs/serverSideTranslations.js:272:17) { page: '/[...slug]' }
I don't think it is an auth issue because all the pages works correctly except nodes. Not sure if it come from my drupal config or something in the local dev version of example-umami. Drupal instance Drupal : 9.4.1 Php : 8.1
Next-drupal "next": "^12.1.4", "next-auth": "^4.3.4", "next-drupal": "^1.4.0", "next-i18next": "^11.0.0",
Next.config is the same as github :
next-i18next.config.js is the same as github
Would appreciate it if someone have a clue for this