-
Hi, I'm using translatable and sluggable both. My slug field is also translatable and slug field is routeKeyName of my model. I'm trying to do route binding but always query on language defined in app.config.locale. I added \Illuminate\Session\Middleware\StartSession::class middleware to api middleware block in kernel.php to understand whether user change api using language. locale seems changed in controller but when try to route binding it still query on default language field and throws error. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
If anyone needs; I use sluggable and translatable together. I serve API service but my needs require also translation for 3 languages. In order to do that, i add those two middlewares to main middleware array not under any middleware group in app.Http.Kernel.php file.
StartSession middleware makes you able to hold session, its added under web middleware group by default. But in my case, you should add this to main middleware array to hold session in API service. Localization middleware is my own middleware for language system. When add StartSession middleware under api middleware group, it didn't work but under main middleware array it worked like charm. |
Beta Was this translation helpful? Give feedback.
If anyone needs;
I use sluggable and translatable together. I serve API service but my needs require also translation for 3 languages. In order to do that, i add those two middlewares to main middleware array not under any middleware group in app.Http.Kernel.php file.
\Illuminate\Session\Middleware\StartSession::class,
\App\Http\Middleware\Localization::class,
StartSession middleware makes you able to hold session, its added under web middleware group by default. But in my case, you should add this to main middleware array to hold session in API service.
Localization middleware is my own middleware for language system.
When add StartSession middleware under api middleware group, it didn'…