albie2011

Vele dank, I have sent the message to the hosting provider as indicated to see what they say (Convesio.com). Will let you know and thank you. Tot later.

Oddly, turning off stats remove all three pixel loads altogether. So I think something must be amiss on this site. I also updated to the latest Jetpack and still see the same issue.

Thank you. I use stats but not Comments or the Like button. So I’m still not sure why three are loading. The other items I am using are as follows – I think I have this same set at another site and it doesn’t load the gif.g three times.

Asset CDN
Custom CSS
Enhanced Distribution
Extra Sidebar Widgets
Image CDN
JSON API
Lazy Images
Monitor
Protect
Shortcode Embeds

It is loading fine – the problem is that there are three loads per page load of a similar link – the poster above said it was three different reasons for it to load. I was trying to figure out why it would load 3 times so I could remove the other loads. My other WP sites do not load the pixel 3 times.

Thank you. Is there a way to determine what is generating each one? I don’t have this issue on any of my other WP sites so I assume I have things turned on that I need to turn off. I checked Debug mode in Jetpack and believe I have only the modules I need on at this time. Any additional information would be appreciated.

Is an update coming soon? If not I have to revert to older version as I need to see my stats.

I am seeing the same exact issue on my site

This is resolved, it was correct on my site. I didn’t detect the <h1> in the code as I was searching for just <h1> but it was actually in a <h1 class=…. type code so I didn’t see it with a Find search. Hope that helps others trying to confirm they are handling things correctly. Thanks Yoast for the prompt response, appreciated as always!

Thank you. What I am referring to is the “About” page and “Contact” page Schema classifications that other plugins support by selection (i.e., you designate which page is your About page and your Contact page and then the output identifies those specific pages as such).

https://schema.org/AboutPage

https://schema.org/ContactPage

Is this something Yoast plans to support?

Having same issue here on Blog Publisher logo on my home page – it would say for BlogPosting Publisher ‘logo.itemtype has an invalid value’ Warning on the Google Structured Data Testing Tool. In the Schema plugin I have a 60 (height) by 600 (width) logo set in the “General” tab of the Schema plugin configuration page.

The next tab is the Knowledge Graph tab, which also asks for a logo which I understand must be square and at least 112 by 112. No matter what I put in there size-wise (even a square box), the Google Tool would throw the error noted above. So, I left the image item there blank, hit Save, cleared my cache and re-tested. Now I have 0 errors, and somehow Google is seeing the Publisher logo from my “General” tab and populating that in the Blog Publisher field as well, which I think solved the issue for me.

Not sure if this is a glitch unique to my site or something that might help debug the issue. For each Blog entry it looks like it has 4 or 5 entries for this logo, so not sure if it is something with my theme. In any event, the Warning message is gone for the time being. I don’t know how I will be able to insert a graphic (112 by 112 or something like that) into the Knowledge Graph tab without this problem reappearing, but that is for another day.

This was a script conflict on our end. Marking closed.

Yes @uriahs-victor that is correct. Will the fix be rolled into the plugin the next time it is updated?

@rohittm @uriahs-victor – not having any luck with my host as they are unable to determine where Feedzy is trying to put the cache. (see earlier messages above). Check out this link:

https://simplepie.org/wiki/faq/i_m_getting_cache_error_messages

That makes it sound like SimplePie would in theory be trying to put that ./cache in the same directory of the page calling it (i.e. https://www.inhouseblog.com/general-counsel-jobs/) although they do make mention of a hook that could change it to place it elsewhere (i.e., wp-content/cache, where all the other plugins put it).

Does this page help? Could a hook to point the cache to wp-content/cache do the trick?

@rohittm Does this webpage shed any light on the issue? In searching Google it seems that others have had the trouble with SimplePie and the cache location – this person seems to be saying that he figured out how to define the location so that SimplePie would be able to deposit the cache so that the caching works:

https://w3guy.com/fix-simplepies-warning-cache-writeable/

In my WordPress installation, I have a folder /wp-content/cache/ that is used by other plugins to hold their cache. Maybe this is where the plugin should also be putting its cache?

Hello @rohittm can you clarify this situation? The instructions are to modify the theme to not show the error. But does this mean that the plugin’s caching functionality is working? Or is hiding the error just doing that, hiding the error visually but the plugin is not caching? We hid the error and that worked visually but one day had a lot of traffic to the page and it caused our server to crash. So, we believe that the plugin is actually pulling the feed with each page load instead of caching, which is what the error seems like it is indicating. Any clarification on your part would be appreciated. We submitted this through premium support and we were told to go to our host to attempt to resolve the issue which to me seems to indicate that there is an issue with non-caching. Thanks in advance for any clarification.