FT&I part with newTiny MCE after SP2 installation

Options
BBNC hive, I need your input/assistance with the new FT&I editor that was released in 7.1 SP2:


The new TinyMCE editor with SP1 for emails was a gift from heaven - the ability to have doc type, head tag, etc is going to make our email coding lives so much better and for that I'm truly thankful. SP2 rolled that same editor to all FT&I parts. This seemed like a great thing until I started working with it. For some nutty reason, the editor for FT&I parts still has top-level html page tags (<html><body><header>, etc.) & it's wrapping all our content in those tags. In addition, and the part that is most troubling, is that it's stripping all of the inline scripts.


Stripping inline scripts/styles is an issue for anyone who uses classes to create styles/buttons/embed 3rd party code/etc in their site to apply responsive behaviors or to elevate the user experience. Any content created before SP2 is OK until I open the part, edit & save. Then it's over. The only work around I've found is to move that content into an Unformatted text part and avoid the new TinyMCE editor all together. This isn't an issue for me since coding is my thing, but I feel like this is going to be a problem for anyone who isn't comfortable with HTML code.  


Is anyone else experiencing issues with code being stripped? If so - what did you do for a work around?

Blackbaud Team - Is there an overarching reason for keeping the html tags in the FT&I that I need to understand and be mindful of? If not, any plans to update the editor for FT&I parts so it's not treating content like email code?


Any help and input is very much appreciated!
Tagged:

Comments

  • Hi Rebecca,


    Hope you've been well! While traditionally scripts have been able to be placed inside FTI parts, we do recommend using Unformatted Text parts due to the HTML formatting with FTI parts. Scripts can still be placed inside the <head> section of the FTI source code, and inline styles should still be accepted within the <body> tag. If you are seeing different behavior, can you provide example code so we can further investigate?


    Thanks!

    Tony

Categories