🕸Fergus Duniho wrote on Tue, May 24, 2016 04:08 PM UTC:
Re-editing.
It looks like the problem was actually something in my config file. After I changed it back, I neglected to refresh the page and flush the cache. Since this is JavaScript, I need to do that to see changes.
I have just gotten this to open in Source mode instead of WYSIWIG mode. I will enter a FIGURE tag as a test, since that got wiped from some of my HTML yesterday.
King
As long as I viewed this as Source, it did not change my HTML, but once I switched to WYSIWIG and then switched back to Source, it removed the FIGURE and FIGCAPTION tags, putting a P tag around the image and another around the caption. So, having the editor open in Source is part of the solution. You should be able to safely use HTML without it changing so long as you avoid using the WYSIWIG mode.
As another test, I am adding another FIGURE tag. This time I have added a new line to the configuration file to allow all content. Let's see if that helps.
Queen
This time, when I switched to WYSIWIG and back, it changed my uppercase HTML to lowercase XHTML and added some line breaks, but it otherwise left my HTML alone.
Lastly, I edited it to close tags with just a greater than sign, and not to add a slash before the greater than sign. Now I should configure individual pages, so that it opens in WYSIWIG for new comments and in Source for editing content or for posting pages.
One more test. Here is the same figure code with the piece class added.
Queen
Â
While it left the class intact, this class needs to be followed by , and it changed that to
,then later got rid of the , which did not do the job of . So I need to find a way to preserve that.
Re-editing.
It looks like the problem was actually something in my config file. After I changed it back, I neglected to refresh the page and flush the cache. Since this is JavaScript, I need to do that to see changes.
I have just gotten this to open in Source mode instead of WYSIWIG mode. I will enter a FIGURE tag as a test, since that got wiped from some of my HTML yesterday.
King
As long as I viewed this as Source, it did not change my HTML, but once I switched to WYSIWIG and then switched back to Source, it removed the FIGURE and FIGCAPTION tags, putting a P tag around the image and another around the caption. So, having the editor open in Source is part of the solution. You should be able to safely use HTML without it changing so long as you avoid using the WYSIWIG mode.
As another test, I am adding another FIGURE tag. This time I have added a new line to the configuration file to allow all content. Let's see if that helps.
Queen
This time, when I switched to WYSIWIG and back, it changed my uppercase HTML to lowercase XHTML and added some line breaks, but it otherwise left my HTML alone.
Lastly, I edited it to close tags with just a greater than sign, and not to add a slash before the greater than sign. Now I should configure individual pages, so that it opens in WYSIWIG for new comments and in Source for editing content or for posting pages.
One more test. Here is the same figure code with the piece class added.
Queen
Â
While it left the class intact, this class needs to be followed by
, and it changed that to
,then later got rid of the , which did not do the job of. So I need to find a way to preserve that.