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

Bug with relations for siblings in online project not updated #805

Closed
tobias-karrer opened this issue Sep 17, 2024 · 1 comment
Closed

Comments

@tobias-karrer
Copy link

tobias-karrer commented Sep 17, 2024

Setup: There are two container pages that are siblings of each other: sibling1 and sibling2 - both pages contain contents and are published.

After adding a new content resource on sibling1 and publishing the page, sibling2 will be published automatically as well.
But reading relations for the content resource in online project doesn't return relation to sibling2.

Even after changing the same content resource on sibling2 and publishing the page, the relations for the content resource in online project doesn't return relation to sibling2:
image
image

Problem is database table CMS_ONLINE_RESOURCE_RELATIONS is not updated, even though sibling2 was published automatically (as it is sibling of sibling1)

Only after editing and publishing sibling2 explicitely both siblings are list on next content resource change publishing.
image

Looks like it is related to this bug here: #797

gWestenberger added a commit that referenced this issue Sep 27, 2024
After changing the links in an XML content and publishing it without its
siblings, the siblings would previously show up as unchanged in the
Explorer despite the fact that their relations have been changed to
reflect the changed content. This has been changed so that both
unpublished siblings will have the 'changed' state and need to be
published.
@tobias-karrer
Copy link
Author

As far as I can see the bug still exists - see new ticket #806

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

No branches or pull requests

2 participants