This plugin preserves the user-generated HTML markup in the TinyMCE editor. Unlike other plugins this one allows developers to work in the HTML tab AND end-users to work in the WYSIWYG Visual tab at the same time! No longer will your HTML markup be completely munged into an unrecognizable form when you switch between those tabs. And you don\u2019t have to hang your users\/editors out to dry when you hand off the project with a disabled Visual tab.<\/p>\n
(One user didn\u2019t read or follow these steps and panicked thinking I ruined their website.)<\/p>\n
It also supports HTML5 Block Anchor tags in addition to other HTML5 elements, something that is currently not supported in WordPress via any existing plugins.<\/p>\n
Version 1.5 will probably be the last version I release for a while since my daughter will be born soon. I\u2019ve added support for full JavaScript code blocks in the HTML tab. They are compatible and preserved when switching to Visual mode. This rounds out the support for almost complete html preservation, with full use of the WYSIWYG editor. And you don\u2019t need to wrap comment codes around it per the recommendations located here: https:\/\/codex.wordpress.org\/Using_Javascript<\/a> but you can leave them in if you want.<\/p>\n Version 1.4 was just a minor patch release. User @denl noticed a problem with the plugin CataBlog which implements its own administrative management features by disabling the \u2018show_ui\u2019 flag for its custom post type. I was ignoring any custom post type that didn\u2019t have a GUI, but it was an unecessary filter that probably limited other plugins. This fix allows any post type that supports the TinyMCE editor to be \u201cfixed\u201d using the tools under Admin > Settings > Writing.<\/p>\n Since version 1.3 you can now use inline CSS and JavaScript in the HTML editor and everything should be preserved. To be clear, this applies to tags only, like This new feature is pretty experimental at the moment. I tried to make it compatible with wptexturize but that proved close to impossible without duplicating a lot of core code in my plugin. It\u2019s also not compatible with TinyMCE Advanced when the \u201cstop removing p and br tags\u201d setting is enabled. Since version 1.2, you now have a little more control over how content is created. And most of the previous caveats to using this plugin are now resolved.<\/p>\n You can now choose whether to use BR tags OR P tags for newlines. Even better you can use both, where one return key press injects a BR tag, and two return key presses will wrap a Paragraph tag. This is great for being able to wrap headers at specific break points all while enjoying the semantic perks of paragraphs.<\/p>\n<\/li>\n In addition to choosing what type of tags to use, you can also change the behavior depending on the type of post, including custom post types. So Pages can default to BR tags, and Blog Posts can default to Paragraph tags.<\/p>\n<\/li>\n If you have existing content that was created before activating this plugin, you can now use the Fixit feature to convert your existing content in a way that makes it render the same as before. Only use this feature (located under Admin > Settings > Writing: Fixing Existing Content) if you are installing this plugin for the first time, otherwise it will remove all of the formatted white space in your posts.<\/p>\n<\/li>\nonclick<\/code> events and style definitions \u2013 not script blocks themselves. To enable this feature you must disable the wptexturize<\/code> and convert_chars<\/code> filters by adding the following code to your theme\u2019s functions.php<\/code>:<\/p>\nremove_filter(\"the_content\", \"wptexturize\");\nremove_filter(\"the_content\", \"convert_chars\");\n<\/code><\/pre>\n
\nI\u2019ve tested it on a variety of code samples and I\u2019m pleased with the results but if you find any content that isn\u2019t preserved just open a support ticket and I should be able to fix it.<\/p>\n\n