WPHSV MeetUp - Migrate to 5.0 and Gutenberg

Transcript

1. Migrate to 5.0 and Gutenberg Jacob McKinney Developer at Image in a Box @jacobmcdev jacobmckinney.com
2. Plugins Most basic themes have nothing to worry about, but if your theme offers customizations to the editor, it needs to be examined. Any plugins that interact with the editor need special consideration during this process. The only way to ensure compatibility is to test. Themes Areas of concern:
3. Step 1: Dev Site You need it.
4. Hosted • Requires technical knowledge. • Options: ◦ MAMP ◦ ScotchBox ◦ Local by FlyWheel • Check with your host to see what options are available. • Managed hosting may provide you with one-click options. Local Set it up!
5. Step 2: Update (DEV) Face your fears
6. Existing Content Your existing content should remain unaffected. When you activate the new editor, all existing content will be loaded into a “classic editor” block, which will essentially keep it the same as it was before the update.
7. Step 3: Plugins (DEV) Update all the things
8. Update Go through each of your plugins and think about whether it interacts with the editor. Once all editor-related plugins have been identified, test them in the new editor (keep in mind some functionality may have been moved to new or existing blocks). Update all plugins that have updates available. Most plugins have recently released updates for compatibility with the new editor. Audit
9. What about broken plugins? Options: • Contact the plugin author. • Find a new plugin that has similar functionality and is compatible with the new editor. • If the functionality isn’t crucial, you could consider moving on without it. Note: If the plugin is necessary for functionality that lives in pre-5.0 posts, you may need to consider keeping it active in order to keep those posts in tact.
10. Step 4: Production Taking care of business
11. BACKUP YOUR DATA
12. Migrate to/Update Production Migrating If you’re lucky enough to have an easy way to copy your staging site data to production, do that. Note: If you have a site with data that is constantly changing, such as an ecommerce site, don’t migrate your database, you will lose data. Updating Most people will probably just need to repeat the update process with one distinct difference: Plugins first, take care of your plugins before updating WordPress.
13. Resources • MAMP - https://www.mamp.info/en/ • ScotchBox - https://box.scotch.io/ • Local by FlyWheel - https://local.getflywheel.com/