Congrats on a great release in 3.0. The page builder shows lots of promise, however I'm hitting a show stopper.
When using the text box in a column, editing the field defaults to the WYSIWYG text editor. As a result, any custom coded classes get wiped out. For example, I wrapped some text in a custom coded H class which seems to keep getting stomped. Am I missing anything? Any recommendations on how to preserve and edit custom code and classes within the page?
One quick followup Phil--I can totally see the allure of the page builder, yet I'm finding the ease of editing the code directly to be much faster (no popups, saves and updates, etc.) Are we safe to use the Classic editor with the existing shortcodes or will future upgrades cause problems? Thanks again, wonderful work (and it seems the custom font header popping is fixed!)
I prefer working with code too (for obvious reasons) but the page builder was an important thing I needed to add for users who are not used to working with. I actually touched on this exact question you have regarding the use of shortcodes going forward here: http://youtu.be/N4mt0lOJ888?t=6m1s and the answer is you're completely safe to continue life the way you did prior to 3.0. I don't plan on removing the shortcodes ever and would never put that burden on legacy users.
Hi Phil,
Congrats on a great release in 3.0. The page builder shows lots of promise, however I'm hitting a show stopper.
When using the text box in a column, editing the field defaults to the WYSIWYG text editor. As a result, any custom coded classes get wiped out. For example, I wrapped some text in a custom coded H class which seems to keep getting stomped. Am I missing anything? Any recommendations on how to preserve and edit custom code and classes within the page?
Thanks as always!
Dave
Scratch that--using the Raw HTML seems to do the job. My bad.
One quick followup Phil--I can totally see the allure of the page builder, yet I'm finding the ease of editing the code directly to be much faster (no popups, saves and updates, etc.) Are we safe to use the Classic editor with the existing shortcodes or will future upgrades cause problems? Thanks again, wonderful work (and it seems the custom font header popping is fixed!)
Hey Dave! :)
I prefer working with code too (for obvious reasons) but the page builder was an important thing I needed to add for users who are not used to working with. I actually touched on this exact question you have regarding the use of shortcodes going forward here: http://youtu.be/N4mt0lOJ888?t=6m1s and the answer is you're completely safe to continue life the way you did prior to 3.0. I don't plan on removing the shortcodes ever and would never put that burden on legacy users.
Cheers!