Hello everybody! I'm wondering if someone already has a realization of comprehensive redirects to the index after creating or updating a resource for different scenarios considering pagination. relations, etc.?
If you are wanting to preserve pagination page or similar, I think you would need to store the current page in a session var or similar? Then use that value when the index page is loaded.
@gpalmer711 Thank you very much for your attention. Yes, I know about suggested features, but I'm searching something like a package or a trait to include and just use. It's a dream, right? =)
There're a bunch of scenarios not to forget (I don't want to list them up), bit the general approach with sessions is the first to consider.
I think, I'll start implementing this feature myself on Monday.
@Snapey The request of my client is very simple. He doesn't want to see that detail page after creating/updating a record. To be honest, I agree with him. There's more uselessness than usefulness. Going back where an administrator had been before is more time consuming =(
@Snapey On the other hand, from the very first thought it seems that by saving all the steps (urls) to a session variable without the edit resource url might be helpful.
@Snapey I might edit a record from a second, third page, I might apply some sorting and again be on the second page. Additionally, we can add relations in my scenarios, filters, search, lens,.....
@Brand3000 so the index page has state, as represented in the url (assuming you can refresh the index page and arrive at the same state with pagination or searches or whatever.
You have (at least) two options. 1, store the query string until you need it back, eg in session or pass it along through editing via a hidden form input or, 2, avoid the issue by performing edit in a modal, thus leaving index intact.
