Violinist.io is well into its seventh year. It has survived a couple of Drupal core major upgrades and remains a profitable SaaS based on Drupal and a vital tool for agencies and organizations.
One of the things a website owner expects when they launch their new Drupal 8/9 website is that their Drupal 6/7 users are still there, and can still log in using the same credentials.
Since this error now has bit me twice, and I had to search for a while to find out how I fixed it the first time, I decided to just write a quick blog post about it instead. And this is indeed it.
Migrate in core is among my favorite parts of Drupal 8 and 9. The framework is super flexible, and it makes migrating content from any source you can dream up pretty straight forward.
On a project I just discovered I had to make a change to both how some blocks were configured, but also remove access to some other blocks (with the module Layout
Violinist.io is well into its seventh year. It has survived a couple of Drupal core major upgrades and remains a profitable SaaS based on Drupal and a vital tool for agencies and organizations.
One of the things a website owner expects when they launch their new Drupal 8/9 website is that their Drupal 6/7 users are still there, and can still log in using the same credentials.
Since this error now has bit me twice, and I had to search for a while to find out how I fixed it the first time, I decided to just write a quick blog post about it instead. And this is indeed it.
Migrate in core is among my favorite parts of Drupal 8 and 9. The framework is super flexible, and it makes migrating content from any source you can dream up pretty straight forward.
On a project I just discovered I had to make a change to both how some blocks were configured, but also remove access to some other blocks (with the module Layout