Support the ongoing development of Laravel.io →
Configuration Input Views
Last updated 1 year ago.
0

You are having this issue in which route?

Also, I don't know this package, but "LaravelLocalizationRedirectFilter" looks suspicious, i'd start looking at it.

Last updated 1 year ago.
0

The problem is only in /used everything else works

LaravelLocalizationRedirectFilter is part of the language plugin and that works as it should, it redirects to a localised route so when I access /used it will direct to en/used and so on, but in the case of this used route everything is ruined.

This is my current routes:

Domain | URI | Name | Action | Before Filters | After Filters | +--------+-----------------------------------+------------------+----------------------------------+--------------------------------------------------------------------+---------------+ | | GET|HEAD / | | PagesController@home | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter | | | | GET|HEAD home | | PagesController@home | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter | | | | GET|HEAD used | used.index | UsedController@index | | | | | GET|HEAD pelting-machines | | PagesController@pelting_machines | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter | | | | GET|HEAD feeding-machines | | PagesController@feeding_machines | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter | | | | GET|HEAD accessories | | PagesController@accessories | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter | | | | GET|HEAD misc | | PagesController@misc | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter | | | | GET|HEAD admin | | PagesController@admin | LaravelLocalizationRoutes, LaravelLocalizationRedirectFilter, auth | | | | GET|HEAD login | | SessionsController@create | | | | | GET|HEAD logout | | SessionsController@destroy | | | | | GET|HEAD sessions | sessions.index | SessionsController@index | | | | | GET|HEAD sessions/create | sessions.create | SessionsController@create | | | | | POST sessions | sessions.store | SessionsController@store | | | | | GET|HEAD sessions/{sessions} | sessions.show | SessionsController@show | | | | | GET|HEAD sessions/{sessions}/edit | sessions.edit | SessionsController@edit | | | | | PUT sessions/{sessions} | sessions.update | SessionsController@update | | | | | PATCH sessions/{sessions} | | SessionsController@update | | | | | DELETE sessions/{sessions} | sessions.destroy | SessionsController@destroy | | | | | GET|HEAD used/create | used.create | UsedController@create | | | | | POST used | used.store | UsedController@store | | | | | GET|HEAD used/{used} | used.show | UsedController@show | | | | | GET|HEAD used/{used}/edit | used.edit | UsedController@edit | | | | | PUT used/{used} | used.update | UsedController@update | | | | | PATCH used/{used} | | UsedController@update | | | | | DELETE used/{used} | used.destroy | UsedController@destroy | | | | | GET|HEAD email | email.index | EmailController@index | | | | | GET|HEAD email/create | email.create | EmailController@create | | | | | POST email | email.store | EmailController@store | | | | | GET|HEAD email/{email} | email.show | EmailController@show | | | | | GET|HEAD email/{email}/edit | email.edit | EmailController@edit | | | | | PUT email/{email} | email.update | EmailController@update | | | | | PATCH email/{email} | | EmailController@update | | | | | DELETE email/{email} | email.destroy | EmailController@destroy | | | | | POST contact | | EmailController@contact | | | +--------+-----------------------------------+------------------+----------------------------------+--------------------------------------------------------------------+------------

I still don't get why a controller here being "UsedController" now suddenly hijacks all /used

and according to this routes table, my requests to /used should go through UsedController@index yes? But weirdly this doesn't happen :( it completely ignores everything and all I get atm is this endless loop thing.

Last updated 1 year ago.
0
Last updated 1 year ago.
0

After even further testing and editing I even cleared the entire routes file only to have UsedController left like this:

Route::resource('used', 'UsedController');

it still won't work when I use that instead for index

Last updated 1 year ago.
0

Investigating it in chrome has the following:

http://imgur.com/tFNIJEU

A lot of requests with and without / at the end ? :o

Last updated 1 year ago.
0

So status is that I still do not know what caused this problem, but I guess it had something to do with the localisation, I solved my issue by using a different controller and routes for the editing part, and leave the translation of the route to the other.

0

you haven't got a folder in /public with the same route name by any chance?

0

Thanks Martin, you saved me a lot of time.

0

+1 Thanks Martin..... you saved me potentially hours of headache!!!

0

Sign in to participate in this thread!

Eventy

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.