[eluser]domainsvault[/eluser]
Its been a while since I've used either editor. But from what I remember of them thats in part the editors themselves. It could also be CI too, if your posting your data through the "form" helper and having validation done on posts before storage. Though then again validation won't convert the data I don't believe.
All in all though whats basically happening is when the data is being submitted your editors being the likely culprits are running the data through htmlentities and or htmlspecialchar which basically takes the data and makes it "safe" to store. I enclose safe in quotes cause all in all you can store whatever you want in the DB in any form even raw html and thats perfectly fine. However the logic is typically if theres a way for a user to submit something to a script for processing be it to display on page instantly or store it in a DB then you want to sanatize the inputs so no one attempts to maliciously cause your page harm by injecting code to do such things.
if your storing your input in a DB its best to just let it be. However if your doing this in a sense to be able to go into your code at later dates remotely for example or you want to allow users to post html and you can trust them to not do something foul, then you can always run your input though html_entity_decode when displaying it back on the page later when calling it back out through the DB. This way it won't look like printed code on the screen it should work as normal html.
Side note: storing PHP and expecting it to work within the html won't work PHP renders upon initial load, and if you echo out a string with php code in it from a DB, it will render it out as a string not working code. Also its fairly unlikely it has anything to do with how your server is configured..
