Also, note from your dashboard you will want to install the ‘classic mode’ plugin prior to moving to WP 5.0 as this will allow you to keep all ‘current’ functionality of the post editor and the pagebuilder. You don’t need to activate it until you plan to upgrade to WP 5.0 (although you may wish to install/activate *now* if you have WP auto updates active, which is not a good idea for daily admin folk anyway).
@simion — Likely there should be a bump in the TD Composer or NP/NM theme update to mention this with a panel added to dashboard ala the new Gutenberg info box?
Gutenberg fundamentally changes the way a post is made, trying to make it a bit like old Quark and PageMaker DTP software, where every element is a ‘block’ — even multiple items on the same page, and it’s a bit wonky as you can end up with blocks you don’t want, and you can’t easily copy/paste the whole shebang into another site, and basic elements like shortcodes, custom fields, etc., might not work at all.
The classic editor will be the best choice for most people using ANY theme built with pagebuilders for the near term. This is for WP 4.9x and up. Not needed for older (and, ahem, insecure versions of WP).
I just installed it on a copy of my main site. All it seems to to is offer you a choice of editior for posts or pages. So to use the TagDiv editor you just choose clasic editor when you create a new page then you have access to it. I assume the full version 5 release will keep this functionality.
The update didnt break any pages or seem to effect the site in anyway.
There was some wierd text that i cant find again relating to WP Bakery visual composer. I dont know if you will be offering an update for that plug-in if its needed?
There will be testing on our side as I mentioned above. If we will spot any issues we will try and fix them. There shouldn’t be anything major however.
Do let us know of problems found with the new editor used with the theme, I will pass them along for testing.