Small issue with the new rich text editor.
If someone comments using markdown the following comment:
> Some quoted text
My reply goes here
It should be turned into
<blockquote>Some quoted text </blockquote> My reply goes here
However instead it gets turned into
<blockquote>Some quoted text
My reply goes here
</blockquote>
Hi @leovictoria,
We don't find such an issue on our test website,
Please watch the video below:
https://www.screencast.com/t/0XSG7R8qZVW
The test comment can be found here: https://wpdiscuz.com/demo/#comment-484
Your test site does not seem to process markdown at all as shown in your video
To clarify, I have the rich text editor enabled, but I am not using the button to make the quote, I am just using markdown (>). On my site it correctly turns it into a blockquote, but it sucks up all subsequent lines as well rather than just the current line as it should.
Could you please leave us some example URL to allow us to check the issue?
@asti Sure. https://househuntvictoria.ca/2020/06/12/napkin-math-on-forced-selling/#comments
If I enter
> test quote
Test comment
It quotes the whole comment text, not just the first line as intended. It works fine in the plain comment editor.
There is some other plugin that caused the issue. Please deactivate the plugins one by one and check after each activation to find a problem maker.
Please check it here, you'll see there is not such an issue:
Please don't forget to press Ctrl+F5 on the frontend each time before checking.
@asti It works perfectly when the rich text editor is disabled, which I've done to preserve the commenting experience for my readers.
I'm not sure why you are referring to it working on your demo site. Your demo site does not process Markdown syntax at all. If I type "> test quote" it doesn't turn it into a blockquote at all, it just leaves the >.
I'm not sure why you are referring to it working on your demo site. Your demo site does not process Markdown syntax at all. If I type "> test quote" it doesn't turn it into a blockquote at all, it just leaves the >.
The same is on all our test websites. There is not such an issue. We've checked many times. That's why we asked you to deactivate the plugins and check again. One of your active plugins causes the issue.
