Migration problem

@gregywordpress It looks like it failed when trying to deactivate the Atomic Blocks plugin. If you deactivate Atomic Blocks manually now, are you able to see and use the Genesis Blocks in a page or post that previously had an Atomic Blocks block in it? They should migrate from AB blocks to GB blocks and work like they did before.

I have some other questions but I’ll wait to hear back from you about the content migration.

I have the exact same problem. I’ve removed the old plugin to no avail, and the “Welcome… migrate now” panel is still at the top of every admin page.

Exact same problem for me as well.

@petervandoorn @jamonkey We’re working on an update now. The problem appears to be isolated to the AB deactivation step, which also handles disabling the notice you’re seeing.

I’ll let you know when the update is published.

@gregywordpress @petervandoorn @jamonkey Thank you for reporting this.

Are you able to share any fatal error messages from your PHP logs, please? It would help us to confirm the cause of this.

Here is the error we get:

[29-Oct-2020 07:39:11 UTC] PHP Fatal error: Cannot redeclare paused_plugins_notice() (previously declared in /mnt/BLOCKSTORAGE/home/user/public_html/wp-admin/includes/plugin.php:2465) in /mnt/BLOCKSTORAGE/home/user/public_html/wp-admin/includes/plugin.php on line 2465

Thank you, @christopherplus. That’s helpful. We’re looking into a fix for this.

Genesis Blocks 1.1.1 is out now with a fix for this issue.

1. Update to Genesis Blocks 1.1.1.
2. Revisit Genesis Blocks → Migrate.
3. Complete the migration process.

Step 3 should now complete and the message to migrate to Genesis Blocks should no longer appear. (It’s ok to see “Migrated: 0.” because your content was migrated in the previous attempt.)

Once the migration has completed successfully you will no longer see the Migrate option in the Genesis Blocks menu. You can also delete Atomic Blocks once you have confirmed all is well.

Thank you again for the reports and for your patience.

Thank you!
The update solved the problem!
Kind regards,
Greg

Thanks for letting us know, @gregywordpress!

Thanks, the update worked for me as well.

@jamonkey @petervandoorn @gregywordpress The update that fixes this is now out. ??