Support » Plugin: Jetpack by WordPress.com » pixel.wp.com

  • Resolved Oclair

    (@oclair)


    We have removed Jetpack and Akismet and are not running any plugins from auttomatic, why is our admin pages connecting to pixel.wp.com when we update our plugins? We are hosting our websites on our own server.

    Thank you for the clarification
    OC

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    Hi there!

    If you’ve deactivated the Jetpack plugin from your site, it will not be able to load any resources from that domain on your site. This is consequently added by another plugin on your site. We can’t really tell without knowing what plugins you use, but I do know that the WooCommerce plugin does include such a feature. Do you happen to use the WooCommerce plugin on your site?

    If you don’t, I would recommend that you deactivate each and every plugin on your site, one at a time, until you find what’s making that call.

    I hope this helps.

    Oclair

    (@oclair)

    Well I found the answer somehow… the plugin had replaced the code we had on our page to what below is the code for a single image.

    Is it the intent that folks who deactivate Jetpack need to re-link all their images back to their own media library?

    <img class="size-medium wp-image-4852 imgborder alignright" src="https://www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01-300x225.jpeg" sizes="(max-width: 300px) 100vw, 300px" srcset="https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?resize=300%2C225&ssl=1 300w, https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?resize=640%2C480&ssl=1 640w, https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?resize=99%2C74&ssl=1 99w, https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?resize=32%2C24&ssl=1 32w, https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?w=800&ssl=1 800w" alt="WieAllesBegann_01" data-attachment-id="4852" data-permalink="https://www.dancingshiva.at/about/wieallesbegann_01/" data-orig-file="https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?fit=800%2C600&ssl=1" data-orig-size="800,600" data-comments-opened="0" data-image-meta="{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;Canon MP640 series&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;}" data-image-title="WieAllesBegann_01" data-image-description="" data-medium-file="https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?fit=300%2C225&ssl=1" data-large-file="https://i2.wp.com/www.dancingshiva.at/wp-content/uploads/2012/10/WieAllesBegann_01.jpeg?fit=640%2C480&ssl=1" width="300" height="225">

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    The i2.wp.com images are part of our image CDN feature: https://jetpack.com/support/site-accelerator/

    When enabled, we replace all image URLs with the CDN URL on page load, we do not directly edit the content. That way, when disabled, the images will return to loading from your server under their local URLs.

    Oclair

    (@oclair)

    The page this code was copied from is back from 2012, at some point things got wonky I assume. I need to re-link the images back to the media library.

    Thanks for the responses!

    >Do you happen to use the WooCommerce plugin on your site?

    Yes that may explain the pixel issue!

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    Interesting, did you directly modify the page’s code to specifically include the CDN image URLs?

    There’s nothing in Jetpack that modifies saved page content itself with the CDN image URLs, that’s all triggered on page view. Underneath, the local image URLs are still stored in the page content itself.

    Because of how that works, if the page content was specifically modified to have the CDN image URLs, we’d have no way of changing them back to the local image URL, and then of course deactivating Jetpack would break the connection with the CDN and thus any CDN images manually inserted like that.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.