CMS 5.2.0-beta1. Regression test: LinkField has "Draft / Modified" label even when Elemental Block was published

[sabina-talipova]

Description

Executed on: SC PHP 8.3 Chrome LinkField
Test scenario: https://studio.cucumber.io/projects/301855/test-runs/947336/folder-snapshots/11144442/scenario-snapshots/34759621/test-snapshots/46444047

After publishing block draft label won't go away, but it has been published on the front end. when the page refreshes only it will go away.

Steps to reproduce issue:

• I create a new Elemental block with LinkField;
• I create a new Link;
• I see "Draft" badge in LinkField;
• I publish the block (not a Page);
• I still see "Draft" badge in LinkField;
• I refresh the Page and then a badge disappears.

Acceptance criteria

• Manually publishing an elemental block with a owned Link relation update the status of the relevant linkfield.

PR

• FIX Update LinkField if Elemental version status was updated #268
• ENH Add element version to global state silverstripe-elemental#1161
• FIX Allow reloading react forms based on changes to a prop silverstripe-admin#1771
• FIX Reload element form when element version changes silverstripe-elemental#1200
• MNT Test publishing block updates link state #294

[sabina-talipova]

There is the similar problem for another nested versioned DataObject.
For example for files:

Update: Related issue was open silverstripe/silverstripe-asset-admin#1450

[emteknetnz]

@sabina-talipova I've closed the linked PRs because I don't think they're going about solving this the correct way. It's doing a couple of things I dislike:

• Creating a coupling between two optional modules
• Add client side form state thus creating a new source of truth. This adds complexity and can easily lead to creating regressions later on. It's FAR easier to only use the server as the source of truth.
• It's also not solving the asset-admin issue noted above which has the same symptom

Instead what I think we want to do is force the inline form (created using FormBuilder which uses redux-form) to refresh after a successful publish/unpublish so that linkfield will subsequently refresh its own data from the server.

This is non-trivial and has a pretty frustrating learning curve so feel free to move this issue back into the ready column if you don't want to tackle it