[PP]: Filter option relationships is not being respected

[erickgonzalez]

Parent Issue

We need to take care of this first #30997

Problem Statement

Despite setting the option relationships: false in the PP Filter, it continues to both send and modify relationships. This suggests that the filter is not functioning as intended, leading to unexpected behavior in how relationships are handled.

Steps to Reproduce

1. In the Sender, create a parent Content Type: Parent, and a child Content Type: Child, with a Title field
2. In the Parent type, add a Relationships Field pointing to the Child type with a many-to-many cardinality.
3. Create a Contentlet of type Child named My Child Content
4. Create a Contentlet of type Parent named My Parent Content and relate the My Child Content to it.
5. Push publish My Parent Content — the parent — to the Receiver. The Receiver must have those two new Contentlets now
6. In the Receiver, create a new Parent contentlet: My Second Parent Content, and relate the pushed My Child Content to it. So now, in the Receiver, My Child Content has two parents.
7. Go back to the Sender, and delete all Push Publishing history via the Maintenance portlet.
8. From the Sender, push publish the My Child Content now — notice that you pushed the parent Contentlet last time using the Only Selected Items filter.
9. Go to the Receiver and check both My Parent Content and My Second Parent Content — the content you manually created in the Receiver. This time, the My Second Parent Content will NOT have its reference to the My Child Content.

Acceptance Criteria

If in the filter Relationships = True:
• The Bundler should include relationship information (table tree) in the bundle.
• The Handler should clean current relationships and populate them with the data from the bundle.
If in the filter Relationships = False:
• The Bundler should exclude relationship information.
• The Handler should not modify existing relationships in the table tree, preserving the current relationships on the receiver.

We need to document this new behavior since it will affect PP globally.

dotCMS Version

23.01 LTS
Demo

Proposed Objective

Customer Success

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[github-actions]

PRs:

• fix(push publishing) fixes #30998 : Filter option relationships is not being respected #31008

[erickgonzalez]

Working as it should, now when using a PP Filter that has relationships: false it won't regenerate the relationships on the receiver.

Screen.Recording.2024-12-27.at.10.20.35.AM.mov

[erickgonzalez]

Another customer: https://dotcms.freshdesk.com/a/tickets/29250