[MAGNOLIA-9127] Import of existing resource in Webapp/DAM repo does not work Created: 02/Oct/23  Updated: 11/Oct/23  Resolved: 10/Oct/23

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

Type: Bug Priority: Major
Reporter: Loris Croci Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: import, jcr, replace
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

prod


Attachments: PNG File image-2023-10-02-09-54-15-513.png    
Issue Links:
causality
duplicate
duplicates MGNLUI-8425 Import as yaml fails on Windows Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Context

  • What is the problem we’re solving? 
    Our client needs to re-enable the import of existing resources(Overwrite/Replace) directly from the desired app (Website/Dam).
  • Who are the users involved in this problem?
    Editors

Use Cases

  • As a user within Dam/Website app would like to Import resources that are already present so that I can replace them and avoid to use JCR Tools app. 
    (Especially we want to avoid to have to rethink all the user permission to let them use JCR Tools)


 Comments   
Comment by Loris Croci [ 02/Oct/23 ]

This issuse for us is linked to the already solved jira: MAGNOLIA-8961.
Thanks
Loris

Comment by Loris Croci [ 02/Oct/23 ]

Testing the online demo, export/import from content app in yaml is broken. 
Or customer is using xml not yaml.


In this screenshot i've exporter a page directly from content app, side bar, export action and tried to reimport. But it breaks.

Comment by Loris Croci [ 03/Oct/23 ]

Hello,

Would it be possible to have at least an initial feedback to share with our customer please? 
Our sprint is blocked because of this issue.

thanks a lot
Loris

Comment by Roberto Gaona [ 05/Oct/23 ]

Hello Loris,

I think this issue can be workaround with the following configuration on the upload field:

allowedMimeTypePattern: text/xml|application/x-yaml|application/octet-stream 

In any case, could I please suggest you create a ticket on the Support project to keep track of your issue?

Kind regards,

Roberto Gaona

Comment by Loris Croci [ 05/Oct/23 ]

Hi Roberto, 
Should this 

allowedMimeTypePattern: text/xml|application/x-yaml|application/octet-stream 

be added in a custom definition on the desired Pages, Dam apps?

Comment by Roberto Gaona [ 09/Oct/23 ]

Hello Loris,

It should be added to the definition of the upload field, so probably applied using a decoration to its respective app and dialog/subapp.

In any case, since there's a Support ticket created, you can just ask there any doubt you may have.

Kind regards,

Roberto Gaona

Comment by Loris Croci [ 10/Oct/23 ]

I think it is possible to close this ticket considering we have the SUPPORT one. 

Thanks a lot Roberto
Have a great day

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