OTS parsing error: invalid version tag

  • Resolved kvv213

    (@kvv213)


    7 years, 10 months ago

    Hello everyone!

    I’m trying to tune my WordPress blog and remove all disturbance I have in the code. Firt of all I see that every single page of my blog returns the following error:
    OTS parsing error: invalid version tag

    After a short review of the origin of this problem I found out that it belongs to JetPack Social Logos sub-plugin. And the problem is in declaration of font-face. The right version of declaration is:

    @font-face {
	<strong>font-family:"social-logos";</strong>
	src:url("social-logos.eot?51b607ee5b5cb2a0e4517176475a424c");
	font-weight:normal;
	font-style:normal;
}

    and it is used in social-logos.css

    but my browser uses different, condenced css file from the same JetPack dir social-logos.min.css. And here we have wrong definitions of the fonts:
    @font-face{font-family:social-logos;src:url(social-logos.eot?51b607ee5b5cb2a0e4517176475a424c);font-weight:400;font-style:normal}

    No aposraf/quotes around social-logos font definition.

    What can I do in order to fix that?

    PS. I don’t use CDN and my Browser is Yandex.Browser (Chrome clone).

    • This topic was modified 7 years, 10 months ago by kvv213.
Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Thanks for the report!

    Could you try to copy the contents of social-logos.css into social-logos.min.css, and let me know if the problem disappears?

    Thanks!

    Thread Starter kvv213

    (@kvv213)

    Hmmm… I’ve done that and check that the browser loaded the right CSS (with good font-face declaration). But… The problem still there and I don’t see other reasons for it. May be it is connected with the same error that is connected with Social-Logos?

    I see also this error in the console:
    Failed to decode downloaded font: https://blog.kvv213.com/wp-content/plugins/jetpack/_inc/social-logos/social-logos.eot?51b607ee5b5cb2a0e4517176475a424c

    The browser can’t decode eot font from the same dir…

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Could you try to switch to one of the default themes, like Twenty Sixteen, for a few minutes, and let me know if the problem remains?

    Thread Starter kvv213

    (@kvv213)

    Sorry, switching to another theme is not possible… Current theme is based on Twenty Twelve (slightly modified).

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Understood. We’ll see if there is something we can do on our end to reproduce this.

    I see you’re using a caching plugin; could you try to deactivate it and let me know how it goes?

    Thread Starter kvv213

    (@kvv213)

    Checked with disablesh cache – nothing happened.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    BY “nothing happened”, do you mean that the error is still there?

    Thread Starter kvv213

    (@kvv213)

    Yes, the error is still there.
    The mistake

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Thanks for the extra details. At this point, I’m afraid I don’t have any other ideas to solve this issue. We may, however, get rid of that part of the code in a future Jetpack release, thus resolving this issue in the process. You can follow our progress here:
    https://github.com/Automattic/jetpack/issues/7148

    I’ll let you know as soon as we make progress on this.

    Thread Starter kvv213

    (@kvv213)

    I think we can wait for the next “release” of JetPack thus the error is not critical.

    Thank you!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘OTS parsing error: invalid version tag’ is closed to new replies.

Tags