Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I'm using the migrate module for the first time. I'm able to add a new table in table wizard and view the contents just fine. Then, I go to Migrate and add a new content set. When I do so I see the error: no Schema type for mysql type date, before importing.
It's a very simple batch of data I am trying to import. It contains only 4 fields: id, date, title and body. They are newsletter issues from an old site I am trying to get into simplenews. If I ignore the error above and proceed to import, 333 rows in total I get 0 Imported and 333 Errors/Unimported. The first time I tried it I had success and it said 333 rows imported but then I could not find the content anywhere. It was the successive tries after that that I receive the 333 errors.
Hoping you can point me in the right direction in searching I am not finding any workable solutions.
Thanks.
Comments
Comment #1
robbieferrero commentedI've just started using these modules, but ran into similar messages as you have on my current project.
Those error messages about no Schema type are coming from the Schema module, not migrate. You can suppress them by going to admin/build/schema/settings and checking the box to suppress warnings.
Concerning the 0 imported message, what is your migrate_msgs_{whatevercontentset} telling you? You can view it from table wizard's interface or go into the view itself and generate a preview.
Comment #2
mikeryan@aleclaughlin: As Robbie says, the message about mysql type date is from the Schema module, and shouldn't be a concern. And also as he says, when you get the 333 errors, what precisely are the errors (stored in the migrate_msgs_foo table and visible by clicking on the error count in the dashboard)?
Comment #3
mikeryanNo further info provided.