search

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.56k stars 9.32k forks source link

Magento 2 Admin Content/Pages #17903

Closed lansy1 closed 6 years ago

lansy1 commented 6 years ago

Preconditions

  1. version 2.2.3

Steps to reproduce

1.Very simple, I login to admin and go to Content on left bar and go to under Elements / Pages. Will not load. If I go to Widgets, it will load. Blocks used to load until I put the asterisk in the search bar and hit enter. Now it does the exact same thing as the Pages page. 2.

Expected result Pages list should load. Please look at pictures carefully. I need to remove the search filter somehow.

  1. [Screenshots, logs or description] 2.https://prnt.sc/ko4012 image

Actual result

Error message is 1. [Screenshots, logs or description] 2.Error message: Something went wrong with processing the default view and we have restored the filter to it's original state.
magento-engcom-team commented 6 years ago

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

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 (2.2-develop +). For more details, please, review the Magento Contributor Assistant documentation.

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

ghost commented 6 years ago

@lansy1, please refer to the Community Forums or the Magento Stack Exchange site for advice or general discussion about this issue. The GitHub issue tracker is intended for Magento Core technical issues only, and your problem is obviously caused by some custom code.