Navigation

Copy Markdown View Source

By default, Backpex redirects to the previous resource path (index or show view) after creating or updating an item, but you can customize this behavior.

Configuration

To define a custom navigation path, you need to implement the return_to/5 callback in your resource configuration file:

# in your resource configuration file
@impl Backpex.LiveResource
def return_to(socket, assigns, live_action, _form_action, item) do
    ~p"/home"
end

The example above will always redirect to the /home path after editing an item.

Available Live Actions

Backpex supports the following live actions:

  • :index - The list view of your resource
  • :new - The form for creating a new resource
  • :edit - The form for editing an existing resource
  • :show - The detailed view of a single resource
  • :resource_action - An open resource action on the list view

Form Actions

When working with forms (in :new or :edit live actions), the following form actions are available:

  • :save - When a form is successfully submitted aka the "Save" button was clicked
  • :cancel - When a form submission is canceled aka the "Cancel" button was clicked

For all other live actions, the form_action will be nil.

Sometimes the destination depends on where the user came from rather than on the resource itself. For these cases you can append a return_to query parameter to any :new, :edit, or :show URL. Backpex uses it as the navigation target after the form is saved/canceled or after an item action completes, overriding the default index/show path.

# link into the show view and send the user back to a custom page afterwards
~p"/admin/posts/#{post}/show?return_to=/dashboard"

This is useful, for example, when a notification links to a resource and you want the user to return to the notification list once they have acted on it.

Only same-origin, absolute paths are honored. Any value that carries a scheme or host (https://example.com, //example.com, /\example.com) is ignored to prevent open redirects, and Backpex falls back to the default destination. Paths may include query strings (e.g. /admin/posts?page=2).