Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manage Publication button breaks cac publishing flow #49

Open
satzlinger opened this issue Nov 18, 2024 · 1 comment
Open

Manage Publication button breaks cac publishing flow #49

satzlinger opened this issue Nov 18, 2024 · 1 comment

Comments

@satzlinger
Copy link

satzlinger commented Nov 18, 2024

Steps to reproduce:
I start off with no sling context aware configuration
2024-11-18_14-14

Create sling context aware configuration.
Save
Use quick Publishing.
Publish dialog appears with my caconfiguration selected
2024-11-18_14-15
Publish
Configuration is properly replicated to the publishing instance.
Values can be changed, saved and quick published and it consistently works
2024-11-18_14-15_1

Change value of a sling context aware configuration

Save
use Manage Publication
2024-11-18_14-16_2

Configuration content is not properly replicated to the publish instance.
The properties cq:lastReplicated and cq:lastReplicated_publish have the timestamp when the manage publication button was pressed on author but the cq:lastReplicated_publish on publisher is not changed and shows the timestamp from the quick publish process before.
Quick publish button now does not show the Publish dialog where the node can be seen, but just shows the "Configuration Editor The page has been published, Close" Dialog. No publishing was done.
2024-11-18_14-12_2

Locally I was only able to get the quick publishing button working again by deleting the configuration node and creating a new one.
I can not see anything suspicious in the author, publish or replication log

Would be great if someone can look into this

@stefanseifert
Copy link
Member

thanks for the detailed report! - i will try to reproduce the issue.

from time to time it may break if something changes inside the AEMaaCS product under the hood.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants