Need help? Check out our Support site, then

Please do not delete XML from my [sourcecode language='xml'] portions

  1. See

    Please get back to me on this, as it is very irritating that WordPress kills all but the most basic XML from sourcecode language=xml fragments.

    Blog url:

  2. Can you please give us a link to a post or page where this isn't working?

  3. Any new post that I try to do with the WordPress "HTML" markup that contains a correctly tagged sourcecode XML block consistently fails.

    Example post is in

    Please follow the link in my opening post to get a feel for what I already know.


  4. Is the example included at the bottom of your .doc file what you were trying to post?

  5. @jpluimers: I checked the file that you reference and the reason why it's not posting correctly is because of a spelling error, your code snippet should start with "sourcecode" (currently it starts with "sourececode"). Once you correct that typo, the code snippet works ;)

  6. that was a typo, but this post isn;t, and all of the XML but the first line is gone:

    That is consistent (just search my blog for XML

    You will see that almost all XML is gone. I even went so far as to replace less than and greater than with braces (but that looks so odd that I stopped with that too).


  7. Had the XML appeared properly in the past?

  8. Ok, so this has happened since you first started posting XML, it wasn't a recent development?

    If it was recent, do you know about when it started?

  9. I have no idea when it started, it has been there all the time and needs to be fixed.

  10. I have no idea when it started, it has been there all the time and needs to be fixed.

    Can you save a post draft with the XML source code using the Text editor, making sure not to switch to the Visual Editor, then reply to this forum thread so I can try to reproduce this on my end?

  11. For instance this post:

    it has two XML parts that got truncated, that you can download here:
    and here:

    And this post:

    for which the XML is here:

    Note that it has to do with the visual editor, but it is virtually impossible to avoid the visual editor as the text editor does not support keyboard shortcuts for editing links, formatting, etc.

  12. Hi,

    Thanks for replying with the Pastebin examples. I tried the first one in a test post in the Text editor, then previewed the post successfully (in a new browser tab).

    Next, on the Edit Post screen, I switched to the Visual editor (screenshot), then previewed the post again, and the result was still the same (screenshot).

    Can you make sure that in the shortcode language option that you're enclosing the "xml" syntax in double quotes? I've annotated it in the first screenshot.

  13. I re-edited the post and now it works.

    Something must have changed, just check out the revisions (see below).

    This is the text now:
    This is the visual now:
    This is the published page now:

    This is the revision list: 20120824 clearly broke it again:

    This is the broken copy:
    This was the OK copy from the text editor on 20120824:
    This is part of the diff (it also mangled with the html on the same page):

    The odd thing is: today I did the same actions as 20120824, and now it works. Very strange: something must have changed somewhere.


  14. I'm glad to hear that it works! I'll go ahead and mark this as resolved.

    We deploy updates to many times daily, so it's tough to say what might've happened without more details to investigate.

    If you come across this again in the future, please post here again (or in a new forum thread) to let us know the exact steps you're taking so we can try to reproduce it on our end.

  15. Thanks, will do.
    Any place I can see which updates have been applied to
    And: any chance for a response on the keyboard focus issue here:
    Thanks again!

  16. We typically don't announce minor updates, as those happen several times per day, but you can always read about major updates at

    As for the other thread, we're looking into it.

  17. thanks, that blog is on my roll now.

  18. Sounds good — cheers Jeroen! :-)

Topic Closed

This topic has been closed to new replies.

About this Topic