Merge branch 'main' into 4.8.x

Author: philwareham

help/en-gb_pophelp.xml

@@ -867,7 +867,7 @@ If a form template needs processing (if it contains Textpattern tags), you must
 <ul>
     <li>When using low load order plugins as tag attributes</li>
     <li>Code replacements inside <code>&lt;txp:php&gt;</code> tags</li>
-    <li>Skipping page elements earlier in the page so they may receive content that is derived from a tag that is processed later<</li>
+    <li>Skipping page elements earlier in the page so they may receive content that is derived from a tag that is processed later</li>
 </ul>
 <p>Textpattern has traditionally run one extra sweep (called ‘secondpass’) for legacy reasons, hence the default value of this preference being <code>1</code>. More sweeps, however, increase the chances of unintended tags slipping through and being processed. Recent improvements in the tag parser have reduced the need for this second pass. So, unless you are using the second sweep for a dedicated reason, please reduce this value to <code>0</code> to make your site more secure.</p>
 <p>If you subsequently find unprocessed tags being rendered on your website (and there are no other tag errors shown in Testing/Debugging modes due to mismatched tag pairs) then please contact us with your page template/code/plugin example. We are trying to eradicate the need for extra parser passes, and this information will help us achieve that.</p>

help/en-us_pophelp.xml

@@ -867,7 +867,7 @@ If a form template needs processing (if it contains Textpattern tags), you must
 <ul>
     <li>When using low load order plugins as tag attributes</li>
     <li>Code replacements inside <code>&lt;txp:php&gt;</code> tags</li>
-    <li>Skipping page elements earlier in the page so they may receive content that is derived from a tag that is processed later<</li>
+    <li>Skipping page elements earlier in the page so they may receive content that is derived from a tag that is processed later</li>
 </ul>
 <p>Textpattern has traditionally run one extra sweep (called ‘secondpass’) for legacy reasons, hence the default value of this preference being <code>1</code>. More sweeps, however, increase the chances of unintended tags slipping through and being processed. Recent improvements in the tag parser have reduced the need for this second pass. So, unless you are using the second sweep for a dedicated reason, please reduce this value to <code>0</code> to make your site more secure.</p>
 <p>If you subsequently find unprocessed tags being rendered on your website (and there are no other tag errors shown in Testing/Debugging modes due to mismatched tag pairs) then please contact us with your page template/code/plugin example. We are trying to eradicate the need for extra parser passes, and this information will help us achieve that.</p>

help/en_pophelp.xml

@@ -867,7 +867,7 @@ If a form template needs processing (if it contains Textpattern tags), you must
 <ul>
     <li>When using low load order plugins as tag attributes</li>
     <li>Code replacements inside <code>&lt;txp:php&gt;</code> tags</li>
-    <li>Skipping page elements earlier in the page so they may receive content that is derived from a tag that is processed later<</li>
+    <li>Skipping page elements earlier in the page so they may receive content that is derived from a tag that is processed later</li>
 </ul>
 <p>Textpattern has traditionally run one extra sweep (called ‘secondpass’) for legacy reasons, hence the default value of this preference being <code>1</code>. More sweeps, however, increase the chances of unintended tags slipping through and being processed. Recent improvements in the tag parser have reduced the need for this second pass. So, unless you are using the second sweep for a dedicated reason, please reduce this value to <code>0</code> to make your site more secure.</p>
 <p>If you subsequently find unprocessed tags being rendered on your website (and there are no other tag errors shown in Testing/Debugging modes due to mismatched tag pairs) then please contact us with your page template/code/plugin example. We are trying to eradicate the need for extra parser passes, and this information will help us achieve that.</p>