Slashes added behind Apostrophes in First Comment Field

[richn]

When saving content in the First Comment field, apostrophes are being escaped and displayed incorrectly after saving.

Example entered:

It's previously hidden conditions becoming visible once work begins.

After saving and reopening, the text appears as:
It\'s previously hidden conditions becoming visible once work begins.

In some cases multiple backslashes are added.

The issue appears to be limited to the First Comment field. I have not observed the same behavior in the main LinkedIn post text.

Steps to reproduce:

1. Open a scheduled social media post.
2. Enable First Comment.
3. Enter text containing apostrophes (It's, isn't, don't, etc.).
4. Save Draft.
5. Reopen the scheduled post.

Expected result:
Apostrophes remain unchanged.

Actual result:
Backslashes are inserted before apostrophes and are displayed in the editor.
eg., (It\'s, isn\'t, don\'t, etc.).

[Blog2Social Support]

Hi,

Thank you for your message and for the example.

This is not the regular behavior in a standard WordPress environment. Blog2Social does not intentionally remove punctuation or spacing from the social description.

In many cases, this kind of issue is caused before the text is processed by Blog2Social, for example by the theme, the way the article content is structured, or by another plugin that generates or modifies Open Graph/social metadata. If headings, paragraphs or line breaks are converted into plain text without proper spacing, the generated description may appear merged.

As a workaround, you can manually edit the social description in Blog2Social before publishing and add the missing punctuation or spacing there.

We recommend checking whether the issue is related to the active theme or another plugin that generates Open Graph/social description data. You can also test this in a standard WordPress environment or with a default WordPress theme to compare the result.

If you can narrow the issue down to a specific theme or plugin, please let us know the name of the theme/plugin and send us the affected post URL and a screenshot of the generated description. We can then try to reproduce the behavior on our side.

Best regards,
Blog2Social Support