Hello!
I got this problem on every comment reply and I don't know how to solve it.
I don't have this issue on new posts but only when I want to reply to a comment.
Thanks for your help.
I only get this when I edit and save a comment. When I reply or type in a new comment it's fine.
'test' as a comment saves fine but if I edit it and save then I get:
'test
As seen on this page here
I'm using a themify theme, there could be a conflict which would explain the variations in terms of when this happens?
Thank you for letting us know about this problem.
This problem is already fixed. Please wait for next version. It includes all changes.
@Cliveeee 2. When you select to only allow a fixed number of words / characters in a comment (which then presents 'load more . . .') the text in the comment is missing all formatting, including new lines - which makes some comments pretty much nu-readable until you click the 'load / read more' link.
This is not a bug. This is a standard content braking logic. If we keep HTML tags, e.g. paragraphs, the comment list will be damaged and you'll see totally mixed layout. For example. comment content is this:
Text text text <p>text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text</p>
If you break it and keep the line-breaks, it becomes this:
Text text text <p>text text text text text text text text text text text text text text text text text text text text Read More
As you see the closer </p> tag doesn't exist, it'll affect all HTML structure of your comment list. And now imagine this problem with all other tags... The result will be terrible. As you may know, WordPress Post excerpt works exactly like wpDiscuz comment excerpt, there is nothing unusual and wrong here. WordPress couldn't solve this issue and they added "More" ( <!--more--> ) tag in Post content editor to allow authors indicate the correct place of breaking. This avoids un-closed HTML tag problems.
I have this issue when editing a comment but I did not find a way to solve this.
Can you please tell me what's wrong in this case?
Regards,
@arena, What issue do you mean?
I have a backslash just before the apostrophe when I edit a comment and even if I go back to remove it/them, it doesn't change and the backslash still in the comment.
See capture.
Thanks.
Ok, this issue is already fixed. Please wait for the next wpDiscuz version.
Ok, this issue is already fixed. Please wait for the next wpDiscuz version.
Any due date for the new one because this issue is terrible annoying? :/
This problem occurs after editing a comment and just after saving.
Apparently, there is a work around which is available on "Codex" and deactivating the magic_quote in the file php.ini can solve this issue but I don't have this issue if I use the WP native comment system.
Do you have any due date to solve this issue?
I'm still have an issue with this apostrophe and it becomes terrible annoying.
I don't have this issue on the native comment system so I presume, it comes from your plugin...
Can you please tell us when the new version will be available?
Hi arena,
You can simple deactivate wpDiscuz till next release if this issue is so annoying. I can't say an exact date of the next version release. However I can say it'll be released within next week for sure.
Hi arena, You can simple deactivate wpDiscuz till next release if this issue is so annoying. I can't say an exact date of the next version release. However I can say it'll be released within next week for sure.
Deactivate your comment system is not the solution because I'm using the reply system and the members are now accustomed to the new system and I don't want to bother them with this change...
I will wait your next release then.