Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hello,
I am a newbie here and I don't know how to set up moving between URL's right. Let's assume this example
/orders
/orders/edit/1
/orders/addNote/1
Main page /orders has got a table with filter form in $_GET. You can go to detail of order from there /orders/edit/1.
Now you can use this for going back to orders:
<a href="{{ url()->previous() }}" class="btn btn-default">Back</a>
But, when form on edit site has errors, this href link returns me on same site /orders/edit/1
Now, let's assume that we go from /orders?name=order_name to /orders/edit/1 and then we need to add note /orders/addNote/1 and go back to /orders?name=order_name. This will work only for last step (addNote -> edit) and then context is lost.
Is there any way how to do this right?
Thank you for any help
After updating data, you redirect back to the same page or its parent.
For example, if you are on /orders and you click edit on an item, ypu might load /orders/edit/1
after posting data to that order, you finish with redirect('/orders') rather than previous
If you add a note, you know which order it was for so you can return to the specific order rather than the list of orders or previous
@snapey Thank you for your answer. It will be right but there is a filter on orders page. And also, user can go to /orders/edit/1 from multiple routes like /stats/orders etc.
/orders?name=order_name
/orders/edit/1
/orders?name=order_name
/orders?name=order_name
/orders/edit/1
/orders/addNote/1
/orders/edit/1
/orders?name=order_name
I think the only way how to solve this is by Session. When user filters something on /orders?name=phil save it to session and then adding some salt as backlink to url.
Like/orders/edit/1?back=SALT
But then, I don't know how to have that salt in url persistent. As user can go to /orders/addNote/1?back=SALT with that SALT.
Part of this is solved by this article
@DarkHarden if you know the flow of url cant you use the route name and redirect it in the end of every particular flow.
@biishmar NO, as I said. You don't get it.
There could be many params in filter /orders?name=name&surname=surname&limit=50
And also - user can go on edit page from multiple pages...
@DarkHarden Dont have to use SALT, just save it in session, in the controller check this session exists or not and append the param in session with the url and redirect.
@biishmar Yes, I can use it in session as I said before, but there is another problem:
/orders?name=Alan&order_by=name
/orders/edit/1
/payments
/orders - it redirects me to filter /orders?name=Alan&order_by=name and that is bad behavior...That's why URL parameter will be much more helpfull.
@DarkHarden You want that query string to be attached while u go back or u dont want it?
@biishmar I want it only when I go back from /orders/edit/1. It's seems very confusing.
Please or to participate in this conversation.