Hi @lostpine,
Sorry to hear that. Version 4 was a major upgrade in which we completely rewrote the database tables to handle redirects and 404 error logs more effectively and with better performance.
During the v4 upgrade, all custom redirects should have automatically migrated from the older version to the new one. However, the error logs will not migrate automatically unless you manually start the process from the plugin UI. After the update, you should see a banner asking you to start the migration—did you happen to click on it? It should be visible on the logs list page.
Nonetheless, the redirects themselves should have migrated automatically. If you have database access, could you please check if the old table (wp_404_to_301) still exists?
I did see the logs prompt, clicked it, and the logs migrated. However, when I checked the tables, the only one I found was “wp_404_to_301_redirects” and it was empty.
Do you remember how many custom redirects you had? This is the first report we’ve received about this issue, so it could be a conflict. We will have to investigate further. Could you contact us through support@duckdev.com?
