After migration we have
1 exception(s): Exception #0 (Magento\Framework\Exception\LocalizedException): No options found.
#0 /var/www/vhosts/www/public_html/vendor/magento/module-customer/Model/Customer/DataProvider.php(359): Magento\Eav\Model\Entity\Attribute\Source\Config->getAllOptions()
It looks like we are missing options or something like that.
Does anyone have the same problem? Or someone can help me?
We are migrating from Magento 1.9 to 2.2.5
Thanks
Ed de Heus
KBITE
9 answers
Hi there,
1 exception(s): Exception #0 (Magento\Framework\Exception\LocalizedException): No options found.
It seem related to a bad settings of at least one custom customer attribute. Let’s provide me information about your instance:
+ Admin credentials and URL to back-end
+ SSH credentials and path to M2 folder
+ phpMyadmin credentials of your M2 database
I will help to check further and help you out.
Regards,
Mall.
HI,
We have a secured development area. It is possible with a remote session, like teamviewer orso. Is that also an option for you?
I just tried to do a delta migration but step 3 fails, attributes. So I think there is somewhere a problem.
Hi there,
How many custom customer attributes in your M2 database now? Could you provide me the screenshots that list all custom customer attributes in your M2 database now? You could use the following SQL to list that attributes at your end:
SELECT `attribute_id`, `attribute_code`, `backend_model`, `frontend_model`, `source_model` FROM `eav_attribute` WHERE `entity_type_id` = 1 AND `is_user_defined` = 1;
Once having further info, I will check further and help you out.
Regards,
Mall.
Thanks in advance..
We have 5 customer attributes (with your query). allowed_payment_methods, fax, newsletter, telephone, url
the fields backend_model, frontend_model and source_model are all NULL
Regards
Ed
Hi there,
the fields backend_model, frontend_model and source_model are all NULL
What is the value of the ‘frontend_input’ field on that attributes? If it has ‘select’ value, let’s change it to ‘text’ and tell me know how it goes then.
Regards,
Mall.
He Mall, yes this solved the error, it is possible to open the customer now in the backend. Problem was with the allowed_payment_methods, this was a multiselect, changed it to text and it solved the problem. But i cannot find the custom fields with the customer in the backend at all. Now checking out if i need them, but I’m thinking that the payment methods per customer is probably needed but I will find out. Lets first check the Magento 1.9 area..
Hi there,
Yeah, that is related to the custom customer attribute and associated third-party extension.
Let’s continue at your end and contact me if you need further assistance.
Regards,
Mall.
He Mall, thanks for your support! I will come back when i need more assistance, today you make my day! Thanks!
Hi there,
Glad it helps. In case you have additional questions, please get back to us here.
Regards,
Ubertheme team
