Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

A problem of Manage Categories #51

Closed
SunshineTech opened this issue Jul 26, 2012 · 9 comments
Closed

A problem of Manage Categories #51

SunshineTech opened this issue Jul 26, 2012 · 9 comments

Comments

@SunshineTech
Copy link

In a store view, when I modify some attributes, I must No checked "Use Default Value" of "Available Product Listing Sort By" and "Default Product Listing Sort By", or I can't succeed to modify these attributes. But after I No checked these and succeed to modify the category, "Use Default Value" of "Default Product Listing Sort By" is checked! At the most worse, I can't check "Use Default Value" of "Available Product Listing Sort By" again for ever!
@magento-team
Copy link
Contributor

@SunshineTech
Thank you for the bug report. However, we've experienced difficulties in reproducing the issue. Could you please provide more details in the following format:

  1. "Steps to reproduce" -- consecutive steps of what should be done to reproduce an issue
  2. "Expected result" -- what is considered to be a correct behavior
  3. "Actual result" -- what is in fact happening instead of a correct behavior

There are quite a few bugs in the Magento 2, some are more, some are less critical than others. In order to increase the chances of fixing the issue sooner, the pull request with actual fix and corresponding automated tests (unit or integration) is greatly appreciated.

@SunshineTech
Copy link
Author

Steps to reproduce:

  1. Click "Manage Categories" menu, then select a store view and a root or sub category.
  2. Modify some attributes, then "Save Category". In the "Display settings" tab, I apply(check) "Use Default Value" on the "Available Product Listing Sort By *" and "Default Product Listing Sort By *".
  3. Then a error is display: Attribute "Available Product Listing Sort By" is required.
  4. I had to No check "Use Default Value" on the "Available Product Listing Sort By *". Then "Save Category".
    5.This time other error is display: Attribute "Default Product Listing Sort By" is required.
    6.I had to No check "Use Default Value" on the "Default Product Listing Sort By *". Then "Save Category".
    7.This time I save the modify. But "Use Default Value" of "Default Product Listing Sort By" is checked!
    8.Then I check "Use Default Value" of "Available Product Listing Sort By" and "Save Category", the first error is display: Attribute "Available Product Listing Sort By" is required.

Expected result:
I want to modify the others attributes, and apply(check) "Use Default Value" on the "Available Product Listing Sort By *" and "Default Product Listing Sort By *".

Actual result:
I can't apply(check) "Use Default Value" on the "Available Product Listing Sort By *" .

@SunshineTech
Copy link
Author

In the Magento v1.7, there isn't the problem.

@yazalpizar
Copy link

Using Magento v1.7.0.2 and I'm having exacly same problem as described by SunshineTech. There is no way I can save a new subcategory. I have always either the [Attribute Available Product Listing Sort By" is required or if I select a different sort by on the "Default Product Listing Sort By" it throws Default Product Listing Sort by not exists on Available Product Listing Sort By.

@magento-team
Copy link
Contributor

@SunshineTech , thank you for the bug report. The issue is fixed and will be available on GitHub with one of the next updates.

@yazalpizar
Copy link

And when will this fix be available? Is really stopping us from going ahead on the development. Is the fix available somewhere as a patch, fork or alike?

@magento-team
Copy link
Contributor

@yazalpizar , it should be available till the end of this week.

@yazalpizar
Copy link

Great! thanks...

magento-team added a commit that referenced this issue Sep 14, 2012
@magento-team
Update as of 9/13/2012
da072ba 
* Implemented the option to enable the single store mode in the system configuration, which simplifies the back-end GUI:
  * Hiding scope labels from the system configuration
  * Hiding the scope switcher from the CMS management pages and the system configuration
  * Hiding scope related fields from the system configuration
  * Hiding scope related columns and fields from the sales pages (order, invoice, shipment pages)
  * Hiding scope related fields from the promotions
  * Hiding scope related fields from the catalog pages
  * Hiding scope related columns and fields from the customers management page
  * Hiding scope related columns and fields from the customer and customer address attributes management pages
* Implemented the history management for the Visual Design Editor
* Implemented the user interface for themes management, which allows to list existing themes and add new ones
* Replaced all usages of the old JavaScript translations mechanism with the new jQuery one
* Refactored methods with high cyclomatic complexity
* Converted some surrogate integration tests into functional Selenium tests
* Converted some surrogate integration tests into unit tests
* Fixes:
  * Fixed inability to install application with a prefix defined for database tables
  * Fixed displaying fields with model name in the payment methods settings
  * Fixed performance degradation of the back-end menu rendering
  * Fixed absence of the success message upon newsletter template creation/deletion/queueing
  * Workaround for occasional segmentation fault in integration tests caused by `Mage_Core_Model_Resource_Setup_Migration`
