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.