episerver / EPiServer.Labs.BlockEnhancements

Block enhancements for CMS UI.
26 stars 9 forks source link

On page editing does not update if page/block is pending publish #82

Closed hallatore closed 2 years ago

hallatore commented 3 years ago

When editing a contentArea with blocks, where the page/block is already pending a publish (Publish button is available), the on page preview of the block is not updated.

Steps to reproduce

  1. Use the on page edit
  2. Add a block to a content area
  3. See that the "Changed to be published" status is showing
  4. Note: If you edit the block again now the changes will be rendered correctly.
  5. Refresh the page (Ctrl + R)
  6. Edit the block again
  7. Notice that the block changes are not rendered on the page
hallatore commented 3 years ago

I found that it works if i go into the given version of the content. aka 123456_654321 instead of just 123456. But epi only uses the main id as long as your not viewing a specific version.

Works: /EPiServer/CMS/?language=en#context=epi.cms.contentdata:///82310_865253 Doesn't work: /EPiServer/CMS/?language=en#context=epi.cms.contentdata:///82310

barteksekula commented 2 years ago

Fixed in https://nuget.optimizely.com/package/?id=EPiServer.Labs.BlockEnhancements&v=1.0.1

hallatore commented 2 years ago

@barteksekula It's fixed in a version we can never adopt, since the project is stuck on net-framework 😭

barteksekula commented 2 years ago

Hmm, actually it does not work in 1.0.1 either. I will try to apply a proper fix in both .net core and .net framework.

evdinursan commented 2 years ago

Hi! Can you please tell me if you have any date set for the release of 0.12.1? Thank you for your time!

barteksekula commented 2 years ago

I've just checked and the package has already gone through our QA process and it's already waiting in the release queue which means it should be public around tuesday next week.

barteksekula commented 2 years ago

https://nuget.optimizely.com/package/?id=EPiServer.Labs.BlockEnhancements&v=0.12.1 is out this bugfix will also be available in 1.0.2 which will be out soon