Invalid characters on Google structured data

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Dpsachou

    (@dpsachou)

    Forgot to mention that this issue appeared on version 2.5.1

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    So you noticed this 6 months ago, when 2.5.1 was released?

    Could you re-enable so I can see what the structured data-testing tool is complaining about (because I can’t reproduce)?

    Thread Starter Dpsachou

    (@dpsachou)

    Hello,

    I just noticed but this issue did not appear a few days ago, before the update to WordPress 5.3. Tried installing Autoptimize 2.5 and 2.4.4 but the problem remains if I enable “Inline all CSS”. I am guessing maybe a conflict with another plugin causes it, so I will troubleshoot and get back to you.

    Thread Starter Dpsachou

    (@dpsachou)

    It turns out that the issue appears when loading “Font Awesome css lib” in WP Discuz plugin along with “Inline all CSS”. Maybe after a WP Discuz plugin update a week ago.

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    OK, so does excluding WP Discuz from CSS optimization fix that? And do you have an indication of what offending characters are in that Font Awesome CSS lib?

    Thread Starter Dpsachou

    (@dpsachou)

    WP Discuz has an option to disable Font Awesome css, and this fixes the problem. This disables some icons in the comment section, but I can live with that. I have not researched further in the Font Awesome files for the culprit.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Invalid characters on Google structured data’ is closed to new replies.