Dear Sir/Madam,
I have a page containing a View block, everything goes well, I change the filter to the View but it doesn't effective until I edit the page and update it once. Is it true the View would be updated if I don't update the page manually?
Best regards,
Kelvin.
Hi Kelvin,
Your observation is correct and as expected.
When working with the blocks-based view, the changes to the view are saved when the page as a whole is saved using the "Update" button.
If you'll make some changes to the view, but leave the page edit screen without clicking the "Update" button, those changes won't be saved.
regards,
Waqar
Dear Waqar,
I mean I have to save the page every time after I change the View, is it only applied on blocks-based view, or I should use shortcode to embed the Views?
I do remember I didn't need to save the page if I change the Views before the WP implement the Block Editor.
Best regards,
Kelvin.
Thanks for writing back.
The workflow and saving method is different when it comes to the blocks-based editor.
In classic/legacy views, a view is created and managed using an independent view editor screen and then placed on the desired page/post. The actual view doesn't actually reside on the page/post where it is placed, therefore, any changes that are made on the view's editor automatically reflects on the page/post where it is shown.
In the case of the blocks-based views, there is no independent view editor screen. The view is created and managed on the same page/post where it needs to be shown. For this reason, if you're making changes to a block-based view, you'll have to save/update the page/post which contains it, so that the changes can be saved. And that behaviour is not limited to Views blocks or Toolset blocks. You'll notice the same for all blocks available in the blocks editor (Gutenberg) environment. As a quick test, you can create a new page and add a simple paragraph block with some text. After the page is saved, make some changes to that text again and without saving the page close the page editor. You'll see that the unsaved changes won't be shown on the front-end.
If you still feel my explanation doesn't cover the scenario that you're reporting and there is still something off, you're welcome to share the specific steps, so that I can reproduce what you mean.
