[MGNLRES-343] Resources-app - publishing 2nd version fails Created: 26/Nov/19  Updated: 29/Mar/22  Resolved: 10/Feb/20

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

Type: Bug Priority: Neutral
Reporter: Christoph Meier Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0.25d
Time Spent: 0.1h
Original Estimate: Not Specified

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:
Sprint: UI Framework 16
Story Points: 2
Team: Nucleus

 Description   

The root cause: unlike the former implemenation, when the list of the resource nodes for publication is being populated, only the child resource nodes are queries for their publication status (the resource/folder is then picked up transitively). Apparently, when the resource/folder is attempted to be published the second time - all the children are already published and nothing is submitted for publication.

The new resources app can publish a first version of a (JCR originated) resource, but it fails to publish a 2nd version of such a resource.

To reproduce

  • Open the new resources app
  • Create the folder static within mte
  • Add the file sugus.yaml as child of the static folder above.
  • Edit the sugus.yaml and ad some content
  • Publish this 1st version of /mte/static/sugus.yaml
    • Check it on the public admin. Works fine
    • Check the status icon on the author admin. Looks good
  • Edit /mte/static/sugus.yaml again, change the resource and save
    • Check the status icon on the author admin again. Is now yellow, which is correct.
  • Try to publish this 2nd version of /mte/static/sugus.yaml
    • => This now fails.
    • Absolutely nothing happens  not even an exception is thrown.

 

 Please note we also can not test the action Restore version before this issue has been resolved.



 Comments   
Comment by Federico Grilli [ 10/Feb/20 ]

QA: works fine. Only oddity is that one can see the publication status on the public instance.

Generated at Mon Feb 12 06:49:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.