Apostrophe-Backslash Problem - How-To and Troubleshooting

RE: Apostrophe-Backslash Problem

arena — Sat, 06 Feb 2016 23:04:51 +0000

Posted by: Tom
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.

RE: Apostrophe-Backslash Problem

Tom — Sat, 06 Feb 2016 19:42:31 +0000

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.

RE: Apostrophe-Backslash Problem

arena — Sat, 06 Feb 2016 17:56:13 +0000

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?

RE: Apostrophe-Backslash Problem

arena — Thu, 04 Feb 2016 20:13:30 +0000

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?

RE: Apostrophe-Backslash Problem

arena — Thu, 04 Feb 2016 03:56:11 +0000

Posted by: Tom
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? :/

RE: Apostrophe-Backslash Problem

Tom — Sun, 31 Jan 2016 15:02:27 +0000

Ok, this issue is already fixed. Please wait for the next wpDiscuz version.

RE: Apostrophe-Backslash Problem

arena — Sat, 30 Jan 2016 15:16:26 +0000

Posted by: Tom
@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. http://s12.postimg.org/nni1kiikt/Capture_d_e_cran_2016_01_30_a_12_12_35.png Thanks.

RE: Apostrophe-Backslash Problem

Tom — Sat, 30 Jan 2016 10:42:55 +0000

@arena, What issue do you mean?

RE: Apostrophe-Backslash Problem

arena — Sat, 30 Jan 2016 02:48:31 +0000

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,

RE: Apostrophe-Backslash Problem

Tom — Fri, 29 Jan 2016 18:31:01 +0000

@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

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

If you break it and keep the line-breaks, it becomes this:

Text text text

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
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" ( ) tag in Post content editor to allow authors indicate the correct place of breaking. This avoids un-closed HTML tag problems.