[MAGNOLIA-7274] Automatic publication of images on upload Created: 06/Mar/18  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Critical
Reporter: Marcus Käppi Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLDAM-745 Auto publish assets when used Closed
causality
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: Publishing Page related content

 Description   

Problem Description:

The upload function is only accessible through the asset library, not in the editorial view on the site. This is a problem that didn't appear in Mag4 where you could publish the images directly in combination of adding them to an element.

The most common method for uploading pictures is today for the editors to do it in the different modals where they also add the pictures. Since the pictures isn't automatically published they have to switch to the asset view and search for the images in order to publish the pictures. This leads to an unnecessary step in the publication process and the time of the actions adds up. One of our most common mistakes is also that we publish a page without published pictures. These problems are usually noticed directly but are still an annoyance.
 

Possible solution:

extend DAM-dialog with prechecked upload option.
With a javaclass to check checkbox and activate images to public



 Comments   
Comment by Natascha Natum [ 13/Apr/18 ]

I would suggest to switch the asset's status to published as soon as the page/story containing that asset is published instead of extending the DAM dialog.

Comment by Richard Gange [ 10/Mar/21 ]

jayala this won't be handled by us. In the observation module there is an example of how to publish pages automatically. Let's try and explore a custom solution with them.

Closing as Won't Do

Generated at Mon Feb 12 04:22:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.