Why are HTML comments and CDATA removed?

Hello @cliffpaulick – It seems like the code in the screenshot is more likely from a different plugin or entered manually OR it could be a plugin conflict error with the Header Footer Code Manager plugin.

We tested this on our end and we were unable to replicate the issue. All HFCM Snippets are preceded & succeeded by HTML Comments which indicate the start and the end of the snippet along with the snippet ID.

Example:

<!– HFCM by 99 Robots – Snippet # 3: Comments –> —> BY THE PLUGIN
<!– This is An HTML Comment –>
<script type=”text/javascript”>
/*<![CDATA[*/
var google_coversion_id=999898989989;
/*]]*/
</script>
<!– /end HFCM by 99 Robots –> —> BY THE PLUGIN

We do not see those in the screenshot shared either. This is why we are inclined to think this might be a plugin or theme conflict.

After exhausting all other forms of debugging it might be best to check for plugin or theme conflicts. Plugin or theme conflicts can cause our product to function unexpectedly or not at all, which is why testing for this conflict is very important.

​We recommend that you perform this test on your staging site and that you backup your site. If you do not have a staging site then you might not be able to perform this test as deactivating plugins or your theme will greatly impact the look and functionality of your site.

Before you perform this test please make sure you have the latest version of our product, WordPress and PHP.

1. Deactivate all other plugins on your site besides our plugin
2. Test to see if the plugins features work as you would expect.  If they do work then you have a plugin conflict. You should now activate each plugin on your site one by one until our plugin’s features do not work. This will help you determine what plugin exactly is causing the conflict.
3. If our product still is not functioning properly, then you can try to deactivate your theme to see if there is a theme conflict. This is the last resort and should only be done if you have a staging site or your site has not gone live yet. If our product works after deactivating your theme then you have a theme conflict, but if our product still does not work then it appears that our product has a bug.
4. If you have completed all of these tests and our product does not function properly with a default WordPress theme like twenty seventeen and all plugins deactivated, then it seems that our product has a bug and we will continue to work with you to solve this issue.

Please let us know if you have any questions about this conflict testing procedure.

• This reply was modified 6 years, 11 months ago by DraftPress Support Team.
• This reply was modified 6 years, 11 months ago by DraftPress Support Team.