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.

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

After migration from 1.9.2.2 to 2.1.1 - Cannot edit customers #6510

Closed
daschenbrener opened this issue Sep 6, 2016 · 12 comments
Closed

After migration from 1.9.2.2 to 2.1.1 - Cannot edit customers #6510

daschenbrener opened this issue Sep 6, 2016 · 12 comments
Assignees
Labels
bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed

Comments

@daschenbrener
Copy link

performed an upgrade from 1.9.2.2 to 2.1.1 and the migration was successful.

But now when i try to go into the admin side, and edit it customer, the page gives me a error and the magento screen of death. (lol)

Preconditions

magento 2.1.1
migrated from 1.9.2.2 to 2.1.0 , using the data migration tools
php 7
mariadb 10.1.14
Ubuntu 16.04

Actual result

here is the first line of the error report

a:4:{i:0;s:89:"The requested component ("") is not found. Before using, you must add the implementation.";i:1;s:8481:"#0 /opt/bitnami/apps/magento/htdocs/vendor/magento/module-ui/Model/Manager.php(207): Magento\Framework\View\Element\UiComponent\Config\Provider\Component\Definition->getComponentData('')

Attached is the full error report

error on no customer display.txt

@daschenbrener
Copy link
Author

not sure if this is related to this also: #5873

@daschenbrener
Copy link
Author

daschenbrener commented Sep 9, 2016

is there anyplace where we can see a roadmap or a time that a new update may be released @andimov @mage-core-team

@victor-v-rad
Copy link
Contributor

Hi @daschenbrener
It is hard to figure out the cause of the issue
You could share DB dump (remove all passwords before) of Magento 1 and send it through email (find it in my profile https://github.com/victor-v-rad)
We will try to migrate it to reproduce and fix

@daschenbrener
Copy link
Author

daschenbrener commented Sep 23, 2016

the db is about 6GB, but what might work better is getting you the login and password of the server that this is setup on,

@daschenbrener
Copy link
Author

or just let me know what would work the best @victor-v-rad

@victor-v-rad
Copy link
Contributor

Let's discuss it in skype rad_victor is my

@victor-v-rad
Copy link
Contributor

It's the end of my working day. We will get in touch on Monday.

@daschenbrener
Copy link
Author

ok sounds good then, im just tied up for a bit yet

@victor-v-rad
Copy link
Contributor

Do you still have the issue? Feel free to connect with me through skype

@daschenbrener
Copy link
Author

I do sorry for the delay, ill try to touch base with you tomorrow (Tues) my timezone is MST (-7 GMT)

@victor-v-rad
Copy link
Contributor

Hi @daschenbrener
The reason of the issue is in attribute with code webtoprint_template. Most likely it is from some extension. In particular in eav_attribute table the webtoprint_template record has empty frontend_input field. This cause the error you have.

@magento-engcom-team magento-engcom-team added 2.1.x bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 11, 2017
@magento-engcom-team
Copy link
Contributor

Thank you for the report. The issue has been resolved

magento-engcom-team pushed a commit that referenced this issue Jan 20, 2021
MCP-89 Move product batch size variable to environment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed
Projects
None yet
Development

No branches or pull requests

4 participants