-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Cannot edit/add Products in Magento 2.1.0-rc2 #5002
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.
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
Comments
Hi @bh-ref can you provide more details? What type of product, what fields/values were you loading? I haven't been able to reproduce your error. |
this might possible be storeview related, seeing the same message in 2.0.x when trying to import/export data through the admin backend in a setup with a DE & FR storeview. |
Hi @choukalos the problem appears with all product types. I use an attribute set with these attributes in it:
When I want to create a product with these attributes, it fails with the error message "No data to save". We are using two storeviews, a French and a German one, like @heldchen mentioned. I listed the loaded layout files above because I noticed that the file |
The error message "No data to save" is generated inside https://github.com/magento/magento2/blob/2.1.0-rc2/app/code/Magento/Catalog/Controller/Adminhtml/Product/Save.php if |
Hi @bh-ref Could you clear browser cache and Magento cache and try again? Thanks, |
Hi @katmoon I cleared the browser and the Magento cache, but unfortunately, the problem is still there. |
Hello @bh-ref |
Hi @mslabko I upgraded using the instructions listed under section "Upgrade using the command line" at http://devdocs.magento.com/guides/v2.0/release-notes/ReleaseNotes2.1_RC2CE.html which is essentially: composer require magento/product-community-edition 2.1.0-rc1 --no-update
composer update
php bin/magento setup:upgrade The 2.0.7 .tar.gz archive is placing the Magento files under the vendor directory, whereas the 2.1.0 Release Candidates spread them to different places. But it looks like composer is handling this correct. |
rm -r www/pub/static/_requirejs/
rm -r www/pub/static/adminhtml/
rm -r www/pub/static/frontend/
rm -f www/pub/static/deployed_version.txt
rm -r www/var/page_cache/
rm -r www/var/view_preprocessed/
rm -rf www/var/di www/var/view_preprocessed/ www/var/tmp/ www/var/cache/ www/var/composer_home/ www/var/generation/ www/var/report/ www/var/page_cache/ www/var/resource_config.json www/var/.cachestates.json www/var/.regenerate
php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento setup:static-content:deploy
php bin/magento indexer:reindex did not help either |
Hi @bh-ref |
@mslabko thank you for your the hint, the reason it did not work was indeed due to a customization (of an htaccess file) we did. |
[TSG] Fixes for 2.3 (pr89) (2.3-develop)
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: