-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Class 'Magento\Framework\Data\Form\Filter\2016-05-01' not found On customer save Magento2 Migration #4936
Comments
Hi @ruturamani , |
I can confirm this issue! Happens after I have upgraded from 1.7.0.2 to 2.1.0. Any solutions so far? |
The solution: #5873 |
Registered MAGETWO-54115 |
Hi @ruturamani Thank you. |
I had the same issue on 2.3 but not related to the migration the update is in this function and as its a bug in core file you're fine to replace the core file |
Hi, My recent upgrade is 2.3.1 as Magento moves we are upgrading one by one, Is there any fix relates to its?
Please help me to get a best solution for this. |
[TSG-Commerce] Tests for 2.3 (pr2) (2.3-develop)
I have done migration from 1.9.2 to 2.0.x many times. Last I did was in 2.0.6. But I am having same error every time. The error I am getting is in saving customer. I am unable to Edit migrated as well as newly added customers after migration. I am getting the following error:
Class 'Magento\Framework\Data\Form\Filter\2016-05-01' not found in D:\wamp\www<magento_root>\vendor\magento\module-customer\Model\Metadata\Form\AbstractData.php on line 214.
I have tried the following solution.
Going into the database, I found in table customer_eav_attribute the column input_filter. Changing varchar to date. But this didnt solved the problem.
One more issue I am facing is that my "billing" and shipping address are not correctly coming on customer edit page, orders page in both frontend and backend.
Here are some screenshots for the above issue.
Can any one please help me to get out of it... I am seriously got rid of this issue.
Thanks !
The text was updated successfully, but these errors were encountered: