I've read the release notes for the last few versions of the editor and could not find entries adressing php tag replacement with special chars.
Can the editor now be configured to leave PHP scripts/tags ,contained in the loaded content, alone; or does the source have to be manually edited to get this functionality?
Can the editor now be configured to leave PHP scripts/tags ,contained in the loaded content, alone; or does the source have to be manually edited to get this functionality?
RE: Status of PHP tag encoding by 2.0FC-Editor
Hello,
I don't have a definitive answer for you but I have experimented a little for my own use on a similar theme. I use the editor for creating templates and have some variables inserted that are not html. I found that the editor stripped everything that it didn't like and not correct html. This was very irritating to me and seems like something that definately should be configurable. Not everyone wants to use the editor for only totally valid html. I found later however that if you change the XHTML values in fckconfig.js to false then it no longer messes with the content or at least not as much it seems. I was then able to embed my variables (that later get replaced before it ever comes visible to the world as a real html document). I did find that the editor tend to mess with content and in my opinion it would be better to have it configurable to be hands off unknown content.
Maybe this helps you as well...
Chris
RE: Status of PHP tag encoding by 2.0FC-Edito
What I would fine very handy to use is either an option to avoid parsing <?php ?> tags, or a special tag, let's say <code> </code> (like now is treating SCRIPT and STYLE tags) where I can insert some php without getting parsed.I don't understand right now where in the code recognizes SCRIPT and STYLE tags to let them remain untouched during the XHTML. ( getXHTML is inside _source/fckxhtml.js but where it set's special tags to be script and style ? )