Hi,
please enable WP_DEBUG by following this guide:
https://www.seopress.org/support/guides/wp_debug-enable-error-logging-in-wordpress/
Then run again the migration.
Once the process is blocked, check the error from the debug.log file.
Thread Starter
gomoot
(@gomoot)
Hello
no thanks , migration messed up everything and I needed to restore all site from backup,
you can report me when it’s fixed and I will try again. Very bad experience by the way, I will stay with AIOSEO.
Graziano
Thread Starter
gomoot
(@gomoot)
I think you should provide a WP console mode with integrated debug.
Thread Starter
gomoot
(@gomoot)
do you think this will work (Claude idea) ?
wp eval “
\$aio = new SEOPress\Actions\Admin\Importer\AIO();
echo ‘Migrazione Impostazioni Globali… ‘;
\$aio->migrateSettings();
echo ‘OK!’ . PHP_EOL;
global \$wpdb;
\$total = (int) \$wpdb->get_var(\”SELECT count(*) FROM \$wpdb->posts\”);
\$increment = 500;
\$offset = 0;
echo ‘Migrazione Metadati Post (Totale: ‘ . \$total . ‘)…’ . PHP_EOL;
while (\$offset < \$total) { \$aio->migratePostQuery(\$offset, \$increment);
\$offset += \$increment;
echo ‘Migrati ‘ . min(\$offset, \$total) . ‘ / ‘ . \$total . ‘…’ . PHP_EOL;
}
echo ‘Migrated’;”
Thread Starter
gomoot
(@gomoot)
Did you consider to use the AIOSEO export settings (it’s a file) instead of migrate option ?
Hi,
Running the migration directly on the database is much more efficient than using a file.
We do offer metadata import via CSV with the PRO version, but that serves a different purpose.
Regarding your issue, it appears to be related to a server limitation.
Could you let us know approximately how many posts, pages, and custom post types your site has?
Also, please go to Tools, Site Health, Info tab, Server and share your server configuration with us.
Finally, using the debug.log would be very useful to quickly understand the issue (I guess it’s related a memory limit).
We are now closing this topic due to inactivity. Thank you for your understanding.
