Bug Report: formRenderDesign causes redirect to Create screen instead of List after Save and Close

[mplodowski]

OctoberCMS version:
4.0.15

Description

When using formRenderDesign in a backend controller, both in the Create and Update views, the redirect after pressing Save and Close does not behave correctly.

Workflow:
1. Open a record in Create view.
2. Fill out the form and press Save → record is created successfully.
3. While still on the form, make any change.
4. Press Save and Close.

Expected behavior:
Redirect to the list view.

Actual behavior:
Redirect goes to the Create form instead of the record list.

⸻

Steps to reproduce
1. Implement a backend form using formRenderDesign inside a controller.
2. Navigate to the Create view.
3. Save a new record using Save.
4. Modify the form data.
5. Click Save and Close.
6. Observe that the system redirects to Create instead of the list page.

[mplodowski]

The same issue is when you create record and after that delete it. It will redirect you back to create action instead of the records list.

[daftspunk]

Since v3 redirect sends you back to the previous page instead of to the list. This is so the page number is retained, if you edit a record from the list on page 5, it wants to return you to page 5. In this case, if you create a record and save, the previous page is to create another record.

[mplodowski]

I’d like to clarify why I believe the current behavior of the Save and Close button is a bug rather than intended functionality.

In most CRUD systems and admin panels, Save and Close means: save the record and return to the list view. This is also how it worked previously in my OctoberCMS implementations. The current behavior — where Save and Close redirects back to the Create page instead of the list — looks like a regression and is not intuitive for users.

Previously, when I was using a custom form view, I relied on the standard AJAX mechanism with:

data-request-data="close:1"

With this, saving and closing correctly returned to the list. Now, after switching to a configuration based on config_form, the redirectClose parameter is not respected at all. Regardless of its value, clicking Save and Close still brings me back to the Create page, exactly as described in the reproduction steps.

According to the official documentation, the redirectClose option is described as “redirection page when record is saved and the close post variable is sent with the request”. In my case the request does include close=1, but redirectClose is still ignored when using formRenderDesign(), so the behavior doesn’t match the documentation and looks like a bug.

The expected behavior would be:
• Save and Close should return to the list view (as in most systems),
• and when redirectClose is defined in config_form, it should be honored and determine the redirect destination.

[mplodowski]

Question:
Is there any way to override or add custom buttons when using formRenderDesign()?

I know how to add buttons through config_form.yaml or via formExtendFields(), but when using formRenderDesign() the buttons appear to be fully controlled by the built-in design partials (mode_basic, mode_document, mode_sidebar, etc.).

Is there an official or supported way to:
• override the buttons section used by formRenderDesign(), or
• inject additional buttons into that layout?

Right now it seems that the standard mechanisms (toolbar buttons, actionButtons, etc.) do not affect the buttons rendered inside formRenderDesign().

Any guidance or recommended approach would be appreciated.

[daftspunk]

Yes, you can create a _form_buttons.php partial in the controller directory to override the buttons.