-
Notifications
You must be signed in to change notification settings - Fork 34
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
Problem routing a form to his respective controller #5
Comments
I did not tested the Route::resource() method with Localization package. I'm gonna check this out and try to fix it if there is a bug. Have you tried explicit routes and see if it fix your problem ? |
How can I try it? I'm newbie in Laravel |
Ok, give me extra time to test your case and try to find the issue. The To be explicit is to create your routes manualy. I know it's a little bit pain in the A55, but (IMO) you have a total control and flexibility on your routes and you don't have to run |
Never mind, i fixed it. Try to update the Let me know if it's OK. |
It works! Good job and thanks! |
You're welcome and thanks for your feedback 👍 . |
how did you solve this? please tell me step by step, i am having the same problem as you and i am also a beginner |
Are you using |
Hi, im having a problem when I try to route a LaravelCollective form to his respective controller, this is the view which contains the form:
And here my routes.php
When I route the login to the LoginController I don't have any problem because the login method does not need to be translated but when I try to open the view which contains the form I receive this error messages (server and project are example names):
and
The rest of the translated pages without forms work fine in all the languages.
Here you have the result of a
php artisan route:list
on my project.How can I solve this error message?, with the mcamara LaravelLocalizaton module i had the same error, I´ve cleared the caches and begin into a clean new project but i receive the same error.
Thanks in advance.
The text was updated successfully, but these errors were encountered: