Template-protected edit request on 23 April 2024[edit]
Please remove all of the "contents" field on the documentation template call so that the documentation subpage can be created easily. Awesome Aasim 23:54, 23 April 2024 (UTC)
- Completed – see Template:Sanction enforcement request footer/doc. P.I. Ellsworth , ed. put'er there 01:55, 24 April 2024 (UTC)
Sandbox missing /p tag error[edit]
When the lorem ipsum content is trimmed in the sandbox, it causes a missing </p>
error. I fixed it, but the error was reinstated. Please find a way to avoid this error. – Jonesey95 (talk) 13:30, 26 April 2024 (UTC)
- To editor Jonesey95: when the
|trim=yes
parameter and arg are removed from the {{Word count}} template, the lint error is fixed. Perhaps there is an issue in the Word count module? P.I. Ellsworth , ed. put'er there 14:20, 30 April 2024 (UTC)
- Also, the module is safe-substituted in the {{Word count}} template, so when subst. in the sandbox, the error is removed even when one begins with
|trim=yes
. One thing I find weird is that the /doc for the "Word count" template uses the unsubst. template with one case of|trim=yes
, but does not show the same error as this sandbox shows under the same conditions. ??? P.I. Ellsworth , ed. put'er there 14:51, 30 April 2024 (UTC)
- Maybe editors Martin and Awesome Aasim can shed some light on what might be an issue with the Word count module? P.I. Ellsworth , ed. put'er there 14:57, 30 April 2024 (UTC)
- Yes, I understand why it happened. The word count template trims at a word boundary, and in the {{lorem ipsum}} template, each paragraph starts with
<p>
. Trimming in the middle of a paragraph leaves that open p tag unclosed. Trimming in the middle of someone's request could have the same effect, so trimming seemed undesirable. I fixed it here, but my edit was reverted, restoring the error. Rather than edit war, I came here to discuss possible resolutions. – Jonesey95 (talk) 15:22, 30 April 2024 (UTC)- Gnarly little challenge, eh? I went ahead and self-reverted, because subst. Word count lost the trim, and I want the problem to be easily found. P.I. Ellsworth , ed. put'er there 19:14, 30 April 2024 (UTC)
- I have documented the potential for errors caused by
|trim=yes
over at {{word count}}. I don't think there is an error-free way to cut off wikitext at a numerically chosen point. Maybe this discussion could be continued over at that template's talk page. In the meantime, now that the risk is documented there, I have once again removed the error condition from the sandbox. That error should, of course, not be put into the live template. – Jonesey95 (talk) 20:38, 30 April 2024 (UTC)- Don't think AA meant to introduce all that to the live template. I think he was just experimenting. I saw your addition to the Wc /doc – definitely a needed bit of info. If there's a way to add a </p> to the module's trim, only a Lua expert would know. Above my paygrade for sure. Thank you for your diligence in all this! P.I. Ellsworth , ed. put'er there 22:17, 30 April 2024 (UTC)
- I have documented the potential for errors caused by
- Gnarly little challenge, eh? I went ahead and self-reverted, because subst. Word count lost the trim, and I want the problem to be easily found. P.I. Ellsworth , ed. put'er there 19:14, 30 April 2024 (UTC)
- Yes, I understand why it happened. The word count template trims at a word boundary, and in the {{lorem ipsum}} template, each paragraph starts with