Download
2013-03-16, 19:32:21
(This is something that some users have requested several times in the past...)
I suggest that for some future GS release the content is not stored with addslashes and htmlentities, but as raw HTML.
Of course this would require many plugins to be adapted, so it would be better doing it in a major release (version 4 maybe?).
For backwards compatibility with old page data files without having to run an upgrade script, I can think of 2 ways to handle it:
A) Have a new field, e.g. format. For example:
<format>1</format> = pure HTML
<format>0</format> (or empty or no field) = old-style addslashes+htmlentities
or
B) Use a new field for raw html, e.g. html or htmlcontent.
GS would check if that field exists, else it would use the content field (decoding, etc.)
I suggest that for some future GS release the content is not stored with addslashes and htmlentities, but as raw HTML.
Of course this would require many plugins to be adapted, so it would be better doing it in a major release (version 4 maybe?).
For backwards compatibility with old page data files without having to run an upgrade script, I can think of 2 ways to handle it:
A) Have a new field, e.g. format. For example:
<format>1</format> = pure HTML
<format>0</format> (or empty or no field) = old-style addslashes+htmlentities
or
B) Use a new field for raw html, e.g. html or htmlcontent.
GS would check if that field exists, else it would use the content field (decoding, etc.)
