Admin contexts

[akelch]

Description

In Admin, context handling for Fluidpage / Fluidpagecontent is unreliable.

There are repeated cases where content elements switch Fluidpages or disappear, likely caused by incorrect context propagation in the Admin.

Expected Behavior

• Content remains assigned to the correct Fluidpage.
• Saving does not change the assigned page unintentionally.
• Context is only applied where explicitly intended.
• No leakage of stale or unrelated context into other views.

Observed Behavior

Content appears to move or becomes untraceable.

Example scenario:

1. Open a Fluidpage.
2. Add a content element (do not save).
3. Open another Fluidpage.
4. Save the element.
5. Element is not visible on either page.

The issue is not reliably reproducible and appears random.

Technical Notes

• Context is currently bound via handlerID in the route.

• This breaks when multiple handlers (e.g. EditViews, relational contexts) are involved.

• The main module context may be incorrectly reused.

• No clear rules exist for:

  • context propagation
  • context reset
  • form preselection handling

Acceptance Criteria

• Context propagation is clearly defined and scoped.
• No unintended context leakage between handlers/views.
• Fluidpagecontent cannot switch pages due to context issues.
• Context can be inspected and reset where needed.
• Behavior is consistent and reproducible.