Skip to content

Commit 87d988e

Browse files
authored
Merge pull request #10127 from alphagov/documentation-for-assets
Amend assets documentation
2 parents 6dc8963 + 61e18f9 commit 87d988e

File tree

1 file changed

+16
-19
lines changed

1 file changed

+16
-19
lines changed

docs/assets.md

+16-19
Original file line numberDiff line numberDiff line change
@@ -214,25 +214,26 @@ Last updated: 3rd April 2025
214214
**How to reproduce:**
215215

216216
1. Unpublish an edition that has an attachment
217-
2. Create a new draft
218-
3. Preview the attachment
217+
1. Create a new draft
218+
1. Preview the attachment
219219

220220
**What happens:**
221221

222-
1. Attachment preview is redirected
222+
* Attachment preview is redirected
223223

224224
**Expected:**
225225

226-
1. Draft Attachment should be previewable
227-
2. Live attachment should still be redirected
226+
* Draft Attachment should be previewable
227+
* Live attachment should still be redirected
228228

229229
**Suggested Support Fix:**
230230

231231
* There is currently no fix. If we make the asset state `draft` in asset-manager, then any previous asset in the replacement chain (if it exists) will become live, which might not be what the user wants.
232232
* One thing we can do is to check whether or not the attachment users want to preview is not a replacement of any prior assets. We can do this by double checking in both Asset in Asset Manager and AttachmentData in Whitehall that no other assets are replaced by this target attachment. If that is the case, we should be able to set the state of the asset to `draft` in Asset Manager which should enable preview for the user.
233233

234234
**Suggested Permanent Fix:**
235-
Having a draft stack for attachments will help. If we duplicate assets for draft, then it won't affect anything live.
235+
236+
* Having a draft stack for attachments will help. If we duplicate assets for draft, then it won't affect anything live.
236237

237238
---
238239

@@ -241,32 +242,28 @@ Having a draft stack for attachments will help. If we duplicate assets for draft
241242
**How to reproduce:**
242243

243244
1. Unpublish an edition with attachment
244-
2. Create new draft
245-
4. Discard the draft
246-
5. Create new draft
247-
6. Publish the draft
245+
1. Create new draft
246+
1. Discard the draft
247+
1. Create new draft
248+
1. Publish the draft
248249

249250
**What happens:**
250251

251-
1. Attachment returns not found
252+
* Attachment returns not found
252253

253254
**Expected:**
254-
255-
1. Attachment should be made live again upon publish
255+
* Attachment should be made live again upon publish
256256

257257
**Suggested Fix:**
258258

259-
1. Reset redirect url and / or deleted_at in Asset Manager for the appropriate asset to bring it back
260-
261-
--
259+
* Reset `redirect url` and / or `deleted_at` in Asset Manager for the appropriate asset to bring it back
262260

263261
### Current unsupported workflows
264262
Last updated: 3rd April 2025
265263

266264
We currently don't support official UI workflow for doing the following.
267265

268-
- Redirect individual attachments
266+
- Unpublish / Redirect individual attachments
269267
- For HTML attachments, rake task `publishing_api:redirect_html_attachments:by_content_id`
270268
- For file attachments, manage in asset manager
271-
- Withdraw individual HTML attachments
272-
- Unpublish individual HTML attachments
269+
- Withdraw individual HTML attachments

0 commit comments

Comments
 (0)