-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strikethrough in unordered list crashes page #24
Comments
I can reproduce the issue on a rather clean install of Dokuwiki and commonmark plugin. |
I cannot reproduce the issue on my 2 production wikis running commonmark plugin v2022-10-08 on DW v2022-07-31b on PHP 7.4. |
Did you remove the spaces around baz in the example above in order for the strikethrough syntax to trigger? In case this is a version issue, my environment is as follow:
|
I had not removed the spaces. Thanks for pointing this out. So, with my Commonmark plugin v2022-10-08 on DW v2022-07-31b on top of PHP 7.4 the source <!DOCTYPE markdown>
- foo
- bar
- ~~baz~~ falsely renders as <ul>
<li class="level1"><div class="li"> foo</div>
</li>
<li class="level1"><div class="li"> bar</div>
</li>
<li class="level1"><div class="li"> </div>
</li>
</ul>
<p>
<del>baz</del>
</p> but no fatal error. |
the problem can be mitigated by putting a backslash before the strikethrough. - foo
- bar
- \~~ baz ~~ I'll try and find an easy way to automatically find and add a backslash on saving as a stopgap solution. right now, i'm doing it client side which is super not ideal but prevents accidental breakages here's my log im using i'm using dokuwiki 2023-04-04a php 8.2
|
This bug has been fixed by PR #22, which has been merged in the main branch of code, but is not yet in a released version of the plugin. |
Steps to reproduce:
add a strikethrough to a bullet point
error produced
page is unreachable, error message is displayed instead
I'm using a few other plugins and havent checked if the error is reproducable on a clean install yet. I'll look into this further when i get a chance
The text was updated successfully, but these errors were encountered: