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

Apply button won't save changes to part config after the content is published or marked as ready #1428

Closed
poi33 opened this issue Jan 21, 2020 · 0 comments
Assignees
Labels
Bug Something isn't working
Milestone

Comments

@poi33
Copy link
Contributor

poi33 commented Jan 21, 2020

Community Ref: https://enonic-community.slack.com/archives/C73JLM8E7/p1579609641021400

Reported in 7.1.2 and 7.2.0
Content studio version 2.3.0

Pressing the apply button does not update the data in the right column, and it goes back to previus data.
Work around: refresh page and pressing apply again.

To reproduce:

  1. Select any part on a page that has config
  2. Mark the content as ready or publish
  3. Click the part that has the config
  4. Make changes
  5. Press Apply button

The panel is refreshed, changes are not saved.

@poi33 poi33 added the Bug Something isn't working label Jan 21, 2020
@alansemenov alansemenov changed the title Apply sometimes resests the content on the right column. Applying changes to part config after the content is published or marked as ready won't save the changes Jan 21, 2020
@alansemenov alansemenov changed the title Applying changes to part config after the content is published or marked as ready won't save the changes Apply button won't save changes to part config after the content is published or marked as ready Jan 21, 2020
ashklianko added a commit that referenced this issue Jan 27, 2020
…ublished or marked as ready #1428

-Issue with comparing components
ashklianko added a commit that referenced this issue Jan 27, 2020
…ublished or marked as ready #1428

-Issue with comparing components
@alansemenov alansemenov added this to the 2.3.2 milestone Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants