cancel
Showing results for 
Search instead for 
Did you mean: 

Problem trying to change Advanced Attribute Properties

Problem trying to change Advanced Attribute Properties

Hello,

 

I'm trying to change the Advanced Attribute Properties for quantity_and_stock_status and set Add to Column Options and Use in Filter Options to Yes, but the loader pops up and nothing happens, it loads endlessly.

 

Any idea on how to fix this please ?

 

Or a way to change this directly with phpmyadmin.. ?

 

I'm using latest Magento 2.1.7.

 

Best regards,

David

3 REPLIES

Re: Problem trying to change Advanced Attribute Properties

@ShapesGS

Have you check this type of problem available for all other attributes or just problem to this attribute only.

You can just run command
`php bin/magento setup:static-content:deploy`

Remove var folder and clear cache.

If problem still exist you have to check console of that page any js error are saw.

Correct js error if anyone exist.

If Its Default bug then you can close this question after accept your answer.
If solution was helpful, click kudos to answer.

If Issue Solved, Click Kudos/Accept As solutions.

Re: Problem trying to change Advanced Attribute Properties

I'm also encountering this issue. I've recompiled, updated database, etc. But still no change in issue. Exactly as OP describes. Changing quantity_and_stock_status value for "Add to Column Options" from "No" to "Yes"...

 

...at this time error is  received, see image below.

 

POST 500 internal server error "https://DOMAIN.COM/admin/catalog/product_attribute/validate/attribute_id/115/key/d4829739f3b1cb4a68f..."

 

Uncaught TypeError: this.trigger is not a function (validation.js:205)

 

500 internal server error "https://DOMAIN.COM/admin/catalog/product_attribute/validate/attribute_id/115/key/d4829739f3b1cb4a68f268e38bba4e3b29441f48120194d11bf010bf71616e88/?isAjax=true"

Re: Problem trying to change Advanced Attribute Properties

For what I tried, I only got this problem with quantity_and_stock_status attribute.

 

The bug has been reported, I hope they will fix this soon :

https://github.com/magento/magento2/issues/9552#issuecomment-311358527