Moving from 3.10.0 to 3.10.1, I received the error I noted earlier. The instructions say if you get errors, then manually set up your url aliases. But the admin and public interfaces won't work easily because no url aliases are working. When I run:
SELECT id, link, parent, lang_mask, text, action, is_original, is_alias, lang_mask_adjusted FROM ezurlalias_ml_migrate WHERE is_restored=0; I get 349 results.
Could someone talk me through how I complete this migration manually in the tables? Thanks.
Thank you. I actually found the cache hadn't fully cleared. This meant the production server's database user and password were being tried on the installation where I was doing the upgrade, which of course didn't work. Fixing that, plus running the migration from the admin interface, did the trick. Thanks!
There's no need to keep the URL alias migration extension once this is complete, right?