* GitHub requests:
  * [#51](#51) -- fixed managing of scope-spefic values for Categories
  * [#56](#56) -- removed excessive semicolon in the CSS file
  * [#60](#60) -- fixed taking bind parameters into account in `Mage_Core_Model_Resource_Db_Collection_Abstract::getAllIds()`
  * [#61](#61) -- relocated declaration of the "Google Checkout" payment method into `Mage_GoogleCheckout` module from `Mage_Sales`
@anilrmg
Copy link

anilrmg commented Dec 16, 2013

I have upgraded magento enterprise 1.12.0.2 to 1.13.0.2 and now getting same error as @SunshineTech , Can you please specify changed files for this issue and i have search in repository but not able to find changes by issue id #51

@leeyisoft leeyisoft mentioned this issue Jun 14, 2014
Closed
magento-team pushed a commit that referenced this issue Jan 23, 2015
@vpelipenko
Merge pull request #51 from magento-extensibility/develop
cc38a64 
[Extensibility] Eliminate Remnants of the Core Module (External Dev)
@stevieyu stevieyu mentioned this issue Apr 3, 2015
Closed
@pccomfrank pccomfrank mentioned this issue Jun 2, 2015
Closed
@vinhtrau vinhtrau mentioned this issue Jul 4, 2015
Closed
@sivajik34 sivajik34 mentioned this issue Jul 13, 2015
Closed
@ljrweb ljrweb mentioned this issue Sep 9, 2015
Closed
@LifeAsBook LifeAsBook mentioned this issue Sep 10, 2015
Closed
@chrom chrom mentioned this issue Oct 7, 2015
Closed
@cfcnn cfcnn mentioned this issue Oct 11, 2015
Closed
okorshenko pushed a commit that referenced this issue Oct 29, 2015
Merge pull request #51 from magento-folks/merchant_beta
ea0362a 
[Folks] Bugfixes
@chaluvadiswamy chaluvadiswamy mentioned this issue Nov 3, 2015
Closed
This was referenced Nov 22, 2015
Closed
Closed
@thomvanderboon thomvanderboon mentioned this issue Nov 29, 2015
Closed
@jiramlopez jiramlopez mentioned this issue Dec 3, 2015
Closed
@viktor-zhuromskyy viktor-zhuromskyy mentioned this issue Dec 3, 2015
Closed
@oaramis oaramis mentioned this issue Dec 22, 2015
Closed
@Git-Rajkumar Git-Rajkumar mentioned this issue Jan 23, 2016
Closed
@wcldharamveer wcldharamveer mentioned this issue Jan 9, 2018
Closed
@kamal7606 kamal7606 mentioned this issue Feb 12, 2018
Closed
@primzonltd primzonltd mentioned this issue Feb 12, 2018
Closed
@forwells forwells mentioned this issue Mar 28, 2018
Closed
@deepak956 deepak956 mentioned this issue Apr 26, 2018
Closed
@ghost ghost mentioned this issue May 3, 2018
Closed
@Jaydeepjd Jaydeepjd mentioned this issue May 22, 2018
Closed
@sabl0r sabl0r mentioned this issue Aug 14, 2018
Closed
magento-engcom-team pushed a commit that referenced this issue Aug 17, 2018
@vital-pantsialeyeu
Merge pull request #51 from magento-epam/EPAM-MAGETWO-91620
8db43e7 
Epam magetwo 91620
@albsa albsa mentioned this issue Sep 26, 2018
Closed
@Microguru Microguru mentioned this issue Sep 27, 2018
Closed
@pskigen pskigen mentioned this issue Dec 14, 2018
Closed
@lfluvisotto lfluvisotto mentioned this issue Apr 7, 2019
Closed
@rafaalvescit rafaalvescit mentioned this issue Apr 18, 2019
Closed
@webspeaks webspeaks mentioned this issue May 14, 2020
Closed
@primafair primafair mentioned this issue Nov 2, 2020
Closed
@mohanwbsofttech mohanwbsofttech mentioned this issue Dec 30, 2020
Closed
@eBusinessAtlantique eBusinessAtlantique mentioned this issue May 20, 2021
Closed
@jpillai88 jpillai88 mentioned this issue May 21, 2021
Closed
@shinkhantmaung shinkhantmaung mentioned this issue Jun 20, 2021
Closed
@ghost ghost mentioned this issue Jun 28, 2021
Closed
1 task
@chequille chequille mentioned this issue Aug 20, 2021
Closed
5 tasks
@jorgb90 jorgb90 mentioned this issue Apr 29, 2022
Closed
5 tasks
@mohammedTBB mohammedTBB mentioned this issue Sep 7, 2022
Closed
5 tasks
@mohammedTBB mohammedTBB mentioned this issue Sep 15, 2022
Closed
5 tasks
@kisfelix kisfelix mentioned this issue Apr 4, 2023
Closed
5 tasks
@Hexmage Hexmage mentioned this issue Jul 11, 2023
Closed
5 tasks
@KhanBadshah588 KhanBadshah588 mentioned this issue Oct 6, 2023
Closed
5 tasks
Closed
5 tasks
@iranimij iranimij mentioned this issue Nov 21, 2023
Closed
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yazalpizar @anilrmg @magento-team @SunshineTech