Store the Conductor content ID so the draft/data can be restored

Created on 17 September 2025, 27 days ago

Problem/Motivation

When a user has used the Conductor application to generate content, a draft is created in their Conductor account. When they close the extension and then come back to it for the same piece of content, the draft should be loaded into the application with all relevant fields filled with their previously entered data.

Need to associate the Conductor Draft ID with the piece of content it’s being used on

Proposed resolution

We associate the draftId with the node_id in a new table. On every page load, the backend will put the draftId in drupalSettings.conductor.draftId (or a better place) so the client (javascript) is able to load all the draft in the different table using the Writing Assistant Draft API.

πŸ“Œ Task
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ͺπŸ‡ΈSpain isholgueras

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024