Magento2: Pages -> View does not work in 2.3.0

[beltran-rubo]

Preconditions (*)

1. Install Magento via CLI using the "developer" mode
2. Reindex & flush cache

Steps to reproduce (*)

1. Magento 2.3.0
2. Go to Pages -> Select one -> Click on View

Expected result (*)

1. Show the Magento page in the browser

Actual result (*)

1 exception(s):
Exception #0 (Magento\Framework\Exception\NoSuchEntityException): No such entity with id = 0

Exception #0 (Magento\Framework\Exception\NoSuchEntityException): No such entity with id = 0
#0 /htdocs/vendor/magento/module-catalog/Model/CategoryRepository.php(141): Magento\Framework\Exception\NoSuchEntityException::singleField('id', '0')
#1 /htdocs/vendor/magento/module-catalog/Model/Layer.php(202): Magento\Catalog\Model\CategoryRepository->get('0')
#2 
/htdocs/generated/code/Magento/Catalog/Model/Layer/Category/Interceptor.php(76): Magento\Catalog\Model\Layer->getCurrentCategory()
#3 /htdocs/vendor/magento/module-catalog/Plugin/Block/Topmenu.php(146): Magento\Catalog\Model\Layer\Category\Interceptor->getCurrentCategory()
#4 /htdocs/vendor/magento/module-catalog/Plugin/Block/Topmenu.php(79): Magento\Catalog\Plugin\Block\Topmenu->getCurrentCategory()
#5 /htdocs/vendor/magento/framework/Interception/Interceptor.php(121): Magento\Catalog\Plugin\Block\Topmenu->beforeGetHtml(Object(Magento\Theme\Block\Html\Topmenu\Interceptor), 'level-top', 'submenu', 0)
...

[magento-engcom-team]

Hi @beltran-rubo. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@beltran-rubo do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

[beltran-rubo]

@magento-engcom-team give me 2.3 instance

[magento-engcom-team]

Hi @engcom-backlog-nazar. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [x] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [x] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [x] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [x] 6. Add label Issue: Confirmed once verification is complete.

• [x] 7. Make sure that automatic system confirms that report has been added to the backlog.

[ghost]

Hi @beltran-rubo i'm not able to reproduce following steps your described, only 2.2.0+ bug reports are considered nowadays. Try upgrading.

[beltran-rubo]

@engcom-backlog-nazar sorry, the version was wrong in the title. This happen in the new 2.3.0 (and not in the previous versions)

[ghost]

@beltran-rubo ok, i'm will retest

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97038 were created

[magento-engcom-team]

Hi @eduard13. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• [x] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[nathanjosiah]

This is a duplicate of internal issue MC-5461. This issue will be fixed in 2.3.1

[eduard13]

@nathanjosiah thank you for letting me know, I won't continue with this one then.

[nathanjosiah]

No problem, we have a fix that should be merged into 2.3-develop within the next week

[jignesh-baldha]

@nathanjosiah I've got a fix which solved this issue, May I create PR now?

[magento-engcom-team]

Hi @jignesh-baldha. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

• [x] 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [x] 2. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [x] 3. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

[nathanjosiah]

@jignesh-baldha Thank you for investigating this issue. We have a fix internally that will be merged into 2.3-develop within the next few business days.

[sdzhepa]

Hello @beltran-rubo @eduard13 @jignesh-baldha

This issue was fixed in the scope of internal ticket MC-5461
The fix should be available for 2.3.1 (curently in 2.3-develop)
Please, see commits for more details:

• d6f7d244fffade4764afb53fc0d4b932f5b180a1
• 25473b75ed223ed37cd677dfa34cc3ac4946bd2a

This ticket can be closed.
Please, feel free to reopen or create a new one if issue still exists or was not fully fixed

Thank you for feedback and collaboration

[AsadKhan95]

I'm getting the same issue in M 2.2.10. While when I add new page then it gives me the above error while when I apply the page then it gives me nothing in the frontend.
https://magento.stackexchange.com/questions/292523/adding-new-page-in-admin-giving-error-magento2
here is the link for more information kindly sort it out or if it is any issue coz of me then let me know thanks