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

Class 'Magento\Framework\Data\Form\Filter\2016-05-01' not found On customer save Magento2 Migration #4936

Closed
ruturamani opened this issue Jun 9, 2016 · 8 comments
Labels
bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@ruturamani
Copy link

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.

untitled

Can any one please help me to get out of it... I am seriously got rid of this issue.

Thanks !

@ruturamani
Copy link
Author

This is one more screenshot of order view page... after migration. Here also I am not getting the billing and shipping address.

untitled2

Thanks !

@mslabko
Copy link
Member

mslabko commented Jun 9, 2016

Hi @ruturamani ,
Thank you for reporting! We will take care about your issue, but please use this repo https://github.com/magento/code-migration/issues for similar issues

@milanstojanov
Copy link

I can confirm this issue! Happens after I have upgraded from 1.7.0.2 to 2.1.0. Any solutions so far?

@milanstojanov
Copy link

The solution: #5873

@ilol
Copy link

ilol commented Aug 30, 2016

Registered MAGETWO-54115

@ilol ilol added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Aug 30, 2016
@magento-engcom-team magento-engcom-team added 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

Hi @ruturamani
For migration related issues please use the correct repository: https://github.com/magento/data-migration-tool

Thank you.

@aniruddh-capital
Copy link

I had the same issue on 2.3 but not related to the migration
here is the solution which worked for me for anyone still having this issue on 2.3
replace this file /vendor/magento/module-paypal/Model/Express/Checkout.php
with latest of magento version 2.2.4

the update is in this function
_setExportedAddressData

and as its a bug in core file you're fine to replace the core file

@hackronshins
Copy link

Hi, My recent upgrade is 2.3.1 as Magento moves we are upgrading one by one,
But we are having an issue which is on Paypal orders we are getting variable prefixes in billing address as email template format in admin side back end.
Admin Dashboard -> Sales -> Operations -> Orders -> View Order

Is there any fix relates to its?

I tried all above solutions who got fixed, In database also I checked it is perfect. But why it is not fixed yet. We didn't touched anything in code.

Please help me to get a best solution for this.
Please find the attachment

14

magento-engcom-team pushed a commit that referenced this issue Oct 29, 2019
[TSG-Commerce] Tests for 2.3 (pr2) (2.3-develop)
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 Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

10 participants