In the selectors above you must select the Drupal10 destination, it can be content type, paragraph or vocabulary, then by Ajax the fields of the selected type will be loaded in the selectors of the fields you say.
On the module page description is explained, i will upload a video tutorial and add more documentation.
all the best.
so have you managed to configure the users?
Hi wattsesings, maybe u are not configured the roles mapping tab.
Maybe a bug i will resolve, please try configure the roles first and later try again with users.
Thanks for use migrate wizard.
Hello,
In the migration of the taxonomy related field you must select the dependency so that migrate can then do the lookup, have you done this?
Can you put screenshots of the configuration of the taxonomy migration and of the field in the content type of that taxonomy?
Regards.
This point would correspond to the general Drupal documentation on how to do migrations, in any case we could refer to that documentation from here.
Regards.
carlos romero → made their first commit to this issue’s fork.
hi acke, u can get me a credit please?
thanks!
carlos romero → made their first commit to this issue’s fork.
carlos romero → made their first commit to this issue’s fork.
Done, I've added a new plugin that migrates the url field type from drupal 7 to a link field type from drupal10.
Please do composer update drupal/migrate_wizard
Thanks and regards
carlos romero → made their first commit to this issue’s fork.
carlos romero → made their first commit to this issue’s fork.
Hi awanson.
You must run drush ms for see the migrations avaliables.
Later you can run drush mim id_migration for run each migration.
Also you can install migrate tools module for run migration from admin interface.
Here you can see all commands for manage migrations with drush.
I understand that your problem is about migrations in general. The purpose of this module is to automatically generate the YML that are normally done by hand, the rest of the process to migrate content from Drupal 7 is the same as always. I recommend that you read documentations, tutorials. Examples and videos to learn and understand how Drupal migrations work. I close the issue. all the best.
Hi, I don't understand why you are getting data from roles and text formats, but your database configuration is not correct.
Seeing what is happening to you, I think it would be a good idea to set the fields as required.
I don't understand why it is reading your roles and text formats, but I recommend trying to put the correct data in the database configuration and then test it.
Sorry if it doesn't seem obvious what data to enter in those fields, but I assumed that it would be understood that it should be done as in the standard configuration for databases, with a quick search on Google I found this tutorial, for example:
https://octahedroid.com/blog/drupal-7-drupal-10-full-step-step-migration...
Take a look at it and do your tests.
carlos romero → created an issue.
Hello,
I think your connection configuration to the drupal 7 database is not correct.
In the database entity configuration offered in the module, you have to put the data in the same way as when you add it in the settings.php file.
There are many tutorials and documentation about how to do it.
In the description of migrate wizard there is an image that shows how it should be:
Although there is some data that I suppose will vary, such as the name of the database, user, password, host, port... adapt this data to what you need, you can see the settings.php file of your drupal7 to see what you need.
If you are using Lando, as slcak has told me, verify that the connection to the drupal database from the drupal 10 docker console works with mysql.
I use ddev for my local stack and from the drupal 10 docker console I write this:
mysql -u db -p -h ddev-drupal7-db
and I can connect to the drupal 7 database.
Sorry the issue is duplicated:
https://www.drupal.org/project/migrate_wizard/issues/3480010 🐛 TypeError: Illegal offset type when creating database Active
I just released a new release of the module with this bug fixed
Please do composer update drupal/migrate_wizard
carlos romero → made their first commit to this issue’s fork.
carlos romero → created an issue.
carlos romero → made their first commit to this issue’s fork.
carlos romero → made their first commit to this issue’s fork.
closed duplicate
Hi avpaderno,
First of all, thank you for your instructions.
I think I have solved everything you have indicated.
In the controllers, I have added a base controller MWControllerBase, which implements ContainerInjectionInterface and I extend that in all my controllers.
Also in that controller I use some traits that I needed (these were already in the original ControllerBase), but now the rest of ControllerBase is no longer there, only what I need :).
I have moved the listbuilders to the entity folder and fixed the namespaces.
I have removed the interfaces of the entities that were not needed.
I await further instructions if there are any.
Thank you very much.
Regards
carlos romero → created an issue.
carlos romero → made their first commit to this issue’s fork.
carlos romero → made their first commit to this issue’s fork.
carlos romero → created an issue.
Hi, I've fixed some bugs that were in the 2.0.x branch.
If you've already started the review, please excuse me.
Regards.
carlos romero → made their first commit to this issue’s fork.
Hi hbaa,
First of all, thank you for your interest in the migrate wizard module.
The module simply generates the yml files for the migrations that will later be used by the drupal (core) migrate module.
If your portal contains so many nodes, it will inevitably take a long time to migrate.
Tips to make it take less time:
Use a machine with more resources, I often program and test the migrations in my local environment of the projects I work on, but then when launching the migrations in the pre-production environments, they run faster because I have machines with more resources.
File migration with migrate wizard has some peculiarities:
the files are copied one by one on the fly when migrating the nodes, you do not need to migrate the files or media first, although if you do, this will be scalable and each entity will be reused when appropriate so that downloaded files or entities pointing to the same file are not repeated.
In any case, to speed up this part, I recommend placing the files in the destination folder, so that in the migration process, each file will not be downloaded and the file or media entities will simply be created when appropriate.
This is done this way because in some cases you may not want to migrate all the files that exist in the source; when migrating the nodes, only the files that are used in the migrated content will be copied.
That is, if you have 20,000 files in the source but you only want to migrate those that are being used in a type of content, do not migrate the files, only migrate the type of content you want and only the files of that type of content will be copied, for example.
Regarding the errors you mention, I would need more data from the trace, to see which part of my module it comes from, although from what I see in the error, from afar, it may be due to your version of php, or the data you are trying to import.
In any case, please investigate the error and if you see that it is due to the module, open a specific issue with it.
I'm closing the issue, best regards and good luck with your migration.
Hi, thanks for your help.
I have fixed all the points you have indicated:
I have deleted the branch that was wrong.
I have corrected all the points in phpcs on my local and I have uploaded the changes to the 2.0.x branch.
I have deleted the line you have indicated from the migrate_wizard.libraries.yml file.
If you need me to make any further changes, please let me know.
Thank you very much for your help.
carlos romero → created an issue.
This issue is related to:
https://www.drupal.org/project/drupal/issues/3453326
🐛
Dynamic local tasks with different children that have the same route with different parameters
Needs work
In some cases, it is necessary to make an alter hook so that the tabs are generated correctly.
The drupal core takes into account the machine name of each url for the tabs, but you have to take into account the parameters they have, since these generate different urls for each tab.
carlos romero → created an issue.
carlos romero → created an issue.
carlos romero → created an issue.
carlos romero → created an issue.
Hi, I have reverted the commit of in branch 3402972-2.1.4.
The method ImageStyleDownloadController::getUriWithoutConvertedExtension is not present in Drupal version 9.5.x, the 2.x version of stage file proxy is for Drupal 9.x and 10.x.
idebr thanks for the contribution, but this only applies to version 3.x of stage file proxy.
Thanks
Carlos Romero → made their first commit to this issue’s fork.
Applied changes from patch #37 to the corresponding branches and created mr
Carlos Romero → made their first commit to this issue’s fork.
Carlos Romero → made their first commit to this issue’s fork.
Carlos Romero → made their first commit to this issue’s fork.
Carlos Romero → made their first commit to this issue’s fork.
Thanks!!
U can get me a the credit please?
Hi cilefen, i'm working on fixing the tests, please don't close the issue.
Thank you
Robbt I invite you to try the patch that I have shared in the fork:
I hope it helps you, greetings
Carlos Romero → made their first commit to this issue’s fork.