<![CDATA[Changing the closing tag on a XML file, so it matches the opening tag, with notepad++ -]]>I have a issue, i have a big XML file, and using notepad++.

I have this XML syntax:

   <wp:postmeta-ingredients>
    <wp:meta_key><![CDATA[ingredients_list_0_name]]></wp:meta_key>
    <wp:meta_value><![CDATA[Tészta]]></wp:meta_value>
    </wp:postmeta>

What i want, is to change the closing tag to:

    <wp:postmeta-ingredients>
    <wp:meta_key><![CDATA[ingredients_list_0_name]]></wp:meta_key>
    <wp:meta_value><![CDATA[Tészta]]></wp:meta_value>
    </wp:postmeta-ingredients>

I have other data like this:

    <wp:postmeta>
    <wp:meta_key><![CDATA[ingredients_list_0_ingredients_1_quantity]]></wp:meta_key>
    <wp:meta_value><![CDATA[2000]]></wp:meta_value>
    </wp:postmeta>

That i want to keep the same. So its just when the opening tag is starting with:

<wp:postmeta-ingredients>

How do i do this in notepad++, have to be with “replace all”

Thanks.

]]>https://community.notepad-plus-plus.org/topic/22534/changing-the-closing-tag-on-a-xml-file-so-it-matches-the-opening-tag-with-notepadRSS for NodeThu, 17 Sep 2026 00:33:56 GMTWed, 09 Feb 2022 15:57:58 GMT60<![CDATA[Reply to Changing the closing tag on a XML file, so it matches the opening tag, with notepad++ - on Fri, 11 Feb 2022 14:03:17 GMT]]>@peterjones said in Changing the closing tag on a XML file, so it matches the opening tag, with notepad++ -:

FIND = (?s)wp:postmeta-ingredients.*?\K</wp:postmeta>
REPLACE = </wp:postmeta-ingredients>
SEARCH MODE = Regular Expression
REPLACE ALL (because of \K, hitting REPLACE multiple times will not work)

Ehh, wow, fast and correct answer, worked like a charm.
Super impress of the quality here.

Thank you so much Peter :)

]]>https://community.notepad-plus-plus.org/post/74063https://community.notepad-plus-plus.org/post/74063Fri, 11 Feb 2022 14:03:17 GMT<![CDATA[Reply to Changing the closing tag on a XML file, so it matches the opening tag, with notepad++ - on Wed, 09 Feb 2022 16:09:37 GMT]]>@nrh_10_2022

Thank you for showing before and after data, in boxes, with data that should match and data that shouldn’t. It makes your question easier to understand.

If I have

<wp:postmeta-ingredients>
<wp:meta_key><![CDATA[ingredients_list_0_name]]></wp:meta_key>
<wp:meta_value><![CDATA[Tészta]]></wp:meta_value>
</wp:postmeta>

<wp:postmeta>
<wp:meta_key><![CDATA[ingredients_list_0_ingredients_1_quantity]]></wp:meta_key>
<wp:meta_value><![CDATA[2000]]></wp:meta_value>
</wp:postmeta>

<wp:postmeta-ingredients>
<wp:meta_key><![CDATA[ingredients_list_0_name]]></wp:meta_key>
<wp:meta_value><![CDATA[Tészta]]></wp:meta_value>
</wp:postmeta>

<wp:postmeta>
<wp:meta_key><![CDATA[ingredients_list_0_ingredients_1_quantity]]></wp:meta_key>
<wp:meta_value><![CDATA[2000]]></wp:meta_value>
</wp:postmeta>
  • FIND = (?s)<wp:postmeta-ingredients>.*?\K</wp:postmeta>
  • REPLACE = </wp:postmeta-ingredients>
  • SEARCH MODE = Regular Expression
  • REPLACE ALL (because of \K, hitting REPLACE multiple times will not work)

becomes

<wp:postmeta-ingredients>
<wp:meta_key><![CDATA[ingredients_list_0_name]]></wp:meta_key>
<wp:meta_value><![CDATA[Tészta]]></wp:meta_value>
</wp:postmeta-ingredients>

<wp:postmeta>
<wp:meta_key><![CDATA[ingredients_list_0_ingredients_1_quantity]]></wp:meta_key>
<wp:meta_value><![CDATA[2000]]></wp:meta_value>
</wp:postmeta>

<wp:postmeta-ingredients>
<wp:meta_key><![CDATA[ingredients_list_0_name]]></wp:meta_key>
<wp:meta_value><![CDATA[Tészta]]></wp:meta_value>
</wp:postmeta-ingredients>

<wp:postmeta>
<wp:meta_key><![CDATA[ingredients_list_0_ingredients_1_quantity]]></wp:meta_key>
<wp:meta_value><![CDATA[2000]]></wp:meta_value>
</wp:postmeta>

The regex is looking for <wp:postmeta-ingredients> followed by any character(s) before the first </wp:postmeta> it reaches; then it resets (so all the stuff that’s matched so far will not be replaced), then matches </wp:postmeta>, and replaces just that last part of the match with </wp:postmeta-ingredients>.

Barring unforeseen on edge cases, I think this should work for you.

]]>https://community.notepad-plus-plus.org/post/73967https://community.notepad-plus-plus.org/post/73967Wed, 09 Feb 2022 16:09:37 GMT