Open rvr-robert opened 2 years ago
@magento run all test
Failed to run the builds. Please try to re-run them later.
@magento run all tests
The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.
@magento run all tests
Hello @rvr-robert @jeremycharron,
Thanks for the contribution!
Can you please help us understand the need to update the database in order to reproduce the issue? I think this is not the correct way to produce an issue. Can we reproduce the issue without this?
Thanks
Hello @rvr-robert @jeremycharron,
Thanks for the contribution!
Can you please help us understand the need to update the database in order to reproduce the issue? I think this is not the correct way to produce an issue. Can we reproduce the issue without this?
Thanks
Hi @engcom-Hotel The real concern would be when you are creating a CMS block and assigning it to a page programmatically (in a data patch for example). You'd want the created page to use the same block identifier on every environment the patch is ran. Editing the database directly is just a quick way to replicate the issue without writing a fictional data patch.
Thanks
@magento run all tests
Description (*)
When adding a CMS block in a CMS page using the block identifier instead of the block ID, pagebuilder displays following error : "Block with ID: [block identifier] doesn't exist." instead of showing preview of the CMS block.
The block renders properly on front-end. There is no way to add a block with his identifier directly from pagebuilder. This issue would only happen if a developer executes a data patch that generates CMS content or directly edit the content in the database.
Bug
Fixed Issues (if relevant)
Manual testing scenarios (*)
Checklist