magento2: Pages -> View does not work in 2.3.0

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)
...

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 16 (11 by maintainers)

Most upvoted comments

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

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

@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.