After clicking “Save changes” in Sortableviews embedded via DynamicLocalTasks, page does not refresh to show updated order

Problem/Motivation

When Sortableviews is embedded via a dynamic local task (e.g., node/<nid>/edit/methoden), the new order is not visibly updated after saving. Although the “Save changes” button successfully updates the underlying numeric weight field and displays “Changes have been saved,” the listed items remain in their old sequence until the user manually refreshes the page.

Steps to reproduce

1. Create a View using Sortableviews that stores order in an integer field (e.g., field_weight).
2. Add a display (Block or Page) and configure:
   • Format: “Sortable table” (or “Sortable list”).
   • Weight field in the Sortableviews settings (e.g., field_weight).
   • “Sortableviews: Drag and drop handle” field.
   • A “Save Sortableviews changes” button in the header or footer.
   • (Tried with “Use AJAX” enabled and disabled, and with View caching disabled.)
3. Embed this View in a local task under node/<nid>/edit/methoden (e.g., with Dynamic Local Tasks or a custom route).
4. Navigate to that tab, reorder items by dragging, and click “Save changes.”

Expected result: The page (or view) reloads or re-renders in the new order immediately.

Actual result: “Changes have been saved.” appears, but the items remain in the old order until a manual page reload.

Proposed resolution

Implement an automatic refresh or re-render after the “Save Sortableviews changes” action completes. This could be:

• For non-AJAX submissions, a forced full page reload so the newly updated weights are reflected immediately.
• For AJAX submissions, a partial refresh or a page reload triggered by Sortableviews’ JavaScript once the reorder is saved.

Remaining tasks

• Review how Sortableviews attaches the reload logic when embedded in custom routes/local tasks.
• Determine if the module should always force a page refresh (for administrative views) or if it needs an option to enable this behavior.
• Provide a patch or inline JS solution that triggers a refresh on successful save.

User interface changes

No immediate UI design changes, but users would see the newly ordered results immediately after saving instead of needing a manual browser refresh.

API changes

None anticipated. The change is primarily about reloading or re-rendering the view after the reorder is saved.

Data model changes

None. Sortableviews already updates the numeric weight field; no changes to the schema or data structure are required.