Nick C
Forum Replies Created
-
Forum: Plugins
In reply to: [Genesis Portfolio Pro] Error messages on new site after changing slugs@madriverweb Great to hear it helped! Thanks for the update here.
Should I update that site, too, over concern for possible breakage, or don’t fix what ain’t broke?
You could pre-emptively fix it in case your host changes the PHP version or error reporting configuration (a difference in those things might be why you’re not seeing the same issue there), or just see how it goes. At least you have a solution to try if you see it again.
Are you available for hire or could you suggest anyone?
I’m employed full-time, but you could check out the Genesis Developers listings if you need paid help, or post in the Genesis Slack #gigs channel if you just want to build your network of freelancers.
Forum: Plugins
In reply to: [Genesis Portfolio Pro] Error messages on new site after changing slugs@madriverweb I corrected some issues with the custom code and this version works for me to create the
/meeting/URLs:https://gist.github.com/nickcernis/f07c9e3cd5bff249cb530dd0e62ac460
There were two issues with the custom code:
1. Translation functions had single underscores instead of double underscores.
2. There were additional stray quotation marks in the function calls in the code in portfolio_args.You may need to visit Settings → Permalinks in the WP admin after updating the plugin file with the corrected version before you see the correct URLs and labels.
Forum: Plugins
In reply to: [Genesis Portfolio Pro] Error messages on new site after changing slugs@madriverweb Please can you share the code on and around line 37 of your edited
genesis-portfolio-pro-custom/plugin.php? It may relate to custom code added there.> Additionally, is the plugin compatible with WordPress 5.6.x?
There are no known issues specific to 5.6. The project has a bug tracker here if you find anything:
Forum: Plugins
In reply to: [Genesis Blocks] Genesis Block Migration ReminderHi, @saketyeotikar. We released an update to fix this (Genesis Blocks 1.1.1).
If you have already completed the migration, you can:
1. Update to Genesis Blocks 1.1.1 if you have not already done so.
2. Visit/wp-admin/?genesis-blocks-migrate=1.
3. Run through the migration process again. This will make no further changes other than to clear the upgrade prompt.You do not need to reinstall Atomic Blocks to do this.
If the notice is not cleared at this point, it could be due to object/option caching. Try clearing any object caches that your host may have in place. (Some hosts offer a cache clearing option via a plugin or control panel.)
Great to hear. Thank you for letting us know, @titusraj.
Hi, @titusraj.
Essence Pro has a new update with Genesis Blocks styles. If you update your theme as prompted in step 2 of the migration you should see the same styling as the original Essence Pro.
You can download the updated theme from your StudioPress account area.
Forum: Plugins
In reply to: [Genesis Blocks] different layout for post gridHi, @outcats85.
Updating Essence Pro to the latest version will fix this. It includes styling for Genesis Blocks instead of Atomic Blocks. Step 2 on the migration page linked to more information about this here:
You can find the latest copy of Essence Pro in your StudioPress account area.
I’m sorry for the difficulties you experienced, @sjoechem.
As long as you update any themes or plugins that include Atomic Blocks CSS/PHP as we describe in step two of the migration, you should not see any design changes, be it a multisite or single site.
Please feel free to take up David’s offer to talk in your post in the StudioPress forums if you’d like to share further feedback with the StudioPress team.
Forum: Plugins
In reply to: [Atomic Blocks - Gutenberg Blocks Collection] Migration problemThanks for letting us know, @gregywordpress!
Forum: Plugins
In reply to: [Genesis Blocks] Migration From Atomic Blocks Failed@mbaiti Great! Thanks so much for letting us know.
Forum: Plugins
In reply to: [Atomic Blocks - Gutenberg Blocks Collection] Migration problemGenesis 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.
Forum: Plugins
In reply to: [Genesis Blocks] Migration From Atomic Blocks FailedGenesis 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.
Thank you again for the reports and for your patience.
- This reply was modified 5 years, 6 months ago by Nick C.
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.
Thank you again for the report and for your patience.
@sokratesagogo Yes, we have a note on the plugin homepage as well as some detailed migration notes that we link to from the migration page in Genesis Blocks.
There’s a video walkthrough in the migration notes and some screenshots and example code. But if you need anything more, let us know!
Several months sounds about right, @and_or. We don’t have immediate goals to remove Atomic Blocks. We recognise that multisite migrations can require more time and planning.
We tested the migration on multisite and have notes for multisite admins here.
Atomic Blocks and Genesis Blocks should not be network-activated together on a multisite install. Editors would see duplicate blocks in the block picker and duplicate block UI such as the Layouts button above the editor.
If you need to support both plugins on multisite, you could individually activate either plugin (but not both) on subsites instead of network-activating them.