Parser-blocking from unkwow origin

  • Resolved osoyogui

    (@osoyogui)


    9 years, 2 months ago

    [ Moderator note: moved to Fixing WordPress. ]

    I discover the issue after installing the Amp plugin and the Yoast Glue for Amp plugin, when the Google Search Console give me the error:
    “Javascript code created by user was found” (translated from spanish)

    Then I look for it on the search console and almost at the end of the page I found:

    </amp-analytics>
 <script type="text/javascript">     var loc = (("https:" == document.location.protocol) ? "https://analytics." : "http://analytics.");     document.write(unescape("%3Cscript src='" + loc + "sitewit.com/v3/xxxxxxxxx/sw.js' type='text/javascript'%3E%3C/script%3E")); </script>

    (xxxxxxx is a number)
    I found the same code on the regular page (non AMP) just before the </html> tag:

    <script type="text/javascript"> var loc = (("https:" == document.location.protocol) ? "https://analytics." : "http://analytics."); document.write(unescape("%3Cscript src='" + loc + "sitewit.com/v3/xxxxxxx/sw.js' type='text/javascript'%3E%3C/script%3E")); </script> </body>

    I tried to found which plugin introduces that code, so I disable ALL plugins but the javascript was still there. It seems somebody is tracking my website.

    How can i find which plugin or whatever did introduce that javascript on my site and how can i delete it?

    thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    9 years, 2 months ago

    This may be a plugin or theme conflict. Please attempt to disable all plugins, and use one of the default (Twenty*) themes. If the problem goes away, enable them one by one to identify the source of your troubles.

    Thread Starter osoyogui

    (@osoyogui)

    9 years, 2 months ago

    Hello @sterndata, thank for your answer.

    Finally it was something that my hosting provider introduced when I supossedly turned on any hosting plugin or feature. I asked them to turn it off and it gone with the wind.

    Thanks anyway!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Parser-blocking from unkwow origin’ is closed to new replies.