-
Bug
-
Resolution: Obsolete
-
Neutral
-
None
-
2.4.1, 2.5
-
None
-
None
Let's suppose you have a folder containing assets with a version/s that were published separately and therefore contains the "lastActivated" and the "lastActivatedVersionCreated" properties.
If you move such a folder and then you click "Publish incl. subnodes", the status icons of the assets with version/s will turn yellow, even though they are correctly published to the public instance. In contrast, the assets without version/s are also published, but show the green icon.
In this case unpublishing and re-publishing incl. subnodes doesn't help. To see have the assets with version/s green, you have to publish all of them separately.
This will update the above-mentioned properties and the status icons will then work correctly for all the actions you do. However, only until you move the folder again.
Steps to reproduce:
- open the "Assets" appÂ
- create a folder and upload some images into (you can also import this testing structure via JCR Tools app: dam.TestFolder.xml)
- publish the folder
- publish some of the assets in the folder separately
- publish the rest of the assets by "Publish incl. subnodes" (the folder and all assets have a green status icon)
- move the folder to some other place (status icons of the folder and all assets change to yellow)
- click "Publish incl. subnodes" ->Â Assets without version - green status icon. Assets with version -> incorrect yellow icon.
- publish the assets with version separately - it updates properties of the assets and status icons start to display correctly (unpublishing and re-publishing incl. subnode have no effect and icons are still incorrect)
- be happy that it works now  ... but not for too long... move the folder again to some other place -> it throws you back to point 6
- is duplicated by
-
PUBLISHING-82 Wrong order of nodes after publishing single page
- Closed
- is related to
-
MGNLUI-5257 Provide push support in Admincentral
- Closed
-
PAGES-310 Refresh status column indicators in the background when doing asynchronous activation
- Closed