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

Sync Resources does not synchronize license description #4916

Open
bjester opened this issue Feb 21, 2025 · 0 comments
Open

Sync Resources does not synchronize license description #4916

bjester opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
DEV: backend P0 - critical Priority: Release blocker or regression

Comments

@bjester
Copy link
Member

bjester commented Feb 21, 2025

Background

  • Certain fields related to authoring and licensing are not editable on imported content, and we performed a migration in concert when that became enforced recently
  • The Sync Resources feature synchronizes various fields on imported content, such as those related to authoring and licensing
  • Previously, we migrated the aforementioned fields to be synchronized with their source content, and thereafter disallowed editing of the fields.

Observed behavior

A user who imported source content into their channel that was incomplete at the time, and then resolved the incomplete issues blocking publishing, are now unable to publish that content if the content's incomplete issue was resolved in the source channel and related to license_description. In short, the license description is not synchronized from source content but should be, and the user is blocked as it is no longer editable on copies of the content.

Expected behavior

The Sync Resources feature should synchronize the license_description field from source content. If the source content is publishable, copies of the content should also be publishable, even if the copy originated from a time when the source wasn't publishable.

User-facing consequences

A user is forced to re-import the affected resources in order to workaround the issue. Although, if the user had previously edited the fields to resolve the issue themselves, we're at least now ensuring licensing fields are not subject to that.

Additional information

Ask @bjester for any channel IDs or examples

@bjester bjester added DEV: backend P0 - critical Priority: Release blocker or regression labels Feb 21, 2025
@rtibbles rtibbles self-assigned this Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DEV: backend P0 - critical Priority: Release blocker or regression
Projects
None yet
Development

No branches or pull requests

2 participants