You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/assets.md
+16-19
Original file line number
Diff line number
Diff line change
@@ -214,25 +214,26 @@ Last updated: 3rd April 2025
214
214
**How to reproduce:**
215
215
216
216
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
219
219
220
220
**What happens:**
221
221
222
-
1. Attachment preview is redirected
222
+
* Attachment preview is redirected
223
223
224
224
**Expected:**
225
225
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
228
228
229
229
**Suggested Support Fix:**
230
230
231
231
* 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.
232
232
* 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.
233
233
234
234
**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.
236
237
237
238
---
238
239
@@ -241,32 +242,28 @@ Having a draft stack for attachments will help. If we duplicate assets for draft
241
242
**How to reproduce:**
242
243
243
244
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
248
249
249
250
**What happens:**
250
251
251
-
1. Attachment returns not found
252
+
* Attachment returns not found
252
253
253
254
**Expected:**
254
-
255
-
1. Attachment should be made live again upon publish
255
+
* Attachment should be made live again upon publish
256
256
257
257
**Suggested Fix:**
258
258
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
262
260
263
261
### Current unsupported workflows
264
262
Last updated: 3rd April 2025
265
263
266
264
We currently don't support official UI workflow for doing the following.
267
265
268
-
- Redirect individual attachments
266
+
-Unpublish / Redirect individual attachments
269
267
- For HTML attachments, rake task `publishing_api:redirect_html_attachments:by_content_id`
0 commit comments