Given the code used by PhpassHashedPassword::needsRehash(), a method implemented by the class used for the default password hashing service, a password is stored using the Drupal hashing schema when:
The first three hash characters are $, S, and $
The hash length is PhpassHashedPassword::HASH_LENGTH
The other hashing schemas Drupal recognizes are the ...
As Kevin suggested, inspired by the
file from the migrate_plus module , i have managed to make it working as such:
label: 'Migrate beetween jobs from XML file'
# We use the XML data parser plugin.
Here is how I was able to achieve it.
Ok, I was able to do it quite easily with drush dumps.
First, I did a dump on the live server with:
drush sql:dump > db.sql
And then in my docker environment.
First I made sure I drop the tables from the database from Phpmyadmin.
Then I entered the docker image.
docker container exec -it <docker-container-id> bash
And then run drush with the name ...
There are two parts to the migration: the database and the static files.
The most important part is the database. You'll need a database backup (aka sqldump) of the production database, and you'll need to import that into your local database. There are several ways to accomplish this, depending on your site hosting and whether or not you can use drush.
This issue appears to have been resolved in:
which was merged into core as of 8.1.4.
In order to preserve pre-hashed passwords, add the following to your migration YAML file:
As I said in the comment(s), the plugins currently ensure field collections are migrated to Paragraph bundles and same for d7 Paragraphs. Field data is not moved, this is a gap you currently need to fill yourself. So you have to write YAML migration definitions to do this.
I recently did a d7 to d9 migration that had this requirement (with Field Collections ...