404 error when attempting to change any product attribute settings in admin panel

[diamondavocado]

Preconditions (*)

1. Magento 2.3.0, data imported from Magento 1.9 using the migration tool
2. Centos 7, Apache, php-fpm

Steps to reproduce (*)

1. Visit Admin panel -> Stores -> Attribute -> Products
2. Choose an attribute (in my case "Size")
3. Note the URL is https://example.com/admin/catalog/product_attribute/edit/attribute_id/200/ at this stage
4. Try to change any setting (e.g. Catalog Input Type -> Dropdown)
5. Hit "Save" or "Save and Continue" to save your changes

Expected result (*)

1. Attribute should be saved with new settings
2. Page should reload to the same URL (https://example.com/admin/catalog/product_attribute/edit/attribute_id/200/)

Actual result (*)

1. Page makes a POST request with all the settings data to https://example.com/admin/catalog/product_attribute/validate/attribute_id/200/?isAjax=true but it seems that request gets a blank/empty response?
2. Page then reloads to different URL https://example.com/admin/catalog/ which results in a 404 error
3. Changes are not saved to the attribute

Please note I have tried clearing (and disabling) all caches, indexes, deployed static content, checked file/folder permissions, etc. and this is still happening.

At least some other parts of the admin panel DO save correctly.

[m2-assistant]

Hi @diamondavocado. 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 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

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

• yes
• no

[orlangur]

This is similar to #22224 and a bunch of other issues, should be pretty straightforward to fix.

[m2-assistant]

Hi @shikhamis11. 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: 👇

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

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

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

• 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

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

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

[shikhamis11]

hi @diamondavocado
thank you for your report .. this issue is not reproduceable at magento 2.3-develop instance

[diamondavocado]

I updated to 2.3.1 and the attribute options are now showing in the dropdown format on the front-end, however the back-end (admin panel) still reports the attribute as being a Text Swatch:

Any ideas as to why this is happening, if you can't replicate it?

[shikhamis11]

Hi @diamondavocado
I checked at 2.3.1 instance . It is working fine. expect once I changed the Catalog Input Type for Store Owner to dropdown from Text Swatch or vice versa from backend you need flush FPC .

[shikhamis11]

hello @diamondavocado I am closing this issue since I am not able to reproduce this issue. message here if you think this issue exists on magento 2.3-develop instance